The executive view
A process can look successful inside every department and still fail the person it serves. Before approving a redesign, follow one outcome across the business. Then give someone the authority to improve the whole journey.
Consider a customer asking when an order will arrive. Sales has entered the request. Finance has completed its review. Operations has scheduled the work. Each team can point to a completed task. The customer still has no reliable answer.
This hypothetical situation exposes a leadership question: who is responsible for the result between the departmental milestones? Adding a dashboard or asking every team to work faster will not settle that responsibility.
Our starting point for operational improvement is the work itself: what somebody needs, how the organization responds, and what it takes to finish. Departmental reports belong in that investigation. So do the handoffs, exceptions and improvised fixes those reports may not describe.
1. Define what finished means.
“Improve onboarding” is a theme. “A new customer can place a first order without repeating information already supplied” describes an outcome people can examine. Specify the starting event, the intended recipient and the conditions that count as completion.
Keep the boundary wide enough to include the result. Ending the review when a team closes its ticket can hide work passed to another department or returned to the customer. Ask what remains unresolved after the organization considers its part complete.
Then name the decision the investigation must support. Leadership might need to change an approval rule, transfer responsibility or fund a system change. A useful investigation narrows that choice.
2. Follow the ordinary case and the awkward one.
Ask employees to reconstruct a recent item using the records they actually used. Follow it through each handoff. Record who had the next action, what they needed, where the item waited and what caused it to return.
Include an exception. A routine case shows the intended route; a difficult one reveals who can make a decision when the route stops working. Examine workarounds with curiosity. A spreadsheet may be maintaining continuity that the official system does not provide.
A few examples establish questions, not prevalence. Compare them with the available records before treating one frustrating story as the dominant problem. Keep the investigation proportionate to the decision and the cost of getting it wrong.
3. Separate the delay from its explanation.
“The request waited three days for approval” is an observation. “We need more approvers” is a proposal. Missing information, ambiguous authority or a poorly timed review could produce the same delay and require different action.
For each constraint, write down what happened, the competing explanations and the evidence that would distinguish them. Bring the people on both sides of the handoff into that discussion. Leadership should resolve conflicting objectives; employees should not have to negotiate the organization's priorities one request at a time.
4. Improve the outcome, including its consequences.
Choose a change small enough to assess and meaningful enough to affect the problem. Define the expected improvement alongside what must be protected: accuracy, service commitments, employee capacity or necessary controls.
Hypothetical operating decision
An order team proposes removing a review to shorten turnaround. Before extending that change, test whether the review prevents errors that would otherwise reach fulfillment. An alternative could be earlier validation or approval by exception. Compare total completion time, correction work and unresolved cases. This is an illustrative scenario, not an Assuras client engagement.
Some decisions cannot wait for a pilot. A serious service interruption may require an immediate temporary measure. Make its limits explicit, appoint an owner and schedule the review that will replace the temporary response with a considered design.
5. Assign authority across the handoffs.
A process owner needs more than a name beside a metric. Specify which decisions that person can make, which require another leader's agreement and who resolves a disagreement. Otherwise, accountability can exceed authority.
Review completed outcomes and unresolved exceptions together. Keep a route for employees to report an obstacle and see its disposition. The management routine should reveal whether the new process works under everyday conditions, including changes in demand and staffing.
Our business practice efficiency practice connects this investigation to a bounded improvement plan. The fictional operational workflow map shows how handoff requirements and exception ownership can be made explicit.
For the next leadership meeting.
- The outcome
- What must the recipient be able to complete?
- The evidence
- Which ordinary and exceptional cases will we examine?
- The choice
- What decision should that evidence inform?
- The protection
- What must continue to work while we make the change?
- The authority
- Who can resolve a disagreement across the handoffs?
