Module 02 · 16 minutes
Frequency and Severity
Map opportunities by how often a problem occurs, how severe it is, and what value a solution could create.
Written and edited by Cahyanto Arie Wibowo. Last reviewed · version 1.2.
How does the idea of “Frequency and Severity” change the decision we make?
This part of Product Thinking uses Frequency and Severity to separate what is known from what still needs to be tested. Frequency and Severity becomes easier to understand in a real situation. Notice what changes in the choice, the risk, and the way the result is reviewed. The result should be an explanation of Frequency and Severity that another person can follow, supported by a relevant example.
After this lesson
- This part of Product Thinking uses Frequency and Severity to separate what is known from what still needs to be tested.
- Use the idea of “Frequency and Severity” 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 small problem that happens often may matter less than a rare problem with serious consequences. This lesson uses the idea of “Frequency and Severity” to examine that situation without treating a single term as the answer to every problem.
This part of Product Thinking uses Frequency and Severity to separate what is known from what still needs to be tested. Map opportunities by how often a problem occurs, how severe it is, and what value a solution could create. Connect the term to a decision someone genuinely needs to make.
Do not rush the choice
Two ways to look at Frequency and Severity
Useful when
- This part of Product Thinking uses Frequency and Severity to separate what is known from what still needs to be tested.
- Use the idea of “Frequency and Severity” to interpret one realistic situation.
- This part of Product Thinking uses Frequency and Severity to separate what is known from what still needs to be tested. Map opportunities by how often a problem occurs, how severe it is, and what value a solution could create. Connect the term to a decision someone genuinely needs to make.
Pause and check
- Stakeholder demand alone does not prove that a solution creates value. 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.
Visual model
Map the parts before choosing what to do.
Read the diagram as a map of Frequency and Severity: begin with the context, follow the connections, and inspect the highlighted point before making a decision.
Let’s see how it works
Reading the situation in practice
Frequency and Severity becomes easier to understand in a real situation. Notice what changes in the choice, the risk, and the way the result is reviewed. Begin with what can be observed, then separate facts, assumptions, and open questions.
A small problem that happens often may matter less than a rare problem with serious consequences. Identify the part of the situation most closely connected to the idea of “Frequency and Severity”. Use the case as a thinking tool, not as proof that one solution fits every context.
Pause for a moment
What evidence could change this decision?
Answer before opening the discussion. Name one fact and one assumption.
Open the discussion
This part of Product Thinking uses Frequency and Severity to separate what is known from what still needs to be tested. Frequency and Severity becomes easier to understand in a real situation. Notice what changes in the choice, the risk, and the way the result is reviewed. The result should be an explanation of Frequency and Severity that another person can follow, supported by a relevant example.
A tempting shortcut
A familiar term can still lead us to the wrong decision.
Why this can seem reasonable
Stakeholder demand alone does not prove that a solution creates value. 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
Frequency and Severity becomes easier to understand in a real situation. Notice what changes in the choice, the risk, and the way the result is reviewed. Begin with what can be observed, then separate facts, assumptions, and open questions.
Try it on your work
Try it with one small piece of real work.
- Choose one real situation related to Frequency and Severity.
- 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.
Choose a task you know. List what is known, what is still an assumption, and what must be tested before using the idea of “Frequency and Severity”. The larger module activity is: Rank several opportunities using evidence rather than opinion alone. Keep the first version small enough for another person to review in a few minutes.
Quick practice
Choose a task you know. List what is known, what is still an assumption, and what must be tested before using the idea of “Frequency and Severity”. The larger module activity is: Rank several opportunities using evidence rather than opinion alone.
Summary
- This part of Product Thinking uses Frequency and Severity to separate what is known from what still needs to be tested.
- Use examples and evidence to test your understanding.
- Record the limits, risks, and conditions that should trigger another review.
Continue from here
- Value Exchange: Continue the idea from Opportunity and Value with a closely related example.
- Build, Buy, or Combine: Connect this lesson to Applied AI and test the idea in another context.
- Updating with Evidence: 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 “Frequency and Severity”.
- AI Risk Management Framework Playbook: NIST · official-framework. Further evidence and context for checking the explanation in “Frequency and Severity”.
- Evaluation best practices: OpenAI · official-documentation. Further evidence and context for checking the explanation in “Frequency and Severity”.