Operations
The second dimension of the Sentinel Mandate. Where the time and the money actually go, and what a bottleneck is costing you before it is fixed.
What is an operational bottleneck?
An operational bottleneck is the step in a process that sets the pace for everything after it. Work arrives faster than that step can clear it, so a queue forms in front and the rest of the operation waits behind, regardless of how efficient those later steps are.
This is why adding effort elsewhere so often changes nothing. Improving a step that is not the constraint moves work into the queue faster. The output of the whole process is governed by its slowest point, and until that point moves, nothing downstream can.
What is business process mapping?
Business process mapping is the exercise of writing down how work actually moves through a business, step by step, with the handoffs, waits and rework included. The value is in the gap it exposes between how a process is believed to run and how it runs.
The map is not the deliverable. It is the instrument that makes a bottleneck visible, because a constraint is rarely where people assume it is. It sits at the handoff nobody owns, or in the approval that waits on one person.
Putting a number on the hidden cost
A bottleneck has a price, and it is measurable: the labour idling behind it, the orders delivered late, the rework it causes downstream, and the revenue that never arrives because capacity is capped. Costing each one is what turns a list of complaints into a decision.
Without a number, every operational problem looks equally urgent and the loudest one wins. With numbers, the sequence becomes obvious and frequently surprising.
Five quantified gains, ranked
The analysis ends with five operational gains, each quantified by expected return and estimated effort, ranked so that the order of work is decided before anyone starts.
Some of the five are usually worth doing this month with no investment. Others are worth knowing about and deliberately not doing yet. Both answers are useful.
What this dimension covers
- A map of your critical processes, including handoffs, waits and rework
- The bottlenecks, and what each one costs in labour, delay and lost capacity
- Five quantified operational gains
- A ranking by expected return against estimated effort
FAQ
How long does process mapping take?
For a mid-market business the critical processes can usually be mapped in days rather than weeks, because only the processes that carry revenue or risk need this level of attention. Mapping everything is a common way to produce a document nobody reads.
Will this disrupt the team while it is happening?
It requires time from the people who do the work, since they are the only reliable source for how it actually runs. It does not require the operation to stop.
What if the bottleneck is a person?
It often is, and usually the owner. That is a structural finding rather than a personal one, and it connects directly to the team dimension of the mandate.
Do you implement the fixes?
The mandate is a diagnostic and ends with a ranked plan. We operate, so we can be engaged to execute it afterwards, but the two are separate decisions and the diagnostic stands on its own.
Operations problems are usually visible before they are measured
Most owners can name the bottleneck. Far fewer can say what it costs, which is why it stays.