The 10 % Doubt Rule
“10 % Doubt” Micro-SOP (stop, zoom-out, and re-orient whenever your confidence slips below 90 %)
| Field | Content |
|---|---|
| Purpose | Prevent “cargo-cult execution” by forcing a deliberate pause the moment a task, its rationale, or its desired output feels even slightly fuzzy. |
| Applies to | Every contributor, every task, every phase. |
| Owner | The person doing the work (you). |
| Success Signal | You can explain—out loud, in 30 s or less—what you’re doing, why it matters, and what “done” looks like before resuming. |
| Trigger Level | Any feeling of ≥ 10 % uncertainty (≈ a “nagging doubt”) about next action, goal, or context. |
5-Step Reset Loop (“S-D-O-N-E”)§
| Step | Action | Tool / Tip |
|---|---|---|
| S — Stop | Pause timers (Clockify) → breathe. | Shortcut: ⌘ K to stop/start Clockify. |
| D — Drop | Put hands off keyboard for a moment to break momentum. | Prevents autopilot typing. |
| O — Orient | Ask & answer in notes: 1️⃣ Where am I in the big map? (Phase ➜ Step ➜ SOP) 2️⃣ What is the intended deliverable? 3️⃣ Why does it matter now? | Use the End-to-End Boot-camp doc or Oracle GPT prompt “Where am I now?”. |
| N — Next best step | Decide the single concrete action that will move you forward with clarity. | If still fuzzy ➜ escalate blocker in team chat (per “One Chat, No DMs” SOP). |
| E — Execute | Restart timers ➜ perform the next step ➜ log outcome. | Clockify entry = Phase / Step / SOP – action. |
Mnemonic: S-D-O-N-E → Stop • Drop • Orient • Next step • Execute (You’re not “DONE” until you’ve re-established 90 %+ certainty.)
Escalation Path (if clarity isn’t reached within 5 min)§
- Quick Search / Oracle GPT (2 min)
- Check documentation & past deliverables (1–2 min)
-
Post a 🔄 BLOCKER message in the team group with:
-
Context tried so far
- Specific question
- Impact if unresolved
Anti-Patterns to Avoid§
| Anti-Pattern | Why it Hurts |
|---|---|
| “I’ll just keep going and hope it’s right.” | Wastes billable time; snowballs rework. |
| Silent waiting for help after posting a vague “I’m stuck.” | Creates idle time; teammates can’t assist without context. |
| Jumping to another shiny task without logging the doubt. | Breaks traceability; hides blocker from metrics. |
Benefits Recap§
- Higher quality deliverables – fewer re-writes & bug-fixes.
- Faster skill growth – you consciously tie actions to purpose.
- Reliable time-tracking – timers reflect intentional work, not flailing.
If it’s not 90 % clear, invoke the 10 % Doubt Rule—every single time.