Outcome-First Product Design
Design around the result customers seek, then perfect how they reach it.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 94%
Outcome-First Product Design begins with the task a customer is trying to complete rather than a narrow demographic profile. Define the desired end state, identify the best way to reach it, and then make that result attainable without unnecessary specialist knowledge. Wix applied this logic by serving computer-savvy people who did not need to know HTML or CSS, while emphasizing websites they could make visually impressive. The desired outcome also becomes a feature-prioritization rule: improvements that strengthen the result can outrank sophisticated additions that do not. The mechanism is a chain from customer job, to quality bar, to simple path, to focused product choices. This gives a product a concrete basis for standing out while keeping its roadmap tied to what users want to accomplish.
Origin
Extracted from The Foundr Podcast
Core principles
- 01Start with what people are trying to accomplish
- 02Prioritize the quality of the finished result
- 03Serve capable users without requiring specialist skills
- 04Use the core outcome to resolve feature trade-offs
How to run it
- 1
Define the customer job
State what users are trying to accomplish in plain language. Keep the focus on the task rather than an overly narrow customer label.
Pro tip Use a verb and an object, such as create a presentation or build a website.
Watch out Do not assume that a broad job means every possible user has identical needs.
- 2
Set the quality bar
Describe how the completed work should look or feel to the user. Make the result specific enough to guide trade-offs.
Pro tip Ask what would make users proud to share the result.
- 3
Design the easiest credible path
Remove technical barriers that are not essential to the job while retaining enough capability for strong results.
Pro tip Target users' existing level of tool fluency rather than assuming no computer knowledge.
Watch out Oversimplification can prevent capable users from expressing their vision.
- 4
Prioritize against the outcome
Compare roadmap options by how directly they improve the customer's desired result. Defer clever features that contribute less to that outcome.
Pro tip Use the desired result as the repeated question in product meetings.
- 5
Validate the finished work
Observe whether customers can produce the intended result and feel ownership of it. Use that evidence to refine the path and quality bar.
Watch out Ease of use alone is not proof that the output is good.
In the wild
Wix chose computer-savvy, nontechnical users and focused on helping them build visually impressive websites. In product discussions, Abrahami says he repeatedly favored better galleries, fonts, and effects because those capabilities helped users create work they were proud of.
→ The visual-outcome focus became a successful differentiation strategy for Wix.
A team designing presentation software starts with the job of creating a presentation, then defines the desired result as a beautiful, clear deck. It prioritizes layouts, typography, and guided composition before adding peripheral administration features.
→ The roadmap stays aligned with the quality of the presentation users want to produce.
Common mistakes
Starting with a narrow persona
A detailed persona can distract the team from the common job that gives the product broad utility.
Optimizing only for simplicity
A product can be easy to use yet still create an output customers find unattractive or ineffective.
Prioritizing impressive side features
Sophisticated features consume attention when they do not materially improve the core result.
Is it for you?
Best for
It is best for product teams entering broad or crowded categories with a clear customer job.
Not ideal for
It is not ideal when the team has not yet identified a real job customers need to complete.
From the transcript
“don't ask too 10 00 much about who is the customer care more about what they are trying to do”
“ask yourself what is the most important thing for the customer when you want to do it”
“great products are always focusing on what the customer want to do”
From the episode
507: Wix Co-Founder Shares Website Tips from 250M+ Users
Avishai Abrahami