Design Principles
Outcomes Over Output
A feature's existence is not success — a measurable change in user behaviour is.
Where it comes from
It's a core idea in the Lean UX movement, articulated by Jeff Gothelf: the measure of a design's success is not what gets shipped but what changes for the user. Building a feature is output; a measurable improvement in user behaviour is the outcome that actually matters.
Why it matters for your website
Shipping something is not the same as achieving something. Gothelf's outcomes-over-output principle says that the real measure of a design's success is not whether a feature exists but whether it produces a measurable change in how users behave. A page that catalogues what a product has rather than what a user gains is answering the wrong question. Visitors aren't shopping for features — they're trying to work out whether their situation will be different if they buy.
It's easy to mistake activity for progress. A feature shipped, a page launched, a list of capabilities — these are *output*, and output feels like accomplishment, but none of it counts until a user actually behaves differently as a result.
The same confusion shows up in copy. A page that catalogues what a product has is reporting output; a page that shows what the user gains is speaking to outcomes. Visitors aren't auditing your feature list — they're trying to work out whether their situation will be different, which is an outcome question.
Wrong vs right
A page that lists everything the product has — features, integrations, specs — as if their existence were the value.
A page that shows the outcome: what measurably changes for the user when they use it.
Measuring success by 'we shipped it', with no link to whether user behaviour actually changed.
Defining success as a measurable behaviour change and judging the work against that.
Copy framed around what the product is, leaving the visitor to guess at the result.
Copy framed around the result the visitor will get, so the value is explicit.
Understanding Outcomes Over Output
Outcomes over output is the principle that a design's success should be measured by the change it produces, not by the fact that something was built. Output is what you ship — a feature, a page, a redesign. An outcome is what changes as a result — a measurable shift in how users behave. The two are easily confused, and the confusion is expensive, because shipping can feel like success while nothing has actually improved.
Jeff Gothelf, in the Lean UX tradition, frames this as a discipline of asking what behaviour you're trying to change before deciding what to build, and then judging the result by whether that behaviour actually moved. A feature that exists but changes nothing is output that produced no outcome — activity mistaken for progress.
On a page, the same distinction sharpens the message. A page that catalogues what a product *has* is reporting output; a page that shows what a user *gains* is speaking to outcomes — and visitors care about the second, because they're trying to work out whether their situation will be different. It connects to jobs to be done, benefit framing, and actionable metrics.
How Kweri checks it
Kweri can assess one side of this directly: whether a page's copy is framed around what the product *is* (output) or what the user *gains* (outcomes), and prompt you where feature-cataloguing crowds out the result. What it can't measure is whether your shipped work actually changes user behaviour — that's an outcome only your analytics and experiments can confirm. So Kweri surfaces output-led framing on the page and prompts the outcomes question, while the real measurement of outcomes lives in your data, not the markup.
FAQ
What's the difference between outcomes and output?
Output is what you produce — a feature, a page, a redesign. An outcome is the change that results — a measurable shift in user behaviour. Output is activity; outcomes are the impact that actually matters.
Why is 'outcomes over output' important?
Because shipping something can feel like success while changing nothing real. Measuring by output rewards activity; measuring by outcomes rewards impact. A feature that exists but doesn't change behaviour hasn't achieved anything.
How does this apply to web copy?
A page that lists what a product has is reporting output; one that shows what the user gains speaks to outcomes. Visitors care about the result — whether their situation will change — so outcome-framed copy connects where feature lists don't.
Who came up with outcomes over output?
It's a core idea in the Lean UX movement, articulated by Jeff Gothelf. It reframes success around measurable behaviour change rather than the delivery of features.
How do I measure outcomes?
Define the user behaviour you're trying to change before building, then track whether it actually moves — through analytics, conversion data, or experiments. The outcome is the measured change, not the existence of the feature.
Related principles
People "hire" a product to get a job done — frame the experience around the job, not the features.
Visitors buy the outcome the product creates, not the product itself — copy that leads with what a user gains beats copy that leads with what a product does.
A visitor must be able to understand what a site offers, who it's for, and why it's the right choice — within 10 seconds and without working hard to decode it.
Attribution & sources
Identified by Jeff Gothelf. Catalogued from Lean UX (Jeff Gothelf).
A core principle of the Lean UX movement; the linked reference is used here.
See Outcomes Over Output on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →