Decision Making Micro SOP
Decision-Making Micro-SOP ( “O-Z-E-D-R Loop” )
| Field | Content |
|---|---|
| Purpose | Give every teammate a 2-minute loop for deciding what to do next without waiting for leadership. |
| Applies to | All individual work inside the Learning-by-Doing boot-camp and live production work (Reddit, Ops, etc.). |
| Owner | Each Operator (you). |
| Success Signal | You always know exactly what you’re doing, why you’re doing it, and can point to a fresh deliverable & timer entry. |
| Red-Flag Rule | If you’re ≥ 10 % uncertain about what or why, STOP and re-run this loop from Step 1. |
Quick Visual§
┌───────────┐ 1 ┌────────────┐ 2 ┌───────────┐ 3 ┌───────────┐ 4 ┌───────────┐
│ ORIENT │ ───► │ ZOOM-IN │ ─► │ EXECUTE │─►│ DOCUMENT │─►│ REPORT │
└───────────┘ └────────────┘ └───────────┘ └───────────┘ └───────────┘
^ │
└───────────────────── if 10 % doubt ─────────────────────────────────┘
Step-by-Step§
| # | Action | Tips / Tools | Deliverable |
|---|---|---|---|
| 1. ORIENT | Zoom all the way out. Ask: “Where am I in the system?”. • Open README_Bootcamp.md → identify current Phase A-E. • Check Trello personal board Inbox / Q-columns for anything flagged URGENT. |
Oracle-GPT prompt:"Where am I in the boot-camp? List my open phases & blockers." |
Phase name (e.g. Phase A) written in your Clockify description. |
| 2. ZOOM-IN | Inside that phase, locate the next unfinished step/SOP (e.g. A-2 Device Focus Setup). Read the mini-goal + proof-of-done. |
• Use GPT: “Summarise step A-2 and the output I must attach.”• If GPT gives a Canvas, reply: “Text only.” |
New sub-tab in your Google Doc named A-2 Deliverable (empty for now). |
| 3. EXECUTE | • Start Time Doctor timer. • In Clockify: create a fresh entry titled PhaseA – A-2 Device Focus. • Do the work; keep Telegram open for “Ping when done”. |
Focus Mode → DND on phone (Phase A-0 rule). | A tangible output (file, screenshot, config, etc.). |
| 4. DOCUMENT | • Paste the output or screenshot into the matching Google-Doc tab. • Add bullet notes: “What went well / blockers / time spent”. |
Google-Docs ➜ Tools ▸ Preferences ▸ Enable Markdown → ⌘+Shift+V for clean paste. |
Updated Google-Doc evidence hub. |
| 5. REPORT | • Drop your Time-Doctor PNG + Doc link into Oracle-GPT with:"Create daily report JSON using these artifacts (▼).". • Copy the GPT summary → post in Telegram (Done with Step X — ready for next). |
Keep a second GPT tab as “Report Helper”, separate from the Oracle. | Daily report message posted; link lodged in Daily Reports tab. |
Exceptions / Branches§
| Situation | What to do |
|---|---|
| Blocked ≥ 5 min | Use Blocker escalation template in Telegram. |
| SOP asks for BitLocker but laptop is Win 10 Home | Skip, note the gap in Challenges bullet. |
| Urgent client ping interrupts loop | Pause Time-Doctor → create new Clockify entry “Client Hot-Fix” → run loop for that item, then resume. |
Reference Prompts§
- Orient
I’m at <Phase>. Show me unfinished steps (max 3) with proof-of-done bullets.
I want to execute <Step-ID>. Give me: goal, 3-sentence why, and exact deliverable format.
Using the Time-Doctor PNG + Google-Doc extract below, draft the End-of-Day report
in the standard schema (summary, hours, links, blockers, next-step).
Checklist (printable)§
- I know my current Phase and Step.
- Timer running in Time Doctor.
- Clockify entry matches phase/step.
- Deliverable pasted to correct Google-Doc tab.
- Telegram “Done with Step X” message sent.
- Daily report posted.
Why this loop matters§
More clarity → fewer stalls → more billable hours → bigger bonus. Follow it until it’s muscle-memory; tweak only if a better, explicit SOP replaces it.