Map What You Do Not Know Before You Start
Added 2026-11-05
Writing the unknowns down early is cheaper than discovering them mid-build.
I am about to start this: [task and context]. Before I touch anything, show me the blind spots: 1) list the knowledge, skills, and information the task needs, graded as know it, half know it, or do not know it at all; 2) split the "do not know" items into those that will block progress and those that can be routed around; 3) for each key blind spot, the cheapest way to close it — who to ask, what to read, how small a test to run; 4) the part I am probably overrating my grasp of, with a ten-minute self-test; 5) an order for closing them. Do not reassure me that I can learn it all.
Site original
Chinese original
Replace these placeholders 1
Swap the bracketed parts for your own details before sending.
[task and context]
How to use
The moment you write down "I do not know this," the risk becomes something you can discuss.
Try tweaking it
- Ask what evidence would overturn the judgement.
- Have it argue both sides with three reasons each.
What you should get
- A decision table: assumptions, evidence, counter-evidence
- A next action with an observable signal
Common mistakes
- Asking only "should I?" and getting equally valid answers both ways.
- Never asking for counter-examples, so you only hear support.
How to check the output
- It states what evidence would overturn the conclusion.
- Both sides are argued, with assumptions marked as such.
Where it works
- Good for: splitting a decision into assumptions, evidence and counter-cases, leaving the call to you.
- Watch out: ask what evidence would overturn the judgement, or you will only hear supporting reasons.