In enterprise software, there's a common pitfall: an obsession with feature lists. We are so focused on what software does that we've forgotten why we buy it in the first place. It's time to stop asking "what can it do?" and start demanding "what value will it deliver?"
This dysfunction is the "Output Trap." We have confused outputs (the tangible things we build like features and code) with outcomes, the measurable business results we actually need. Prioritizing outputs is a mistake we see all the time, and at Pega, we actively work to avoid it from day one of a client engagement. Instead of presenting a list of features, our proposals often start with a "Business Value Case." For one major bank, this meant focusing not on features, but on the outcome of achieving GBP 407M in incremental customer lifetime value and an 18-point increase in net promoter score.
The only way to escape the Output Trap is by defining your "North Star Metric." It is the single, critical business outcome that you are aiming for. A great North Star is specific and measurable. For example, a global consumer goods company we worked with, Unilever, established a North Star of saving 13,000 man-hours annually. Another client, a U.S. insurer, used Pega Task Mining to identify its North Star: recovering 48,000 work hours per year. These metrics are not features; they are meaningful, needle-moving business results.
Are you celebrating the launch of new outputs, or are you achieving meaningful outcomes?
With a North Star Metric fixed, features are no longer deliverables. They are specific bets made to move that metric. This requires a different kind of plan: an Outcomes Roadmap. A traditional roadmap is a timeline of features. An outcomes roadmap, which our Catalyst team builds, is a list of business problems to solve. A team using an outcomes roadmap isn't assigned "Build Feature X by Q3." They are tasked with "Cut customer onboarding time by 15%," and it's their job to figure out how.
To ensure these bets pay off, you need a process for measurement. Our consulting teams use a method called Business Value Realization (BVR). The work starts by setting a performance baseline before the project begins. The BVR process then tracks the North Star Metric and related KPIs through the project and after launch. The key question changes from "Did we launch on time?" to "Did we hit the ROI we forecasted?" This makes the software's business value a hard number, not a talking point.
So, take a hard look at your strategy. Are you celebrating the launch of new outputs, or are you achieving meaningful outcomes? The most successful enterprises know the difference, and it's time to stop buying features and start investing in results.
Ready to move from outputs to outcomes?
Related Resources
Don't Forget
- Continue the conversation on the Pega Community Forums.