download dots

🚦 Find the Bottleneck in Your Process

Use answer-first prompts to design data models, approval matrices, executive reviews, portfolio risk systems, job costing, cash scenarios, vendor SLAs, commission trackers, retention dashboards, and customer health scorecards. Each prompt asks for the operating rules and evidence needed before generating an app or workflow.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Find the Bottleneck in Your Process

Copy

Everything takes too long and everyone blames a different part of the process. Build me a bottleneck analysis app. Define the stages a piece of work passes through, and for every item record the time it entered and left each stage, separating time actually being worked from time simply waiting. Show average and worst-case time per stage, the split between working and waiting, and the number of items queued at each stage over time, since a growing queue is what really identifies a constraint. Show throughput for the whole process and what it would become if a given stage were improved. Add an AI agent that reviews the data and states plainly which stage is the constraint, how much waiting time sits in front of it, what improving it by a realistic amount would do to overall throughput, and warns me where improving a non-constraint stage would change nothing at all. Automate two things: a scheduled weekly report on stage times and queues, and an alert when a queue at any stage grows beyond a threshold. Two logins: a stage owner who sees their own stage, and an operations owner who sees the whole flow.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Find the Bottleneck in Your Process

Measure working and waiting time per stage with queue lengths to identify the true constraint on throughput.

// the spark catches · intelligence awakens · the answer unfolds

Improving a stage that is not the constraint changes nothing. This measures waiting time at every stage so the real bottleneck is a fact rather than an opinion.

What's Included

  • Time at each stage separated into working and waiting.
  • Queue length per stage which is what reveals the constraint.
  • The constraint identified rather than argued about.
  • An assistant that says what would improve throughput most.

How To Use

  1. Separate working time from waiting time. Waiting is where the answer is.
  2. Measure queue length, not just duration. Queues point at the constraint.
  3. Improve only the constraint. Everything else changes nothing.
  4. Re-measure after any change. The constraint moves.

Feed it from process cycle time, and act with continuous improvement.