Many teams are busy. The activity level is high. The meetings happen. The reports go out. The initiatives launch.
Then someone asks the hard question. What actually changed?
That's an Impact question. Many leaders can't answer it.
Performance tells you how much work happened. Impact tells you what the work moved forward. Those aren't the same measurement, and the gap between them is where accountability gets foggy.
Performance measures what you did. Impact measures what changed.
What people think Impact means
Many leaders think Impact is about results. Hitting targets. Delivering outcomes.
That's closer. It's still not the same thing. Impact is about what changed in the world outside the deliverable.
-
Not whether the report was completed, but whether decisions got better.
-
Not whether the training happened, but whether the behavior changed.
-
Not whether the product launched, but whether the problem it was built to solve is actually being solved.
Many teams produce outputs and measure them as outcomes. Outputs are things you make. Outcomes are things that change.
The gap between those two is where initiative accountability breaks down.
What Impact actually looks like in leadership
Impact shows up in three places.
-
Defining success as a change in condition, not a completion of activity
-
Asking “what did this move?” not “what did we deliver?”
-
Connecting every major initiative to a specific before-and-after that can be observed
When Impact thinking is present, the team asks a different question before any initiative launches: what problem are we actually solving, and how will we know it's solved?
A pattern I have lived through
I once launched an initiative to improve the customer experience. We ran the program. We measured participation. Every activity metric said it was working.
Six months later, customer retention hadn't moved.
We had measured activity: sessions delivered, hours logged, staff trained. We hadn't measured impact: whether customers stayed longer and referred more. Those were different numbers and they told a completely different story.
What changed was how we defined success at the front end, before launch. We stopped asking “what will we do?” and started asking “what will be different when this works?” That question forced specificity we hadn't had before.
You see this in team sports at halftime.
The coach who says “we need to play better in the second half” has described activity. The coach who says “we've been beaten on the left side on first downs, we're changing the coverage, here's the specific adjustment” is targeting impact.
One of those halftime talks produces a different second half. The other produces more effort toward the same result.
The discipline leaders must practice
Impact requires leaders to define change before they define activity. Three disciplines build that clarity.
-
Define impact before you define the initiative. Before any team launches a program or project, require one sentence: “We will know this worked when ___.” That sentence names the change, not the activity.
-
Separate outputs from outcomes in your tracking. Build two columns. One is what we delivered. One is what changed. Review both. If the output column is green and the outcome column is flat, you have a direction problem.
-
Ask “what did this move?” in every review. Make it a standing question in your post-launch check-ins. Not “did we deliver?” That's the floor. “What changed?” That's the measure.
Actionable application
Pick one current initiative. Ask three questions.
-
Can you state in one sentence what will be different in the world when this initiative works?
-
In your last review of this initiative, did you measure what was delivered or what changed?
-
If someone asked you right now “what did this move?” could you answer with a specific before-and-after?
If you can't answer question one, the initiative doesn't have an impact definition yet. Write that sentence before the next review. Everything else you measure follows from it.
What usually gets in the way
Impact is harder to measure than activity. Activity is always available: meetings happened, reports went out, hours were logged. Impact requires waiting for the world to respond.
Leaders default to activity metrics. They're immediate. They're controllable. Impact metrics require patience and a clear definition of what you're actually trying to change.
The result: teams stay busy, initiatives multiply, and the question “what did all of this actually move?” gets harder to answer each quarter.
Busyness and impact are not the same thing. One is motion. The other is movement.
Closing challenge
Look at your top three initiatives right now. For each one, ask: what will be different in the world when this works?
If you can't answer that in one sentence, you don't have an impact definition yet. You have a project plan.
Define the change first. Then build the work to create it.
One Word Leadership is our way of teaching leaders the disciplines that make growth less chaotic and more sustainable.
Pat Alacqua is a business growth strategist and Amazon best-selling author of Obstacles to Opportunity. He helps leadership teams think, plan, and execute differently so they can fix or prevent what growth breaks.