What is an impact strategy?
An impact strategy sets out the change an organization intends to support, the choices it will make to pursue that change and how evidence will inform those choices. It identifies the people or systems affected, priorities, activities, assumptions, resources, responsibilities and ways to assess progress. It should also explain which results would lead the organization to continue, adapt or reconsider its approach.
The strategy is broader than a set of indicators. It may include outcomes that take years to observe, commitments to how people are treated and choices about where the organization will not operate. Measurement helps examine the strategy; it should not reduce the mission to whatever happens to be easiest to count.
This guide is for leaders and program, portfolio or operations teams turning an impact ambition into a workable plan. It includes a reusable structure, a fictional example, collection design and a review process. For methods of gathering evidence, use the companion impact measurement guide.
How strategy, theory of change and measurement fit together
Scroll horizontally to see all columns →
| Part | Question it answers | Useful output |
|---|---|---|
| Impact strategy | Which changes will we pursue, through which choices and resources? | Priorities, scope, responsibilities and review decisions |
| Theory of change | Why might our activities contribute to those changes? | A reasoned pathway with assumptions and alternative influences |
| Measurement plan | What evidence will help us assess progress and those assumptions? | Questions, indicators, methods, timing and owners |
| Management review | What should we do in light of the evidence? | An agreed action, responsible owner and follow-up |
| Impact reporting | What can we explain credibly to others? | Findings, supporting evidence, limitations and next steps |
These parts need a clear connection, but they do not need to be one document or one database record. A strategy can refer to several evidence sources. The important test is whether a reviewer can follow a priority through its assumptions, available evidence and resulting decision.
Use the theory of change guide to develop the pathway and the five dimensions of impact to broaden the questions you ask about effects and uncertainty. Neither framework validates the strategy simply by being included in it.
How to build an impact strategy
1. Understand the situation with the people affected
Describe the problem, whose experience matters and what is already known. Include delivery staff, partners and affected groups in a way that suits the context. Examine existing evidence before commissioning more collection. Differences in experience can reveal where a single organization-wide objective is too broad.
2. Choose priorities and boundaries
State which changes the organization will pursue and which it cannot reasonably take responsibility for. Explain the trade-offs. A training organization might prioritize sustained use of skills at work rather than maximizing enrollment alone. It cannot control employer decisions or the wider labor market, but it can plan how to examine their influence.
3. Explain the expected pathway
Connect activities to near-term and longer-term outcomes. Name assumptions such as access, participation, partner capacity or opportunities to apply learning. Include possible unintended effects and questions that could challenge the preferred explanation. An attractive diagram should make this reasoning easier to inspect, not conceal uncertainty.
4. Plan resources and responsibilities
Identify what delivery, coordination, collection and analysis require. Assign an owner for the strategic priority and for each decision the evidence must inform. If partners provide essential information, agree responsibilities and collection burden before treating that information as guaranteed.
5. Select useful evidence
Choose measures and methods that fit the question. Some outcomes need several indicators or a qualitative investigation; they cannot be reduced to one field. Other questions can be answered from existing operational data. Document what is feasible now, what needs further evaluation and where evidence remains unavailable.
6. Set review points and decision rules
Agree when evidence will be reviewed, who participates and what kinds of findings call for action. A threshold can prompt investigation, but it should not automatically dictate a strategic change. Preserve room to consider coverage, unintended consequences and context before deciding.
A practical impact strategy template
Use the following structure for one strategic priority. A short, specific plan is easier to maintain than a large inventory of disconnected indicators.
Scroll horizontally to see all columns →
| Section | What to write |
|---|---|
| Situation and intended change | The problem, affected groups, scope and meaningful progress |
| Strategic choice | What you will prioritize, what you will not do and why |
| Pathway and assumptions | Activities, expected outcomes, dependencies and alternative influences |
| Evidence questions | What the team needs to know before continuing or changing the approach |
| Measures and methods | Sources, definitions, populations, timing and limitations |
| Resources and ownership | Delivery and evidence responsibilities, capacity and partner commitments |
| Review and decisions | Cadence, participants, investigation triggers and recorded actions |
| Communication | What will be returned to participants, partners, leaders and reporting audiences |
Example: improve the use of skills after training
Fictional planning example, not a customer outcome. An organization delivers professional-development courses through regional partners. Its old plan emphasizes increasing course completions. Its revised priority is to help participants use relevant skills in their work, while continuing to monitor access and completion.
The expected pathway is that relevant instruction, practice, feedback and an opportunity to apply the skill support later use. One important assumption is that participants' workplaces provide that opportunity. The organization can improve the course and partner coordination; it cannot guarantee the workplace conditions.
Scroll horizontally to see all columns →
| Strategic question | Evidence to collect | Possible decision |
|---|---|---|
| Are we reaching the intended participants? | Enrollment and participation coverage against the intended audience | Review outreach or access barriers |
| Can participants demonstrate the skill? | An appropriate assessment with a defined standard | Review instruction, practice or assessment design |
| Do participants have an opportunity to apply it? | A later check-in and relevant participant or manager perspectives | Review partner arrangements or support after the course |
| Is the skill being used? | A suitable follow-up measure with timing, coverage and source limitations | Continue, adapt or investigate before expansion |
Suppose 50 of 80 participants answer the follow-up and 20 of those respondents describe limited opportunities to apply the skill. That is a reason to investigate, not evidence that 40% of every participant lacked opportunity or that this issue caused all weak outcomes. The team should examine who responded, whether the pattern differs by partner and what other evidence supports it.
A practical action might be to test a partner-supported application activity in the next cohort. The strategy review records the reason, owner and evidence needed to assess that change. It does not erase the previous result or announce success before the follow-up exists.
Connect the plan to collection without over-standardizing
For each evidence question, define the relevant record or group, measure, population, source and period. Keep stable registration context separate from repeated observations. Collect changing attributes through an explicit update process rather than repeatedly asking for every detail.
Across a network, sites can use locally appropriate forms while sharing a limited core of comparable fields. A data dictionary should specify the shared meaning and how local instruments map to it. If one partner measures course satisfaction and another measures skill use at work, those are different results, not two versions of the same strategic indicator.
Where individual change matters and identification is appropriate, plan how observations will be connected over time. For anonymous feedback or organization-level change, use suitable group or organization context. A strategy does not become more credible simply because every record contains a person's name.
Keep the strategy responsive without chasing every fluctuation
Different decisions need different cadences. Operational problems may need prompt review, while strategic outcomes may take months or years to emerge. A regular review should consider evidence readiness as well as results: what arrived, what is missing, which definitions changed and whether the available information can answer the question yet.
Record three things separately: the finding, its interpretation and the decision. This helps a future reviewer understand why the organization acted and whether later evidence changed that view. Preserve the previous strategy and measure definitions when revisions occur.
Changing a question can be sensible when the old one was weak. Document the change and assess whether a comparison remains defensible. Do not freeze a poor measure forever for the appearance of consistency, or combine incompatible versions as if nothing changed.
How a connected workflow supports the strategy
Sopact's role is to support the collection, analysis and governance that keep relevant evidence available for review. When structured measures, comments and documents retain their context, an operating team can spend less time rebuilding the evidence and more time examining the strategic question.
For codebook-based analysis, the team defines and reviews themes while automated processing applies the definitions across eligible responses. Revisions still need validation. The aim is to make repeated analysis practical, not to let a system decide which mission priorities the organization should pursue.
Test the workflow with a real strategic question: introduce a new observation, change an indicator definition, inspect missing coverage and trace a reported finding to its source. Include setup, review and ongoing maintenance in the ownership estimate. The qualitative and quantitative analysis guide provides a visual explanation and an illustrative staff-hours comparison.
Explain progress without overstating it
An impact statement should summarize the intended change and the organization's contribution, but it is not proof. Report the observed result, evidence period, coverage and main limitation. Distinguish a future commitment from a completed outcome, and explain what the team changed after review.
Use How to Write an Impact Report to turn that evidence into a clear narrative, and explore report examples for presentation ideas. For the ongoing decision process, see social impact management.
Watch: separate delivery from intended change
This video explains outputs and outcomes. Use the distinction when checking whether your strategic measures describe delivery, observed change or a longer-term claim that needs more evidence.
Frequently asked questions
What belongs in an impact strategy?
Include the intended change, affected groups, priorities, activities, assumptions, resources, responsibilities, evidence questions and review decisions. Explain the boundaries of the organization's contribution and what remains uncertain.
How is an impact strategy different from a theory of change?
A theory of change explains the expected pathway between activities and outcomes. An impact strategy also sets priorities, allocates resources, assigns responsibilities and determines how evidence will inform choices.
Does every outcome need to be a single data field?
No. An outcome may require several measures, qualitative evidence or a separate evaluation. Define a feasible evidence approach without removing meaningful goals simply because they are harder to measure.
How often should an impact strategy be revised?
Review it at a cadence suited to the decisions and expected outcomes. Operational issues may need quick attention, while strategic changes require enough evidence and consideration of context. Record why a revision was made.
Can one strategy cover several programs or sites?
Yes, if shared priorities and definitions are clear while meaningful local differences remain visible. Use a limited common core for comparison rather than imposing identical measures on work with different purposes.
Does software create an impact strategy?
Software can help organize evidence, analysis and review. People still choose priorities, examine trade-offs, allocate resources and decide what the evidence justifies.
Choose your next step
American Heart Association Ventures
Explore how impact plans and evidence are connected in a portfolio workflow. This story does not validate the fictional training strategy above.
Read the customer story →