Process Bottleneck Analysis Chain

validated business chain v1.0.0 cc-by-sa

Block ID: ab9da81e-029b-40df-ac4f-ad63aa44531c

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. User assumes all responsibility for use.

Template

Analyze the operational process in {process_context} to find and fix the constraint limiting throughput, reasoning from the theory that a system's output is set by its bottleneck. (1) Map the process end to end as it actually runs, not as documented, capturing each step's capacity and the flow between them — because the real bottleneck often sits where no one looks, and optimizing a non-bottleneck step wastes effort entirely. (2) Identify the true constraint: the step with the least capacity relative to demand, revealed by where work piles up (inventory, queues, wait times) ahead of it. Confirm it, since teams routinely misidentify the bottleneck and improve the wrong station. (3) Recognize the governing principle: improving any step other than the constraint does not increase system output — it only builds inventory or idle capacity — so the constraint gets priority. (4) Exploit the constraint first (get maximum output from it without new investment: reduce its downtime, offload work it needn't do, ensure it's never starved), before spending to expand it. (5) Then subordinate the rest of the process to keep the constraint fed and flowing. (6) State the constraint, the reasoning that identified it, and the sequenced fix — noting that once relieved, the bottleneck moves, so the analysis is iterative rather than one-time. Flag where your capacity data is estimated rather than measured.

Analyze the operational process in {process_context} to find and fix the constraint limiting throughput, reasoning from the theory that a system's output is set by its bottleneck. (1) Map the process end to end as it actually runs, not as documented, capturing each step's capacity and the flow between them — because the real bottleneck often sits where no one looks, and optimizing a non-bottleneck step wastes effort entirely. (2) Identify the true constraint: the step with the least capacity relative to demand, revealed by where work piles up (inventory, queues, wait times) ahead of it. Confirm it, since teams routinely misidentify the bottleneck and improve the wrong station. (3) Recognize the governing principle: improving any step other than the constraint does not increase system output — it only builds inventory or idle capacity — so the constraint gets priority. (4) Exploit the constraint first (get maximum output from it without new investment: reduce its downtime, offload work it needn't do, ensure it's never starved), before spending to expand it. (5) Then subordinate the rest of the process to keep the constraint fed and flowing. (6) State the constraint, the reasoning that identified it, and the sequenced fix — noting that once relieved, the bottleneck moves, so the analysis is iterative rather than one-time. Flag where your capacity data is estimated rather than measured.

Variables

Name	Type	Required	Trust level
process_context		yes

operationsbottleneckthroughputchain-of-thought

Ratings

0.0

Overall (0)

0.0

Accuracy

0.0

Consistency

0.0

Clarity

0.0

Efficiency

Benchmarks

Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.

Submitted by James P FounderMod via mcp · 2026-07-18