Process improvement from bottleneck to fix

Map a messy workflow, find the bottlenecks and waste, and get ranked improvements with effort, impact and a pilot plan.

LLazyPrompt(@lazyprompt)Business & StrategyAnalyzeWorks with any model
No ratings yetSign in to rate
Save 0 Fork Report
Prompt template
Act as an operations improvement consultant. Analyse this process and recommend improvements.

Process: {{process}}
Who is involved: {{people}}
Current steps and pain points (as messy as you like):
{{steps}}

Metrics, if known (volume, cycle time, error rate, cost): {{metrics}}
Constraints (tools, budget, compliance): {{constraints}}

Please deliver:
1. **Cleaned-up process map**: numbered steps with owner, tool and approximate time per step. Mark waiting time separately from working time.
2. **Diagnosis**: the 3 biggest bottlenecks and the root cause of each (ask "why" until you reach something fixable). Separate real problems from symptoms.
3. **Waste check**: rework, handoffs, approvals that add no value, duplicate data entry, and steps that can be removed entirely.
4. **Improvement options**: 6 to 8 changes in the order: eliminate, simplify, automate, then reorder. Present them in a table with impact (high/med/low), effort, cost and risk.
5. **Recommended package**: pick the best 3 and describe the future-state process in numbered steps.
6. **Pilot plan**: what to test for 2 weeks, how to measure success against the current metrics, and how to bring the team along.

If a metric is unknown, propose how to measure it quickly rather than guessing.
Example output
**Process map (current)** 1. Proposal signed (Sales, e-sign) - 0 days 2. Details re-keyed into CRM, billing and practice system (Admin) - 1 day, plus 2 days waiting 3. Document checklist emailed and chased (Account manager) - 9 days, mostly waiting 4. Manual ID and compliance check (Admin) - 1 day 5. Engagement letter drafted, corrected, sent (Account manager) - 3 days 6. First work begins - day 19 **Bottlenecks and root causes** 1. Document chasing: no single portal, so reminders rely on memory. 2. Triple data entry: systems are not connected, and errors then flow into the engagement letter. 3. Letter errors: drafted from scratch rather than from a template. **Options** | Change | Type | Impact | Effort | Cost | |---|---|---|---|---| | Single intake form feeding all systems | Eliminate | High | Medium | Low | | Automated reminder sequence | Automate | High | Low | Low | | Engagement letter template with merge fields | Simplify | Medium | Low | None | | Run compliance check in parallel with document collection | Reorder | Medium | Low | None | **Future state:** intake form on signature, automatic reminders, parallel ID check, letter generated from the form. **Pilot (2 weeks):** use it for the next 8 clients; target 10 days from signature to first work; track time, errors and client feedback.

Why it works

Asking for root causes and an eliminate-first ordering stops the model from simply recommending software for every problem. Measure cycle time for a week before and after to prove the gain.

Licensed CC0 (public domain) Version 1 · history