Article 06 · UX Principles
Outcomes Over Outputs
Why shipping more features does not necessarily create more value.
Core principle
Measure the change in user behavior or capability, not the volume of delivery.
Velocity can tell you how quickly a team ships. It cannot tell you whether the team solved the right problem.
Delivery is not the same as progress
Teams can complete hundreds of tickets while users remain unable to name a single meaningful improvement. Output measures activity: screens designed, stories closed, releases shipped. Outcomes measure what changed for people and the business.
Start with the big rocks
A backlog can fill quickly with surface-level improvements. If teams begin with small UI changes before defining the larger transformation, the meaningful problems may never fit. Establish the vision, identify the highest-impact problems, and connect smaller wins to those priorities.
A functional MVP, not a fragment
An MVP should provide enough value for a person to use, understand, and respond to. Delivering only a wheel does not validate a car. A skateboard may be simpler, but it still helps the user move from one place to another.
Protect trust while learning
“Fail fast” can become careless when failure affects users' time, confidence, or safety. The goal is to learn quickly through thoughtful experiments — not to transfer organizational uncertainty to the user.
Define success before building
Clarify the desired behavior, baseline, user value, operational value, and evidence that would change the team's decision. This keeps iteration connected to purpose.
Speed means nothing if we are not delivering the right solution.
Design takeaways
- Define the desired outcome before the feature.
- Connect small wins to a meaningful north star.
- Make MVPs functional enough to create real user value.
- Treat user trust as a design and product constraint.
Categories: UX Principles · Design Leadership · Human-Centered Design