/problem-space

Map the terrain where solutions live: objective, constraints, systems, assumptions, and what would prove the map wrong.

Problem space precedes solution space. Jump to code too early and you build the wrong thing fast.

When to Use

• Starting new work before implementation
• Repeated blockers or patches keep appearing
• Estimates are badly off
• Constraints are being hand-waved away

Skip when: The problem is well-understood and you are in execution.

The Problem Space Process

Step 1: State the Objective