Building Software Right Isn’t Enough
Do you know what percentage of features we build are rarely or never used by the end customer? Over 60% of software features fall into that category.
Imagine launching a new feature your team spent weeks building. It’s secure, tested, and beautifully integrated. But then… no one uses it. According to Pendo, 80% of features in the average software product are rarely or never used.
That’s billions in wasted engineering effort, and a clear signal:
Building software right isn’t enough.
We must ensure we are building the right software, and proving it matters
What do teams need to shift toward?
To move from output to outcome, teams must embrace four key mindsets:
Dual Commitments in the Scrum Guide Expansion Pack 2025
To support this evolution, the Scrum Guide Expansion Pack 2025 introduces a new dual commitment:
- Definition of Output Done – Is it built right?
- Definition of Outcome Done – Did it make an impact?
How to apply
At SQLI we make it actionable by:
Indicators that matter
We need to distinguish between leading and lagging indicators. Both are essential to measure outcomes effectively.
Examples of outcome criteria
Outcome criteria define success beyond delivery, focusing on measurable impact and validated hypotheses for each Product Backlog Item.
By embracing outcome-driven practices, defining clear indicators, and validating real impact, teams can move beyond vanity delivery and create products that truly make a difference. The question is: how will you measure success in your next Sprint?
How does your team know when an outcome is truly done?
Check how our Agile Services support digital transformation with data-driven delivery and adaptive practices.
