# Find a bottleneck and improve a process

Lean-style analysis of a process: waste, bottlenecks, root causes, and an improvement plan.

- Topic: Projects & Operations
- Framework: RCTFVV
- Level: Advanced
- Tags: Sales, Rewrite & Edit, Analyze, Fill-in Template, Step-by-step
- Source: https://www.thinkwithprompt.com/prompts/find-a-bottleneck-and-improve-a-process

## Prompt

```text
Role: Act as a process improvement / Lean lead analysing an end-to-end process.

Context: The process, its boundaries and its business objective: [PROCESS_OBJECTIVE]. Current performance (lead time, process time, wait time, first-pass yield, rework, cost, demand rate/takt): [PERFORMANCE]. Step-level data or a walk-through: [STEP_DATA]. Known pain points and prior attempts: [PAIN_PRIOR]. Constraints (system, headcount, regulatory): [CONSTRAINTS].

Goal: Identify the true constraint and the highest-value waste, and produce an improvement plan that shortens lead time and improves quality with the least disruption.

Task: Produce: (1) a value-stream summary - each step's process time, wait time, and yield, the total lead time vs value-add time, and the takt vs cycle time picture; (2) the bottleneck / constraint and why it is the constraint; (3) the top wastes (waiting, rework, over-processing, handoffs, motion, inventory) with their root causes traced (5-whys), evidenced from the data; (4) a sequenced improvement plan - what to do first (relieve the constraint), then flow and quality improvements - each with expected effect on lead time / yield / cost, effort, and owner; (5) how to measure and sustain the gains.

Constraints: Focus improvement on the constraint first - improvements elsewhere will not move lead time. Root causes must be evidenced, not asserted. Estimate effects as ranges with the assumption. Respect the constraints - no recommendation that needs headcount or system change that is ruled out.

Examples: Waste row: 'Wait before step 4: avg 2.3 days (48% of lead time). Root cause chain: batch approval once daily <- approver also does [other role] <- role not backfilled. Fix: move to continuous approval with a delegate -> est. -1.5 to -2 days lead time.'

Format: Sections: Value-stream summary (table) | Constraint & why | Wastes & root causes | Improvement plan (sequenced table) | Measure & sustain. ~700 words.

Verification: Show the lead-time vs value-add math; for each root cause state the data point that supports it and where the chain is inference.

Validation: Challenge as an operator on the line: is the constraint diagnosis right, and would the first change actually help or just shift the queue? Adjust if it shifts the queue.
```

## What to fill in

- PROCESS_OBJECTIVE
- PERFORMANCE
- STEP_DATA
- PAIN_PRIOR
- CONSTRAINTS
- other role

Free to copy and use. From ThinkWithPrompt (https://www.thinkwithprompt.com/), a library of 2,663 curated AI prompts.