Anonymous Bottleneck Analysis
A sample bottleneck analysis showing how ADA turns a messy operating complaint into a practical workflow candidate.
Direct Answer
A bottleneck analysis should translate frustration into a workflow decision: where work gets stuck, why it gets stuck, what evidence is missing, who owns the fix, and whether AI should help.
How to use this
- Step 1: Write the complaint exactly as the team says it.
- Step 2: Translate the complaint into where work gets stuck or loses context.
- Step 3: Separate symptoms from root causes.
- Step 4: Decide whether AI should help, whether simple automation is enough, or whether the process needs cleanup first.
- Step 5: Choose a better metric than the complaint itself.
Anonymous example
- Complaint: Sales says leads are low quality, but marketing says sales responds too slowly.
- Observed bottleneck: Inbound requests lack fit, urgency, source context, and duplicate history before assignment.
- Root cause: The team treats lead capture, qualification, and routing as one manual step.
- AI opportunity: Prepare a fit summary, missing-info list, duplicate check, and route recommendation.
- Human owner: Sales lead reviews high-value, unclear, or disqualified inquiries.
- Better first metric: Time to qualified owner response, not raw lead volume.
Worksheet prompts
- Complaint: What does the team keep saying is broken?
- Observed bottleneck: Where does work wait, get routed poorly, lose evidence, or require repeated follow-up?
- Root cause: Is the problem speed, evidence, ownership, quality, priority, or decision authority?
- AI opportunity: Can AI prepare a summary, score, draft, route, check, or exception packet?
- Non-AI fix: Would a better form, rule, owner, checklist, or CRM field solve the problem faster?
- Better metric: What should improve if the bottleneck is actually fixed?
Why anonymous examples work
They show the thinking without pretending to be client case studies. The point is to demonstrate operating judgment: problem, evidence, owner, review point, and metric.
What AI should not solve
AI should not paper over unclear ownership, weak offers, poor intake forms, or missing follow-up discipline. It should make the bottleneck visible and prepare better owner decisions.
How this becomes a workflow
The bottleneck becomes a candidate workflow only after the trigger, inputs, owner, review point, stop rule, and measurement are defined.
Quality bar
- The analysis does not assume AI is the answer.
- The bottleneck is tied to a repeated workflow.
- The proposed metric is closer to revenue, speed, quality, or rework than vanity volume.
- The owner is named before the workflow is designed.
- The recommendation distinguishes process cleanup, simple automation, and AI assistance.
Where This Helps
Research basis
- NIST AI RMF: Supports evaluating AI risks and context before use.
- Microsoft Responsible AI Resources: Supports impact-aware design rather than tool-first implementation.
- OWASP Top 10 for LLM Applications: Highlights practical LLM application risks that should be considered before turning a bottleneck into automation.
Related Resources
FAQ
- What is a bottleneck analysis?: It is a practical review of where work slows down, loses context, creates rework, or misses revenue.
- Is every bottleneck an AI opportunity?: No. Some bottlenecks need clearer ownership, better forms, better rules, or simpler automation before AI.
- What makes it useful?: It converts a vague complaint into a workflow candidate with evidence, owner, review point, and metric.