Five Minutes to De‑Clog Your Ops
Expose three process gaps—and one head‑slap win—before the next fire drill
Startups often run on heroics: the founder juggles client delivery, WhatsApp pings, and spreadsheet chaos. Meetings sprawl, tasks slip, and nobody can see the whole board. Skip another “scale‑up playbook”—run this micro‑audit first.
Copy, paste, act
You are my 5‑minute ops sanity coach.
Before advising, collect only these five facts (ask if any are missing): 1. One‑line delivery flow: “We turn ___ into ___ for ___ via ___. ” 2. Recurring ops pain that hurts most (≤ 20 words). 3. Hours per week the founder spends firefighting. 4. Which assets exist today (Y/N): org chart, KPI dashboard, internal wiki. 5. Budget or time cap for a quick win.
Then, in ≤ 150 words, give me: • Three highest‑impact ops fixes (rank by hours saved). • One quick win we can ship in 14 days within the cap (name a tool if helpful). • The metric that will prove it worked.
Keep it calm, precise, and jargon‑free.
Why it works
Fire‑spotting. Stating the core flow + pain makes hidden friction visible.
Founder load. Quantifying firefighting hours reveals the real cost of chaos.
Asset check. Yes/No on org chart, dashboard, wiki pinpoints missing scaffolding—core to EOS “rocks,” FlowCode check‑lists, and Mochary/Martell scorecards.
Fast ROI. A single sub‑budget win—e.g., auto‑generated SOPs with ScribeHow, Notion wiki template, or Zapier task‑handoff—pays back inside a sprint.
How to use
Paste the prompt into ChatGPT (or Claude/Gemini).
Answer the five questions honestly; hit enter.
Spend one hour executing the quick win—document, automate, or delegate.
Track the proving metric (firefighting hours, task‑cycle time, missed‑handoffs).
Re‑run the audit each quarter; ops stays light, predictable, and founder‑stress drops.
No COO required—just clear visibility, one list, and a tiny automation budget.