Requests cross departments without clear decision ownership.
04BUSINESS OPERATIONS & PERFORMANCE / OPERATIONAL IMPROVEMENT
The work is hard enough without the unnecessary steps.
Clarify processes, responsibility and the rhythm of execution so the organization spends less energy navigating itself.
BEYOND THE SERVICE LIST
A workaround that repeats every week is a signal that the operating design deserves attention.
THE DECISION BEHIND THE WORK
The process on paper may not be the process anyone follows.
Operations drift as companies grow. Teams develop workarounds, exceptions become routine and information passes through people who were never formally assigned to own a handoff. A process can appear stable because employees continually compensate for its weaknesses.
Improvement begins by following actual work rather than accepting an organizational chart as a process map. We examine the trigger, sequence, waiting time, rework, decisions and outputs. A change should make the work easier to manage without removing controls that protect safety, quality or customer experience. Process approaches such as plan-do-check-act reinforce that improvement requires review after implementation, not only a redesigned diagram.
THE OPERATING REALITY
Friction often appears normal because everyone has adapted to it.
Workarounds can become the unofficial process. We observe actual handoffs and decisions before proposing change, then test improvements against frontline reality.
Repeated errors are handled individually rather than fixed at the source.
Managers lack a reliable way to see capacity, exceptions or bottlenecks.
WHERE WE FOCUS
Simplify the process without losing necessary control.
Understand what happens, identify the constraint, design a better path and establish a routine to keep it working.
Current-state mapping
Follow work through real steps, delays, exceptions and owners.
Constraint analysis
Locate rework, waiting, ambiguity and capacity mismatches.
Process and role redesign
Clarify decisions, handoffs, standards and supporting tools.
Implementation cadence
Establish accountability, measures and review points for adoption.
An operating handoff map
Find where work waits between owners.
The largest delay can be hidden in a queue, rework loop or approval transfer rather than the activity itself.
DECISIONEVIDENCE TO MAKE VISIBLE
Intake
What triggers the work and what must be complete?
Demand, entry criteria and variationTransfer
Where are decisions or materials waiting?
Queue, rework, exception and ownerClosure
What proves the work was finished correctly?
Acceptance, feedback and control checkWhat the first working output might be
Possible first output: a current-state map with measurable bottlenecks and a controlled improvement trial.
Important limitation: Local efficiency can worsen total performance when another constraint controls throughput.AN EVIDENCE-LED REVIEW
Find the constraint before redesigning everything.
These are useful lines of inquiry, not a universal checklist. The specific evidence and scope depend on the business context.
Flow
Where does work wait, repeat or change hands unnecessarily?
Observe actual steps, queues, exceptions and cycle time.
Ownership
Who makes the decision when the normal path breaks?
Map authority, handoff rules and escalation.
Sustainability
Will the new process be used when business is busy?
Test training, controls, measures and review cadence.
ILLUSTRATIVE OPERATING SITUATION
An onboarding process with four unofficial versions.
This is a hypothetical example for explanation. It is not presented as a client engagement or result.A business has one documented onboarding procedure, yet four teams maintain separate checklists. The service team often receives incomplete information and asks sales to clarify details after work has begun. Managers blame individual carelessness, but the process itself contains incompatible definitions of complete.
The improvement might start with one agreed intake standard, a clear receiving owner, exception rules and a small pilot before broad rollout. The objective is not to eliminate every variation but to prevent avoidable rework and make necessary variation explicit.
BOUNDARIES AND RESPONSIBILITY
A local gain can move the bottleneck.
Operational redesign can affect people, contracts, systems and controls. Changes should be tested at an appropriate scale, with safety, regulatory and service requirements considered before rollout.
Independent reference: ASQ on the Plan-Do-Check-Act cycle ↗. This source informs the topic; it does not endorse Avermont Partners.
QUESTIONS WORTH CLARIFYING
Where does the entire process wait?
An informed first conversation is often more useful than a prematurely detailed proposal.
Do we need a major transformation program to improve a process?
Often not. A bounded problem with clear ownership and evidence can be a more effective starting point than a broad program whose dependencies are poorly understood.
Should every process be standardized?
Only to the degree that standardization supports quality, coordination and the actual requirement. Some customer or market differences justify controlled variation.
What evidence should we collect?
Cycle time, waiting, rework, error patterns, capacity and frontline observations can help, provided the measures are clearly defined and used for decisions rather than surveillance.
THE QUESTION WORTH ASKING
Which recurring workaround has become part of the job?
Useful progress begins with a clear requirement, the right evidence and ownership of the next decision.
View all Operations capabilitiesTHE NEXT CONVERSATION
Make the process easier to run.
Share the situation, constraints and intended outcome. We can then assess whether a focused engagement would be useful.
Discuss an Engagement