A technique described by Gojko Adzic in his book Impact Mapping that I have found extremely useful when applying the principles I present in the book. With Impact Mapping, a team begins with a business objective, maps it into what needs to change in order to accomplish that objective, and then maps each of those changes into possible ways to cause the change. These become the hypotheses that can be tested and used to drive the delivery of new IT services or business process changes. I present it as a way to support the Objective Model.
— War and Peace and IT: Glossary, Mark Schwartz