Module 01 · 20 minutes
Outcomes
Begin with the user, the job they need to complete, the evidence, and the outcome they need.
Written and edited by Cahyanto Arie Wibowo. Last reviewed · version 1.2.
When is the idea of “Outcomes” most useful?
Within Product Thinking, the point of Outcomes is clearer when its benefit, owner, and limits are visible. Instead of memorizing Outcomes, compare one clear example with another that looks similar but works differently. You will leave with a simple way to explain Outcomes and one question that tests its limits.
After this lesson
- Within Product Thinking, the point of Outcomes is clearer when its benefit, owner, and limits are visible.
- Use the idea of “Outcomes” to interpret one realistic situation.
- Explain the limits of the concept and the information that still needs to be checked.
Start with the situation
Understand the situation first. The label can come later.
A request to 'build a chatbot' often hides a broader problem, such as difficulty finding reliable information. This lesson uses the idea of “Outcomes” to examine that situation without treating a single term as the answer to every problem.
Within Product Thinking, the point of Outcomes is clearer when its benefit, owner, and limits are visible. Begin with the user, the job they need to complete, the evidence, and the outcome they need. Connect the term to a decision someone genuinely needs to make.
See how the decision unfolds
Move from the situation to a choice others can review.
01
Situation
A request to 'build a chatbot' often hides a broader problem, such as difficulty finding reliable information. This lesson uses the idea of “Outcomes” to examine that situation without treating a single term as the answer to every problem.
02
Decision
A request to 'build a chatbot' often hides a broader problem, such as difficulty finding reliable information. Identify the part of the situation most closely connected to the idea of “Outcomes”. Use the case as a thinking tool, not as proof that one solution fits every context.
03
Review
A problem statement that already names the solution narrows the options too early. This mistake often appears when a label is used before the problem is understood. Write down your assumptions so another person can review them.
Visual model
Map the parts before choosing what to do.
Read the diagram as a map of Outcomes: begin with the context, follow the connections, and inspect the highlighted point before making a decision.
Do not rush the choice
Two ways to look at Outcomes
Useful when
- Within Product Thinking, the point of Outcomes is clearer when its benefit, owner, and limits are visible.
- Use the idea of “Outcomes” to interpret one realistic situation.
- Within Product Thinking, the point of Outcomes is clearer when its benefit, owner, and limits are visible. Begin with the user, the job they need to complete, the evidence, and the outcome they need. Connect the term to a decision someone genuinely needs to make.
Pause and check
- A problem statement that already names the solution narrows the options too early. This mistake often appears when a label is used before the problem is understood. Write down your assumptions so another person can review them.
- Explain the limits of the concept and the information that still needs to be checked.
The stronger choice is the one whose evidence, owner, and limits can be explained, not simply the more sophisticated option.
Try it on your work
Try it with one small piece of real work.
- Choose one real situation related to Outcomes.
- Separate what you can observe from what you are assuming.
- Write one decision, its owner, and the evidence needed to review it.
- Name the signal that would make you stop or change direction.
Make one small decision with the idea of “Outcomes”. Record your reasoning, the limits, and the signal that would make you change course. The larger module activity is: Turn the available evidence into one clear problem statement. Keep the first version small enough for another person to review in a few minutes.
Pause for a moment
What evidence could change this decision?
Answer before opening the discussion. Name one fact and one assumption.
Open the discussion
Within Product Thinking, the point of Outcomes is clearer when its benefit, owner, and limits are visible. Instead of memorizing Outcomes, compare one clear example with another that looks similar but works differently. You will leave with a simple way to explain Outcomes and one question that tests its limits.
A tempting shortcut
A familiar term can still lead us to the wrong decision.
Why this can seem reasonable
A problem statement that already names the solution narrows the options too early. This mistake often appears when a label is used before the problem is understood. Write down your assumptions so another person can review them.
How to check it
Instead of memorizing Outcomes, compare one clear example with another that looks similar but works differently. Begin with what can be observed, then separate facts, assumptions, and open questions.
Quick practice
Make one small decision with the idea of “Outcomes”. Record your reasoning, the limits, and the signal that would make you change course. The larger module activity is: Turn the available evidence into one clear problem statement.
Summary
- Within Product Thinking, the point of Outcomes is clearer when its benefit, owner, and limits are visible.
- Use examples and evidence to test your understanding.
- Record the limits, risks, and conditions that should trigger another review.
Continue from here
- Users and Jobs: Continue the idea from Start with the Problem, Not the Hype with a closely related example.
- When Not to Use AI: Connect this lesson to Applied AI and test the idea in another context.
- Data Distribution: See how the same decision changes when viewed through Data Literacy.
Sources and further reading
- People + AI Guidebook: Google PAIR · official-guidebook. Primary reference for the definition, evidence, or limits discussed in “Outcomes”.
- Artificial Intelligence Risk Management Framework: NIST · official-framework. Further evidence and context for checking the explanation in “Outcomes”.
- Rules of Machine Learning: Google for Developers · official-guidance. Further evidence and context for checking the explanation in “Outcomes”.