Decision bottlenecks are some of the highest-value areas for improvement.
Work doesn't just slow down because tasks take a long time. It slows down because people are waiting—for approvals, for decisions, for information that someone else has to provide.
This step helps you identify those waiting points and understand their impact.
How to Identify Decision Bottlenecks
Decision bottlenecks show up naturally during interviews. Your job is to recognize them, name them clearly, and understand their cost.
Step 1: Listen for "Stall Language"
While reviewing interviews, look for phrases like:
- "We have to wait for approval..."
- "This needs to be reviewed before moving forward..."
- "I can't continue until I hear back..."
- "Someone has to sign off on this..."
These phrases almost always point to a decision bottleneck.
Simple example: A support agent says, "I can't close a ticket until a manager reviews it." Clear approval bottleneck.
Complex example: A project manager says, "We wait on finance to confirm pricing, but they need updated data from sales, which usually comes late." Multi-step bottleneck involving multiple teams.
Step 2: Identify the Decision Owner
For each bottleneck, write down:
- Who makes the final decision
- Who provides the information needed for that decision
If the answer is unclear or changes by situation, flag it. Unclear ownership is itself a bottleneck.
Step 3: Define the Decision Trigger
Ask:
- What starts this decision?
- Is it a new request, an exception, a report, or an error?
This helps you understand how often the decision occurs.
Step 4: Estimate the Delay
Determine:
- How long the decision usually takes (minutes, hours, days)
- How often it happens (daily, weekly, monthly)
Simple example: A daily approval that takes 15 minutes still adds up.
Complex example: A weekly pricing decision that takes 2–3 days can delay deals and revenue.
Step 5: Check the Information Problem
Most slow decisions aren't caused by people. They're caused by bad or missing information.
Ask:
- Is the data incomplete?
- Is it spread across tools?
- Is it outdated or hard to trust?
If the decision would be fast with better information, mark it as high-value.
Step 6: Note the Business Impact
For each bottleneck, write what it causes:
- Slower delivery
- Missed deadlines
- Customer frustration
- Extra back-and-forth
- Lost revenue or margin
Avoid vague language. Be specific.
What You Should Have Now
✅ Decision Bottleneck List with:
- Decision description
- Decision owner
- Trigger
- Delay time
- Frequency
- Business impact
Quality Check
- Bottlenecks are written in plain language
- Each one is tied to a real delay
- Simple and complex examples are clearly separated
- Impact is described in business terms, not opinions
Next Step: With bottlenecks identified, you're ready to inventory all the tools and systems your business uses.
Need help identifying real opportunities? See our audit process → OpsSystem.ai