Mission statements, strategic plans, social-responsibility commitments, and community priorities often express meaningful intent. But intent alone does not tell people what the organization is trying to change, how change is expected to happen, what the organization will actually do, or how it will know whether the work is producing value.
Without that design logic, impact work becomes vulnerable to drift. Activity gets mistaken for progress. Metrics become disconnected from strategy. Reporting becomes decorative rather than useful.
The result is not a lack of passion. It is a lack of architecture.
The logic that links intent, action, outputs, outcomes, and the conditions that allow change to occur.
The reasoned belief about what the strategy will improve, for whom, and through which mechanisms.
The meaningful change the organization is trying to influence beyond completing activities.
The set of measures, signals, feedback loops, and interpretation routines used to judge progress and learn.
An organizational factor — such as ownership, capability, engagement, or learning — that affects whether intended impact can actually be produced.
Name the problem, population, opportunity, or strategic priority the organization is trying to influence.
State what meaningful change would look like and why that change matters.
Specify what the organization will actually do, with whom, and through what mechanisms.
Surface what must be true for the pathway to work and where risk, fragility, or uncertainty sits.
Determine how progress, outcomes, and learning will be observed and interpreted.
Use evidence to refine the strategy without losing sight of the outcome the work exists to create.
The organization can distinguish desired change from activity, output, or aspiration alone.
The path from action to change is visible enough to explain, challenge, and improve.
People know who is accountable for shaping, carrying, and learning from the strategy.
Measures and signals are designed to support learning and decision-making, not just reporting.
The strategy reflects the realities, needs, and insight of the people or communities it aims to affect.
The organization can revise its methods while keeping the core impact logic intact.
What issue, opportunity, or strategic need are we trying to influence?
What will we do differently, repeatedly, or at scale to influence that issue?
What immediate products, services, experiences, or reach will result from those actions?
What meaningful change should occur if the strategy is working?
What will we examine to know whether progress is real, partial, delayed, or absent?
Busyness is treated as evidence of progress, even when the connection to outcomes is vague.
Measures exist, but they do not help the organization understand whether meaningful change is happening.
The strategy assumes impact without making the pathway between action and change explicit.
Evidence is collected for presentation rather than for interpretation, adaptation, or strategic choice.
The strategy exists conceptually, but no one clearly owns how it is implemented and evolved.
The organization ignores whether governance, engagement, measurement, or capacity are strong enough to support the intended impact.
Name the outcome clearly enough that the work can be organized around it.
Describe the pathway — the actions, actors, assumptions, and mechanisms involved.
Determine what evidence will show progress, unintended effects, or the need to adapt.