Identify a Bottleneck and Propose an Improvement
8 weeks · 0 milestones
Identify a real bottleneck in a real operational process using data — time measurements, error rates, queue lengths, or throughput metrics — and propose a specific improvement with a before/after metric plan that defines what success looks like. The deliverable is a bottleneck analysis document with the supporting data and an improvement proposal with measurable targets. Proof requires review by an operations professional who can confirm that the identified bottleneck is real and the improvement proposal is technically sound.
Milestone map
Milestone map
3 milestones
Select a real operational process in an organisation you have access to. Map the end-to-end process, measure throughput and capacity at each stage, and identify the primary bottleneck using the Theory of Constraints (TOC) or a compatible framework (value stream mapping, Little's Law analysis). The bottleneck must be identified with data — throughput rates, queue depths, or cycle times — not through intuition.
Proof required
Submit: (a) a process map for the chosen process (minimum 8 steps, with throughput rates or cycle times at each stage), (b) a bottleneck identification document showing the specific data (queue depth, WIP, or cycle time variance) that identifies the binding constraint, and (c) confirmation from a process owner or manager that the process and data are real and that the bottleneck identification aligns with operational experience.
What gets checked
- Process map shows actual measured throughput rates — not estimated or assumed values
- Bottleneck is identified with specific data — not qualitative judgement alone
- Process owner confirmation from a named stakeholder