Service pillar · Bottlenecks & Rhythm
More capacity will not fix a waiting queue
Find where work stalls. Build the rhythm that keeps it moving.
At a glance
- The problem
- Work waits between teams while ownership and priorities remain unclear.
- What we do
- We follow real jobs, measure delays and agree a light operating cadence.
- What you leave with
- A ranked constraint list, named owners and a metric board your team reviews.
Illustrative days by stage: Brief 1 work, 0.5 wait; Scheduling 0.5 work, 9 wait; Delivery 3 work, 1 wait; Review 1 work, 2 wait. Scheduling is the longest wait.
Scopetwo-week bottleneck audit
Scopethree prioritised constraints
Scopesix operational measures
What the work looks like
The loudest complaint may not be the constraint
A team can blame delivery while the queue sits before kickoff. We follow a customer, a project and a new hire, then rank waiting and rework against effort.
- Work-path map
- Waiting and rework measures
- Ranked constraint readout
Scope: two-week bottleneck audit. Week one follows a customer, a project and a new hire. Week two measures waiting and rework, ranks constraints and delivers a readout.
A cadence should produce decisions, not updates
Ambiguous ownership lets the same problem return every week. We name accountable owners and set reviews that decide what changes next.
- Ownership register
- Operating review agenda
- Improvement pipeline
Daily check-in
Illustrative duration: 10 mins
Team lead
What needs unblocking today?Weekly review
Illustrative duration: 30 mins
Workflow owner
Which constraint comes first?Monthly metrics
Illustrative duration: 45 mins
Metric owners
Which process needs adjusting?Quarterly reset
Illustrative duration: 90 mins
Founder and leads
What should we stop or start?Illustrative cadence: daily 10 minutes, team lead, unblock today; weekly 30 minutes, workflow owner, prioritise constraints; monthly 45 minutes, metric owners, adjust the process; quarterly 90 minutes, founder and leads, reset priorities.
Measure the process people can influence
A large dashboard can hide the few signals that matter. We choose a small set of measures with an owner, a baseline and a review cadence.
- Metric definitions
- Baseline and review board
- Improvement benchmark
Example metric · Illustrative
Quote turnaround
Example metric · Illustrative
Enquiry response
Example metric · Illustrative
Time to first output
Example metric · Illustrative
Handover defects
Example metric · Illustrative
Founder approvals per week
Example metric · Illustrative
On-time delivery
Six example metrics with illustrative trend lines, not measured results: quote turnaround, enquiry response, time to first output, handover defects, founder approvals per week and on-time delivery.
Illustrative scenario
Scheduling, not delivery, holds the queue
Situation
A startup plans to hire into delivery, but projects wait nine days for a founder-confirmed kickoff date.
Approach
Follow the work for two weeks and move scheduling to the delivery lead with a clear rule set.
Outcome
9 days waiting → owned scheduling
Illustrative: nine days of scheduling wait becomes a delivery-lead decision, without adding a delivery hire.
A composite of patterns in growing teams, not a named client
How we would start
Agree the constraint before committing to the work
Start with an Operational Diagnostic, or frame the challenge with your free Vision Board.
Diagnose Prioritise Build Hand over