Scaling exposes the limits of the systems that helped a business succeed in its earlier stages. Informal decisions, individual workarounds, and close personal coordination can carry a company a long way. But as teams, customers, and delivery complexity grow, those same habits can create delays, rework, inconsistent handoffs, and an executive team pulled into daily operational firefighting.
The challenge is that operational rigor can feel threatening when it arrives as a top-down mandate. Leaders need clearer workflows, better process visibility, and fewer bottlenecks. Employees and middle managers need confidence that improvement will make their work more workable, not turn them into cogs in a rigid system.
Overcoming resistance to process improvement starts with treating change as both an operational and a human challenge. Lean Six Sigma discipline can reveal where work slows down or fails. Human-centric change architecture helps people understand the purpose of the change, contribute to its design, and adopt it in practice.
The scaling paradox
The processes that support a company at $10M in revenue may not support it on the path to $100M. At a smaller scale, experienced people can bridge gaps through direct conversations and personal knowledge. As the organization expands, that approach becomes harder to sustain. A missed handoff between sales, delivery, operations, or customer support can affect both cycle time and the customer experience.
The executive response is often understandable: document the process, standardize the workflow, and hold people accountable. Yet a process introduced without context can be interpreted as a loss of autonomy or a signal that leadership does not trust the people doing the work.
That is the central scaling paradox. The business needs more structure, while the people who must operate within that structure may fear that it will remove the agility that made the company successful. The answer is not to avoid process improvement. It is to build enough operational discipline to scale while preserving the judgment, ownership, and feedback loops that allow teams to adapt.
For broader context on this transition, see Executive operational excellence: The $100M scaling guide.
Diagnosing employee resistance to process change
Employee resistance to process change is often labeled as stubbornness, complacency, or unwillingness to be accountable. That interpretation can lead leaders to push harder, communicate less, and deepen the divide they are trying to close.
A more useful starting point is to ask what the proposed change appears to mean to the people affected by it. Will it alter a role? Add reporting work? Reduce discretion? Expose a problem that someone has been managing informally? Will a manager be expected to carry a rollout without adequate time, authority, or support?
What executives perceive as resistance can be a response to uncertainty, perceived loss, or threats to psychological safety. As McKinsey’s discussion of organizational strain notes, change can trigger responses to perceived threats and loss. For process improvement, that means leaders should investigate the conditions around the rollout rather than assuming the workflow itself is the only issue.
Look for the rollout problem before blaming the people
Resistance may indicate that a process was communicated as an instruction rather than a shared operational problem to solve. It may also reveal a legitimate concern about an unintended consequence. For example, a team may understand the need to reduce turnaround time but see that a proposed approval step creates delay for an exception that is common in their part of the customer journey.
This does not mean every concern should halt the change. It means leaders need a disciplined way to distinguish between preference, risk, and useful frontline knowledge. Invite people closest to the work to identify failure points, test assumptions, and clarify where a standard process needs a defined escalation path.
Recognize the middle-management squeeze
Middle managers are frequently asked to translate executive priorities into everyday action while absorbing pressure from teams facing the practical realities of delivery. When a new workflow arrives without clear rationale, usable measures, or room to raise concerns, managers can become enforcers of rules they did not help shape.
That position is difficult to sustain. It also makes adoption less likely because the manager becomes associated with compliance rather than improvement. Leaders should treat this layer as a source of operational insight and a critical partner in the change effort.
Balancing operational efficiency with psychological safety
Psychological safety does not mean avoiding performance conversations or allowing every process to remain optional. It means creating conditions in which people can raise risks, question assumptions, and report problems without being punished for surfacing inconvenient information.
That environment is essential when refining a process. A dashboard may show that a handoff takes too long, but the people doing the work can explain whether the delay comes from incomplete inputs, unclear ownership, an exception path, or a system constraint. Without that explanation, leaders can optimize the visible symptom while leaving the cause untouched.
To balance operational efficiency with psychological safety, make the improvement effort explicit:
- State the operational problem. Describe the customer, quality, cash-flow, or delivery impact that needs attention.
- Define the non-negotiable outcome. Teams need to know what must improve, such as reducing rework or shortening a specific cycle time.
- Invite evidence from the workflow. Ask people to identify friction, failure demand, and unintended consequences before finalizing a new standard.
- Test changes in manageable increments. A pilot creates evidence and gives teams a practical way to refine the design.
- Close the feedback loop. Explain what was changed, what was not changed, and why.
This approach replaces the fear of micromanagement with useful visibility. Measurement becomes a way to understand work and remove obstacles, rather than a mechanism for watching individuals. Human-centric process improvement is not less rigorous; it is more likely to identify the operational reality that a spreadsheet alone cannot show.
Empowering middle management to drive continuous improvement
Cross-functional friction rarely sits within one team. It appears at the points where work changes hands: when a commercial promise becomes an operational commitment, when an exception requires a decision, or when customer information is passed from one function to another.
Middle managers are the make-or-break layer in these moments. They can either relay targets downward or help teams understand how their work affects the wider value stream. The second role is more valuable during scaling because it connects strategy, operational data, and frontline reality.
A strategic business coach does not simply ask whether tasks were completed. They help teams ask better questions: What is blocking first-pass quality? Where does the customer experience become fragmented? Which handoff creates avoidable rework? What decision can be made closer to the work without losing appropriate control?
This requires executives to equip managers with a clear mandate, access to relevant process measures, and permission to surface constraints. It also requires a shift in how performance conversations are conducted. Instead of using metrics solely to explain why a target was missed, use them to guide problem-solving across functions.
For a closer look at the customer impact of broken workflows, read The hidden cost of cross-functional handoffs in service delivery.
Integrating Lean Six Sigma with human-centric change architecture
Lean Six Sigma offers a disciplined way to define problems, examine variation, identify waste, and improve process performance. Used well, it does not require a company to copy a large-enterprise operating model. A scaling SME needs methods that are proportionate to its complexity and adaptable to its people and customers.
The practical task is to combine data-driven process visibility with an approach to change that accounts for behavior. A workflow is not truly improved because a new diagram exists. It is improved when the people involved can use it consistently, understand the reason for it, and raise evidence when it no longer reflects reality.
Track adoption alongside process performance
Cycle time, first-pass yield, rework, and other operational measures show whether the process is moving in the intended direction. They do not, on their own, show whether a new way of working has become part of normal practice.
Leaders should therefore track behavioral adoption alongside operational performance. This can include whether teams are using the agreed decision path, whether managers are reviewing the right measures, whether cross-functional issues are being raised early, and whether recurring workarounds are appearing. The goal is not surveillance. It is to identify where the designed process and the lived process have diverged.
Digital and AI-enabled analysis can assist with visibility and pattern recognition, but they should remain facilitators for human judgment. A metric can signal variation; it cannot independently determine why people are working around a process or what trade-off best protects the customer journey.
Use an SME-specific improvement rhythm
A practical improvement rhythm can be simple:
- Map the current value stream with the people who work in it.
- Choose one operational problem with a clear customer or business consequence.
- Define a small set of measures for process performance and behavioral adoption.
- Run a pilot, review the evidence, and adjust the workflow with frontline input.
- Give middle managers responsibility for coaching the new practice across handoffs.
- Standardize what works while retaining a clear route for exceptions and future improvement.
This rhythm creates rigor without confusing standardization with rigidity. It gives leaders a repeatable way to drive continuous improvement in resistant teams while preserving the capacity to learn and adapt.
Making change something people can own
Process improvement becomes sustainable when people can see how it helps them deliver better work, solve recurring problems, and protect the customer experience. The leadership task is to set the direction and the measures while making room for the operational knowledge required to make the change work.
Oliemuller combines rigorous Lean Six Sigma Black Belt methodology with human-centric change architecture for organizations navigating the critical $10M to $100M scaling phase. The approach focuses on strengthening operational systems while developing middle management into strategic business coaches who can carry improvement into everyday execution.
For leaders who want to embed that capability over time, Building a continuous improvement culture: CEO guide provides related perspective.
Discuss your operational bottleneck confidentially
If your company is scaling and recurring operational fires are pulling leadership away from strategic work, book a free, confidential 30-45 minute exploratory consultation with Oliemuller. It is an opportunity to discuss the bottleneck, the customer impact, and whether a human-centric operational improvement approach fits your situation.
