Joseph is the Vice President of Customer Success at ClearPoint
There are many tools out there that can help you make "strategy" a little more clear
Table of Contents
The Aspen Institute defines theory of change as follows: "At its most basic, a theory of change explains how a group of early and intermediate accomplishments sets the stage for producing long-range results."
The theory of change model espoused by Aspen includes the following:
Learn more about the theory of change here.
The logic model is more focused than the theory of change framework. The W.K. Kellogg Foundation defines a logic model as "a systematic and visual way to present and share your understanding of the relationships among the resources you have to operate your program, the activities you plan, and the changes or results you hope to achieve."
The logic model has five components:
Read more about creating logic models here.
Finally, the strategy map (as we define it) is a set of cause and effect relationships that illustrate how the people, processes, and partners work together to achieve mission results. The strategy map is a pictorial representation of an organization's strategy and the hypotheses underlying that strategy.
A good strategy map will "tell the story of your strategy" and should be comprehensible by people within and outside your organization. Strategy Maps, as the name implies, are focused on the highest-level objectives and strategy of the organization and often will not mention individual programs by name. Instead, the strategy map includes the high-level pillars of your strategy and how you will achieve it.
Learn more about the strategy map here.
So, what model makes sense when?
The strategy map makes a lot of sense if you are operating at an organizational level and are looking to document your strategy in a way that everyone can understand. The theory of change, on the other hand, is more process focused. If the strategy map represents the "what" of your strategy, the theory of change represents the "how." Finally, logic models operate at the program level and really force the discipline of describing, in a concrete way, how the program will make an impact. I like to think of a logic models as a "business plan" for a program.