How to Write Outcome Statements That Drive Product Decisions

The Sentence Structure That Predicts Product Success

Here is a claim that will sound absurd until you see it in practice: the single biggest determinant of whether your next product succeeds or fails is the quality of a few hundred sentences.

Not your engineering talent. Not your marketing budget. Not your competitive intelligence. Sentences.

Specifically, outcome statements — the precisely formatted expressions of customer needs that form the backbone of Outcome-Driven Innovation. Get them right, and you have a quantifiable map of every opportunity in your market. Get them wrong, and you are surveying noise.

This guide covers the art and science of writing outcome statements: the format, the rules, the examples, and the mistakes that even experienced researchers make.

What Is an Outcome Statement?

An outcome statement is a precisely worded expression of a desired outcome — a metric the customer uses to measure success when executing a job to be done. It captures what the customer wants to achieve, free of any reference to a specific solution.

Every outcome statement follows the same format:

Direction of improvement + Performance metric + Object of control

The three components:

• Direction of improvement: Always “minimize” or “maximize.” This makes the outcome measurable and unambiguous. You can always measure whether something has been minimized or maximized — you cannot measure whether something has been “improved” or “enhanced.”

• Performance metric: The specific dimension being measured. Common metrics include time, likelihood, number, amount, frequency, and degree.

• Object of control: What specifically is being measured, stated in the context of the job. This is the content-rich part of the statement — the part that captures the customer’s actual concern.

The complete statement reads as a single sentence: “Minimize the time it takes to identify the correct tool for the material being worked.”

Why the Format Matters

The rigid format of outcome statements is not bureaucratic pedantry. It serves three critical functions:

1. It eliminates ambiguity. “Better usability” means different things to different people. “Minimize the number of steps required to complete the calibration procedure” means exactly one thing. When you survey 300 customers on ambiguous statements, the data is meaningless. When you survey on precise statements, the data is actionable.

2. It separates needs from solutions. The format forces you to express what the customer wants to achieve — not how they want to achieve it. “I want a wireless connection” is a solution. “Minimize the time it takes to transfer data between the device and the analysis system” is an outcome. The first limits you to wireless technology. The second opens the solution space to wireless, wired, optical, near-field, or any other data transfer mechanism.

3. It makes outcomes surveyable. Because every statement follows the same format, you can ask the same two questions for each one: “How important is this outcome?” and “How well satisfied is this outcome?” This standardization enables the Opportunity Algorithm — the quantitative engine of ODI.

The Direction: Minimize or Maximize

Every outcome statement begins with “minimize” or “maximize.” No exceptions.

“Minimize” is used approximately 80% of the time. Most outcomes express something the customer wants to reduce: time, effort, likelihood of error, waste, variability, cost.

“Maximize” is used for the remaining 20%. It applies when the customer wants to increase something desirable: accuracy, confidence, range, capacity, visibility.

What about “optimize”? Never use it. “Optimize” is ambiguous — does it mean more or less? “Improve” has the same problem. “Ensure” is a trap — it implies binary success/failure rather than a spectrum. Stick to minimize and maximize.

The Metric: What Gets Measured

The performance metric is the bridge between the direction and the object of control. Common metrics include:

The metric must be specific enough to measure but general enough to avoid implying a solution. “Minimize the time” is good. “Minimize the download time” is solution-contaminated (it implies a digital solution).

The Object of Control: Where the Content Lives

The object of control is the substantive part of the outcome statement. It describes what is being measured, in the context of the job. This is where domain expertise matters most — and where most mistakes happen.

Good objects of control are:

• Specific to the job context: “…to position the load at the target elevation” (not “…to move things up”)
• Free of solution references: “…that the bond fails under vibration” (not “…that the adhesive fails”)
• Observable by the customer: “…to verify that the repair meets specification” (not “…that the molecular bonds are correctly formed”)

15 Example Outcome Statements Across Industries

Medical Devices

1. Minimize the time it takes to prepare the surgical site for the repair procedure
2. Minimize the likelihood that the repair device causes unintended tissue damage during insertion
3. Minimize the number of repositioning attempts required to achieve optimal placement
4. Maximize the degree to which the repair provides long-term structural integrity under physiological loads
5. Minimize the time it takes to verify that the repair meets the required closure strength

Industrial Equipment

6. Minimize the time it takes to determine the optimal lifting approach for the load’s weight distribution
7. Minimize the likelihood that the load shifts during transport to the target position
8. Maximize the ability to monitor the load’s stability in real time during the lift
9. Minimize the number of communication errors between the operator and ground crew during positioning
10. Minimize the amount of idle time caused by waiting for site conditions to permit the operation

Consumer Products

11. Minimize the time it takes to identify the correct product for the child’s developmental stage
12. Minimize the likelihood that the product causes skin irritation during extended use
13. Maximize the degree to which the product maintains its functionality after repeated cleaning cycles
14. Minimize the frequency with which the product needs to be replaced due to wear
15. Minimize the effort required to transition the child from one product size to the next

I’ve reviewed thousands of outcome statements over the past two decades. The ones that produce the best strategic insights share one trait: they describe something the customer would nod at vigorously if you read it to them, while containing zero information about how to solve it. That combination — resonant and solution-free — is what makes ODI outcomes uniquely powerful.

The 7 Most Common Mistakes

Mistake 1: Including Solution References

Wrong: “Minimize the time it takes to wirelessly transfer data from the sensor” Right: “Minimize the time it takes to transfer measurement data to the analysis system”

The word “wirelessly” smuggles a solution into the outcome. The customer’s need is fast data transfer — the technology is your design choice.

Mistake 2: Using Vague Metrics

Wrong: “Improve the quality of the weld” Right: “Minimize the likelihood that the weld contains structural defects detectable at inspection”

“Improve quality” is unmeasurable. What dimension of quality? Structural integrity? Visual appearance? Consistency? Each one is a separate outcome.

Mistake 3: Combining Multiple Outcomes

Wrong: “Minimize the time and effort required to set up and calibrate the device” Right (two statements):

• “Minimize the time it takes to set up the device for operation”
• “Minimize the effort required to calibrate the device to specification”

Each outcome must be independently measurable. When you combine two, you cannot determine whether the customer cares about the time, the effort, both, or neither.

Mistake 4: Using the Wrong Direction

Wrong: “Maximize the minimization of waste” Right: “Minimize the amount of material wasted during the process”

This seems obvious, but it trips up researchers who try to make statements sound more “positive.” Waste is something you minimize. Accuracy is something you maximize. Choose the natural direction.

Mistake 5: Writing Outcomes That Are Too Abstract

Wrong: “Minimize the risk of failure” Right: “Minimize the likelihood that the connection fails under repeated thermal cycling”

“Risk of failure” could mean anything. The specific statement tells you exactly what type of failure, under what conditions. This specificity is what makes the outcome actionable for engineering.

Mistake 6: Writing Outcomes That Are Too Granular

Wrong: “Minimize the time it takes to remove the third bolt from the left-side access panel” Right: “Minimize the time it takes to access the internal components for maintenance”

Outcomes should be at the level where a meaningful design decision exists. There is no design decision at the level of a single bolt — but there is a significant design decision about maintenance access.

Mistake 7: Confusing Outcomes with Job Steps

Wrong: “Check the oil level” Right: “Minimize the time it takes to verify that fluid levels are within the operating range”

Job steps belong on the Job Map. Outcomes describe what the customer wants to achieve at each step — they are the success criteria, not the activities.

How to Capture Outcomes in Interviews

Outcome statements are not dictated by customers. Customers describe their experiences, frustrations, and desires in natural language. The researcher’s job is to translate those raw inputs into properly formatted outcome statements.

Here is the translation process:

Customer says: “The worst part is when I can’t tell if the joint is tight enough. I’ve had cases where I thought it was good, but it failed the pressure test.”

Researcher captures:

• Minimize the likelihood that the joint fails a pressure test after assembly
• Minimize the time it takes to verify that the joint meets the required torque specification
• Maximize the degree to which the assembly process provides feedback on joint integrity in real time

Notice that a single customer statement often yields 2-4 outcome statements. Each one captures a different dimension of the same frustration.

Interview Probing Techniques

To elicit outcomes, use probing questions at each stage of the Job Map:

• “What are you trying to accomplish at this step?”
• “What could go wrong here?”
• “How do you know when this step is done correctly?”
• “What takes the most time at this step?”
• “What would a perfect result look like?”
• “What frustrates you most about this step?”

Each answer should be translated into one or more outcome statements before moving to the next probe. Do not wait until after the interview to write outcomes — you will lose the nuance and context.

For more on interview technique, see our JTBD Interview Guide.

From Statements to Strategy

Individual outcome statements are interesting. The complete set is powerful.

A typical ODI project produces 50–150 outcome statements. When these are quantified through survey research (measuring importance and satisfaction for each), the resulting Opportunity Algorithm scores reveal exactly where the market is underserved, appropriately served, and overserved.

The outcome statements with the highest opportunity scores become your innovation targets. Instead of vague goals like “improve the user experience,” you have specific, measurable targets:

• “Minimize the time it takes to verify that the load is secured to specification” (Opportunity Score: 15.2)
• “Minimize the likelihood that the load shifts during highway transport” (Opportunity Score: 14.1)
• “Maximize the ability to monitor load stability in real time during transport” (Opportunity Score: 13.8)

These three statements define a design brief. They tell engineering exactly what the customer needs, without prescribing the solution. They tell marketing exactly what to message. They tell product management exactly what to prioritize.

That is the power of well-written outcome statements. They are not just research artifacts — they are the bridge between customer need and product strategy.

A Practical Exercise

Want to practice writing outcome statements? Pick a job you know well — it does not have to be your product’s job. Try “prepare a meal for a family” or “commute to work” or “file an expense report.”

1. Map the job into 6-8 steps using the Job Map framework
2. For each step, write 3-5 outcome statements following the Direction + Metric + Object of Control format
3. Review each statement against the seven common mistakes listed above
4. Ask: Can I survey this statement? Does it make sense to ask “how important is this” and “how satisfied are you with this”?

If you can write 20-30 clean outcome statements for a simple job, you have the foundational skill. The rest is domain expertise and practice.

Frequently Asked Questions

Further Reading

• Outcome-Driven Innovation: The Definitive Guide
• The ODI Process: 6 Steps to Systematic Innovation
• The Opportunity Algorithm: Finding Underserved Customer Needs
• JTBD Interview Guide