Decision 1 of 6
Messy business complaints
Anonymous Bottleneck Analysis
Use this to decide whether a complaint is an AI opportunity, process cleanup, or simple automation issue.
Step 1
Answer guided questions
Step 2
Get verdict
Step 3
Use result in strategy session
Decision Tool
Turn a workflow idea into a yes, no, or fix-first call.
4-6 minutes6 decisions
Complaint
Anonymous example
Example output from the ADA method.
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.
Why anonymous examples work
They show the thinking without pretending to be client case studies. The point is to demonstrate how a vague operating complaint becomes a concrete revenue workflow candidate: what is leaking, what it is costing the business, whether AI can recover it, and the number that should move.
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
Use these checks before calling the workflow ready.
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
Use it before build decisions get expensive.
Revenue leak review
Operations triage
Sales and marketing handoffs
Service delivery delays
Research Basis
Built against practical AI risk and quality standards.
NIST AI RMFSupports evaluating AI risks and context before use.Microsoft Responsible AI ResourcesSupports impact-aware design rather than tool-first implementation.OWASP Top 10 for LLM ApplicationsHighlights practical LLM application risks that should be considered before turning a bottleneck into automation.
Related Resources
Read this with the workflows and service pages it supports.
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.
Next Step
Use this result on a real workflow.
Bring the bottleneck, current handoff, and the result you want to improve.