01
Observable value
Success is described through a change in behavior or condition that can be seen, tested, and measured.
Outcome-oriented designUX is the product
Design the change
Start with the outcome. Earn every feature.
HAAM begins with the behavior and result that must change, then chooses the research, design, engineering, analytics, automation, or AI needed to move it.
The principle
The product is the experience people can actually use.
“The UX is the product. Everything else, including AI, is a tool for making it better.”
A polished interface can still produce hesitation, abandonment, errors, support burden, or mistrust. Outcome-oriented design follows the complete journey across the interface, service, system, and organisation, then holds the work accountable to observable change.
02
Evidence over opinion
Research, analytics, accessibility, support, and product states become one shared picture of the journey.
03
Replaceable tools
Methods and technologies can change as long as the experience improves and the guardrails remain protected.
Translate requests into consequences
A feature request is the beginning of the design question.
Incoming request
Outcome question
Add an AI assistant
Which important task should become easier, faster, or safer?
Redesign the dashboard
Which decision should become clearer, and for whom?
Improve onboarding
Which first-value behavior should increase?
Add personalisation
Which repeat behavior should improve without reducing user control?
Interactive outcome builder
Turn an ambition into a usable contract.
Define the change, audience, baseline, target, timeframe, and guardrail. The result is specific enough to guide research, prioritisation, design, delivery, and measurement.
The outcome stack
Connect strategy to the smallest interaction.
Each layer should explain the one below it. This keeps the product coherent while preventing a tool, trend, or stakeholder request from becoming the strategy by accident.
- 01
Outcome
The business or public-value result that should change.
More qualified customers reach value and stay.
- 02
Behavior
The observable action people need to complete more often or with less friction.
New users finish setup and create their first useful result.
- 03
Experience
The conditions that make the behavior understandable, possible, trustworthy, and worth repeating.
Clear choices, immediate feedback, preserved progress, safe recovery.
- 04
System
The product logic, content, data, operations, and engineering required to support the experience.
State handling, permissions, instrumentation, support ownership.
- 05
Tools
The replaceable methods and technologies used to build the system.
Research, prototyping, code, analytics, automation, AI.
How HAAM works
01
Frame the change
Define one meaningful outcome, the user behavior behind it, a timeframe, and the guardrails that cannot be traded away.
02
Find the evidence
Combine research, analytics, support patterns, accessibility findings, product states, and operational constraints.
03
Redesign the journey
Work across content, interaction, service, system behavior, and visual hierarchy instead of treating the screen as an isolated artifact.
04
Prototype the behavior
Test the decisions, states, recovery paths, and feedback loops that determine whether the outcome can move.
05
Ship with measurement
Build or hand off implementation-ready work with events, baselines, ownership, and a plan for reading the result.
06
Learn and compound
Keep the evidence. Every launch should improve the next design decision, not reset the team to opinion and memory.
Measurement
Measure value, friction, and the cost of the shortcut.
A single conversion number can hide confusion, exclusion, pressure, errors, or support work. A useful measurement model combines the desired result with early experience signals and explicit guardrails.
01
Primary outcome
The change that matters: completion, activation, retention, confidence, recovery, revenue, cost, or public value.
02
Leading indicators
Early evidence such as time to value, task success, errors, hesitation, correction, and repeated support questions.
03
Guardrails
Accessibility, trust, privacy, performance, user control, sustainability, and long-term brand credibility.
Task success
Time to value
Error recovery
Repeat value
Confidence
Support burden
Accessibility
Performance
When this approach earns its keep
Use it where activity has outrun clarity.
- 01A roadmap is crowded with features but the team cannot explain which result each one should change.
- 02A redesign is planned, yet success is still described through taste, polish, or stakeholder approval.
- 03AI is being added because the technology is available, before the useful user behavior is clear.
- 04Analytics show activity while task completion, recovery, confidence, and repeat value remain invisible.
- 05Product, design, engineering, marketing, support, and leadership are optimising different versions of success.
Related work
Green Filter
Research-led decision support connecting recommendations, user choices, feedback loops, and measurable sustainable behavior.
Related work
AI Product Trust Sprint
A focused service that redesigns one critical AI journey around trust, correction, recovery, and measurable value.
Related work
User research
Research planned around the decision the team needs to make, with evidence carried through into product work.
Work with HAAM
Bring one important journey and the evidence you already have.
HAAM can frame the outcome, study the journey, prototype the behavior, help build the product, and connect the result to measurement. The engagement follows the problem rather than a predetermined deliverable.
Start with the outcomeFounder-led by Kris Haamer. Available for focused sprints, product redesigns, design engineering, and ongoing improvement.