Problem Framing
Core Idea
Most product mistakes are not caused by bad solutions, but by solving the wrong problem.
Problem framing is the process of defining:
- what the actual problem is
- who it affects
- what constraints shape it
Before deciding what to build.
State of Thinking
Framing is not a one-time step — it is iterative. Define, test, update. Better framing leads to better decisions. If the problem is wrong, everything that follows will be wrong — even if execution is good.
Thinking Trace
How I approach problem framing
1. Start from what is actually happening
Focus on observable reality:
- what are users doing today
- where does friction occur
- what signals indicate a real problem
Avoid starting from ideas or assuming the problem is already known.
2. Move from symptoms to underlying problem
Most initial problem statements describe symptoms. The goal is to identify what is actually failing.
Example:
“Users cannot find helpers easily” may actually be “Information is fragmented and unstructured”
This shift matters because it changes what kind of solution is even possible.
3. Identify constraints early
Constraints define the solution space. These may include regulation, trust requirements, supply limitations, behavioural patterns. Ignoring constraints often leads to solutions that look good in theory but cannot work in practice.
4. Expect the framing to change
Initial framing is rarely correct. As more information appears, assumptions should be challenged and framing should be updated. This is not a mistake — it is part of the process.
What changed?
v1
— skip —
Why it changed?
v1
— skip —
Evidence / Signals
Example: Helper Match SG
Initial framing: “There is a gap in the market for maid transfers”
Updated framing: “This is a differentiation problem within an existing, constrained ecosystem”
What changed: existing players already operate in this space; regulatory constraints limit how matching can work; trust and process complexity are deeper than expected.
The key shift: from “no one is solving this” to “this problem exists, but winning depends on positioning within constraints.”
Open Questions
- At what point does iterating on framing become avoidance of execution?
- How do you know when the framing is good enough to move forward?
Connections
- Decision Making — choosing direction once the problem is framed
- Belief Updating — updating assumptions when reality changes
Changelog
- v1 — Initial node (migrated from Quartz pm-thinking, 2026-04-25)