“Why is everything slow?” is the wrong question — it leads to vague “we need more focus” answers and another all-hands. The right question decomposes cycle time stage by stage, splits work from wait, and surfaces the one stage where 60% of total elapsed time is queue, not action. These prompts force that decomposition, name the stage with the worst wait-to-work ratio, and propose a ranked remediation plan instead of scapegoating one team. Pair with process improvement prompts once the bottleneck is identified.
Best for
- Engineering velocity audits
- Support ticket-time analysis
- Sales cycle audits and pipeline leakage
- Hiring pipeline audits
- Approval-chain and handoff reviews
- Cross-tool workflow consolidation
1. Cycle-time decomposition
Workflow: {workflow}. Stages: {stages}. For each stage, estimate (a) median time, (b) variance, (c) primary cause of waiting (handoff / approval / tool switch / rework). Output a stage-by-stage table with the top suspect highlighted.2. Wait vs work time
For each stage in {workflow}, split total elapsed time into WORK time (active) vs WAIT time (queued / approval / handoff). Any stage where wait > 50% of total time is a bottleneck candidate. Identify the top 2 and explain what kind of wait dominates each.3. Bottleneck remediation options
For the top bottleneck stage, propose 4 remediation options: (a) Eliminate the stage, (b) Parallelize with other work, (c) Automate, (d) Pre-stage prep. For each: estimated cycle-time reduction, effort to implement, risk introduced. Rank by impact × effort.4. Rework rate audit
Identify stages with high rework rate (work bounces back). Diagnose root causes: (1) Unclear input from prior stage, (2) Missing handoff doc, (3) Late discovery of a constraint, (4) Skipped acceptance check. For each: 1 preventive control + who owns it.5. Approval-chain audit
Workflow has approval steps. Audit: (1) Approvals that pass ≥ 95% of the time (candidates for removal or opt-out), (2) Specific approvers who are bottlenecks (out-of-office, SLA breaches), (3) Approvals that exist for legacy reasons no one remembers. Recommend trims.6. Tool-switching cost
How many tools does an item cross in this workflow? List them. For each tool boundary: time lost to context switch, copy-paste, missed notification, manual status sync. Recommend consolidations, with the 1 most impactful change first.7. WIP limit recommendation
Team has too much work-in-progress. Compute throughput vs WIP using Little's Law (cycle time = WIP / throughput). Recommend a WIP cap per stage. Explain the math so the team agrees with the cap instead of resenting it. Don't over-engineer.8. Engineering velocity audit
Eng workflow: open → in-progress → code review → merged → deployed. Identify which stage drags. Likely culprits: code review wait, CI duration, deploy gates, environment availability. Output stages ranked by median wait time + the single highest-leverage fix.9. Support ticket-time analysis
Tickets take an average of {avg} to close. Decompose: triage → first-response → investigation → fix → verification → close. Find the stage with highest wait. Suggest one intervention (template, automation, escalation rule) with expected lift.10. Sales cycle audit
Sales workflow: lead → qualified → demo → proposal → close. Audit: (a) stage-to-stage conversion rate, (b) average time per stage, (c) where opportunities die quietly vs explicitly. Identify the leakiest stage and the single sales motion change that could fix it.11. Hiring pipeline audit
Hiring pipeline: sourced → phone screen → onsite → offer → accepted. Audit: (a) median time per stage, (b) drop rate per stage, (c) most common reason candidates drop at each stage. Output 3 targeted fixes ranked by impact on time-to-hire.12. Bottleneck-to-roadmap
I identified bottlenecks A, B, C (paste). Prioritize by impact × effort. Output a 90-day plan: month 1 = quick wins (no new tooling), month 2 = process change (requires team alignment), month 3 = automation or tool consolidation. For each month: owner and success metric.
{paste bottleneck list}Common mistakes
- Asking “why is everything slow?” instead of decomposing cycle time stage by stage
- Optimizing a non-bottleneck stage — doesn’t reduce total cycle time, only adds slack to the bottleneck
- Scapegoating one team — bottlenecks are systemic, the team is downstream of the design
- Ignoring wait time — work time is usually smaller than wait time but gets all the focus
- No baseline measurement before the fix — can’t tell if the change worked
- Adding more approval steps “for visibility” — every approval is a wait queue in disguise
Related
- Process improvement prompts
- Project planning prompts
- Weekly report prompts
- SOP drafting prompts
- Project risk analysis prompts
- Productivity & Office Prompts hub
Tags: #Prompt #Productivity #Bottleneck