Isolate the primary constraint in an operational workflow

Pinpoint the single limiting bottleneck in a multi-step process so your team avoids wasting effort on non-constraining tasks.

You getStage-by-Stage Flow Table, identified Bottleneck and local Distractions

Prompt

Prompt
Act as an operations research lead applying the Theory of Constraints. Analyze the workflow steps described below to find the single primary bottleneck dictating total system throughput.
- Map out each operational stage, noting queue times, processing duration, and handoff delays.
- Identify which step maintains the highest work-in-progress inventory or longest idle wait time.
- Distinguish between true system constraints and local inefficiencies that do not affect overall cycle time.
- Propose two operational changes to exploit or elevate the true bottleneck immediately without buying new tools.
Output format:
1. Stage-by-Stage Flow Table (Stage Name, Cycle Time, Queue Status)
2. Identified Bottleneck (named step with root justification)
3. Local Distractions (steps that look slow but do not constrain total output)
4. Immediate Relief Actions (two concrete operational steps)
Here is the workflow description:

Example output

Example for: marketing content production workflow from brief to publication

  1. Stage-by-Stage Flow Table
  • Brief Submission: 1 business day cycle; 0 items queued.
  • Draft Copywriting: 3 business days cycle; 2 items queued.
  • Legal & Compliance Review: 6 business days cycle; 14 items queued.
  • Design & Asset Creation: 2 business days cycle; 1 item queued (idle waiting on legal).
  • CMS Publishing: 0.5 business days cycle; 0 items queued.
  1. Identified Bottleneck
    Legal & Compliance Review is the primary constraint. It has the longest cycle time (6 days) and holds the largest work-in-progress backlog (14 assets). Every other team works faster than legal can clear items, meaning any effort spent speeding up copywriting or design simply piles up more drafts waiting outside legal.
  2. Local Distractions
  • Draft Copywriting: Stakeholders complain writers take 3 days per piece, but writing faster only bloats the compliance queue further.
  • CMS Staging: Formatting takes half a day, but the publisher sits idle 60% of the week waiting for approved copy.
  1. Immediate Relief Actions
  • Subordinate input: Institute a pre-submission checklist for writers so legal receives zero drafts with missing disclaimers or unverifiable claims.
  • Exploit capacity: Establish a fast-track lane where standard blog updates bypass full legal review and receive quick sign-off based on pre-approved messaging templates.
Written by AI from this prompt. Your results will vary.

Paste your process documentation, ticket handoff notes, or step-by-step pipeline details directly after the prompt in ChatGPT, Gemini, or Claude. For a deeper check, ask the model what happens to downstream capacity if the primary bottleneck's output doubles.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Critical Thinking & Decisions