Observable condition
Sales improves response targets. Finance tightens controls. Operations maximises utilisation. Procurement batches work for efficiency. Support protects its queue. Each function can show a reasonable local decision, yet customers wait longer, handoff queues grow or the overall process needs more coordination than before.
Realisation
A company is not experienced by customers as separate departments. Work moves horizontally across those departments from demand to fulfilment, service, billing and resolution. If every function optimises only its own measure, the result can be a collection of locally efficient steps connected by increasingly inefficient waits and handoffs.
Identification
This is a local-optimization and end-to-end operating-model problem.
Diagnosis
The mechanism is usually structural: departmental metrics reward local utilisation or risk reduction, queues are invisible outside the function, handoff costs belong to nobody and there is no accountable owner for end-to-end flow. Lean value-stream thinking explicitly distinguishes improving the whole flow from merely optimising individual parts. The operating problem is not that departments are behaving irrationally; it is that the system can reward rational local behaviour that produces a weaker total outcome.
Commercial impact
The value wrapper is cycle time, margin, customer experience and strategic capacity. Waiting accumulates between teams. Managers spend time negotiating priorities. More work-in-progress can exist without more completed value. Technology investments may accelerate individual steps while leaving the cross-functional constraint untouched.
Common misidentification
The usual response is to ask each department to “work better together”. Collaboration matters, but it cannot compensate indefinitely for incentives, measures and workflows that optimise different objectives. If the system rewards local success, recurring cross-functional friction is a design signal.
Possibility
A stronger model adds an end-to-end view alongside functional accountability. The business can define the value stream, measure total cycle time and completion, make queues visible, assign ownership across handoffs and evaluate local improvements by their effect on the whole process.
Intervention
Choose one important customer or revenue journey and map it from trigger to completed outcome. Record actual processing time, waiting, handoffs, queues, rework and ownership. Then compare departmental metrics with what the end-to-end customer or commercial outcome requires. Improvement priorities should follow the constraint in the whole flow, not simply the loudest local pain.
Practical diagnostic questions
- Who owns the complete process across departmental boundaries?
- Which local metrics can improve while total cycle time worsens?
- Where does work wait between otherwise efficient teams?
- Can leadership see work-in-progress and queues across the whole flow?
- Are improvement projects measured by local output or completed customer value?
Bottom line
If every department can prove it is improving while the overall process gets worse, the missing layer may be end-to-end operating ownership.
Sources and further reading
- Lean Enterprise Institute — value-stream mapping overview
- Lean Enterprise Institute — local optimization and value-stream transformation