How do I practice problem identification?

The most direct way to practice problem identification is through a focused exercise: Set a timer for two minutes. Write down every blocker you are currently aware of — anything preventing progress on any project, goal, or commitment in your life right now. Do not filter. Do not solve. Just name. Use the form: 'I cannot [action] because [specific obstacle].' After two minutes, review your list. Circle the one blocker that, if removed, would unlock the most downstream progress. For that one blocker, write one concrete next action that begins to address it. Notice two things: how many blockers you were carrying without having named them, and how much lighter the named ones feel compared to the unnamed residue still running in your mind.

Common pitfall: Waiting until the blocker is fully understood before writing it down. This is the most common failure — the belief that you need to diagnose the problem before you can name it. But diagnosis follows naming, not the other way around. If you wait until you understand the blocker completely, you will spend hours in a rumination loop where the unnamed obstacle generates anxiety, the anxiety impairs your ability to think clearly, and the impaired thinking prevents you from identifying the obstacle. The second failure mode is naming blockers in language so vague it provides no traction: "I am stuck" is not a blocker identification. "I do not know which API endpoint to call because the documentation contradicts itself in sections 3 and 7" is a blocker identification. Specificity is what converts a named obstacle into a solvable problem.

This practice connects to Phase 10 (Externalization Mastery) — building it as a repeatable habit compounds over time.