Clarify the Problem
The second step in the ContextOS process — defining what needs to be solved.
The Core Argument
A well-defined problem is half-solved. The way we frame the problem determines the solutions we consider and the outcomes we achieve.
Once we understand the situation, the next step is to clarify the problem. This means defining what needs to be solved — clearly, precisely, and in a way that points toward a solution.
This step is often overlooked. People assume they know what the problem is. They rush to solutions without examining their assumptions. They solve the wrong problem.
Clarifying the problem is the most important step in the decision-making process.
The Danger of Solving the Wrong Problem
Why problem definition matters.
Wasted effort
Solving the wrong problem wastes time, money, and energy. The solution may be elegant, but it does not address the real issue.
Symptoms vs. causes
When we define the problem as a symptom, we address the symptom, not the cause. The problem returns.
Unintended consequences
Solving the wrong problem can create new problems. It can make the original problem worse.
Loss of trust
When people see that the wrong problem is being solved, they lose trust in the decision-makers. They wonder if anyone understands what is really going on.
The Acacia perspective:
The cost of solving the wrong problem is high. It is not just inefficiency. It is wasted effort, unintended consequences, and loss of trust. Clarifying the problem is the most important thing we can do.
How to Clarify the Problem
A structured approach to problem definition.
Ask "Why?"
Keep asking "why?" until you reach the root cause. Surface the assumptions behind the initial problem statement.
Frame as a question
Frame the problem as a question. "How might we..." invites possibilities. "Why is..." invites diagnosis.
Identify the gap
What is the gap between the current state and the desired state? What is missing? What is not working?
Define the scope
What is in scope? What is out of scope? Where are the boundaries? A well-defined problem has clear boundaries.
Test the definition
Test the problem definition with others. Does it resonate? Does it capture what needs to be solved? Is it clear?
Key insight:
Clarifying the problem is not a one-time activity. It is iterative. As you learn more, you may need to revise your problem definition. This is not failure — it is learning.
The Tools
How ContextOS helps you clarify the problem.
Problem framing templates
ContextOS provides templates for framing problems — helping you articulate the situation, the gap, and the desired outcome.
Root cause analysis
ContextOS provides tools for root cause analysis — helping you go beyond symptoms to understand the underlying causes.
Scope definition
ContextOS helps you define the scope — what is in and out of bounds. This prevents scope creep and keeps the problem manageable.
Stakeholder validation
ContextOS provides a way to validate the problem definition with stakeholders — ensuring that it reflects the real situation.
The Acacia perspective:
These tools are not just about defining the problem. They are about building a shared understanding of the problem — so that everyone is working on the same thing.
The Practice
How to make problem clarification a habit.
Start with the situation
Never define the problem without understanding the situation. The situation provides the context for the problem.
Write it down
Write the problem definition down. This forces clarity and creates a record that can be reviewed and revised.
Share it widely
Share the problem definition with others. Ask for feedback. Does it capture what needs to be solved? Is it clear?
Review and revise
As you learn more, revisit the problem definition. Revise it if needed. A good problem definition evolves with your understanding.
Key insight:
Clarifying the problem is a skill that must be practiced. It is not something you do once and forget. It is a habit of mind that improves with use.
Reading path: