Benefits or Impact?
A few weeks ago, I wrote about how objectives, outcomes, and benefits are not the same thing. That post answered the question of what the difference is between objectives, outcomes, and benefits, and whether the sequence matters. Since that post, I have led multiple workshops and have discussed how perhaps the outcome is the objective. For a user experience designer, changing the user behavior for a fully self-service buy flow may be the objective that delivers business benefits. But there’s a question that goes beyond the outcomes, and it’s whether the action/feature/product delivered value? Did it have an impact?
Outcome vs. impact
Where the outcome is the change in user behavior, impact examines whether the change mattered.
We changed the checkout flow, and users completed the purchase faster (behavior changed). Did the revenue go up? Did the support calls go down? Did customers come back?
Teams can drive behavior change that doesn’t produce value. More clicks, more time on page, more logins — none of that is impactful unless it connects to something that matters for the user, for the business, or both.
Benefit vs. impact
Benefits are the upside we expect. Impact is what actually happened, including the things we didn’t plan for.
Benefit is direct, intentional, and always positive. It’s the short-to-medium term upside we planned for.
Impact is wider, often systemic, and can be positive, negative, or neutral. It’s the longer-term effect of the change, planned or unplanned.
A feature that increases engagement but burns out the support team has a positive benefit on paper and a negative impact in practice.
Benefits are the result of the bets we placed and the value we delivered; impact is the effect of the change.
Why this matters
Teams that only measure benefits stop too early. We ship, the north star metric turned green, and we move on. Leaders who only ask for benefits get a filtered view of what the team intended, not what the product caused.
When we skip the impact question, we create a blind spot where negative consequences go unexamined. The checkout flow is faster, but did returns increase because users are buying impulsively? The platform migration sped up one team, but did it break three others?
These are uncomfortable questions. That’s the point. Benefits tell us what we hoped would happen. Impact tells us the full story.
In the f(Clarity) framework, purpose examines why, users look at who, and impact tells us whether any of it mattered.
If we stop at the benefit and don’t look at whether it mattered, we are only telling half the story. What’s something your team shipped recently where the benefit was clear but the impact wasn’t?