Organizational Change Management: A Practical Playbook for Mid-Market Leaders

Mid-market change management has a fundamental constraint that enterprise change management doesn't: you don't have a dedicated change team. The VP of Operations who is leading the transformation is also running current operations. The HR leader managing the communications program is also managing daily HR operations. The change has to happen in parallel with the business — not instead of it.

This constraint shapes everything about how change management needs to work at the $50M–$300M level.

Phase 1: Diagnosis before prescription (Weeks 1–4)

Before any change program launches, you need a clear-eyed picture of three things: what specifically needs to change, who needs to change it, and what is currently preventing that change from happening. The organizations that skip this phase and go straight to solution design almost always end up solving the wrong problem. Spend four weeks doing structured interviews with your leadership team, your frontline managers, and a representative sample of the people who will be most affected by the change. You will learn things that are not in any slide deck or status report — and those things will determine whether the program succeeds or fails.

Phase 2: Build the coalition before you launch (Weeks 3–6)

No change program survives without a coalition of leaders who visibly support it. In mid-market companies, this coalition is typically small — four to six people across the leadership team — but its influence is disproportionate. Your job in this phase is to identify who those people are, get them genuinely aligned (not just publicly supportive), and give them the tools and language to lead the change in their own functions. A leader who understands the change and believes in it is worth ten communications campaigns.

Change management is a leadership competency, not a communications program. You can't communicate your way to behavior change. You have to lead people through it.

Phase 3: Design the change for the actual organization (Weeks 5–10)

The change program needs to be designed for your specific starting point — not for an idealized version of your organization. This means: process changes that account for your actual process maturity, not the process maturity you wish you had; training that meets people where they are, not where the design assumes they are; a timeline that reflects your actual organizational capacity, not an optimistic assumption about how fast people can absorb change while running the business.

The most common design failure in mid-market change programs is an implementation timeline built for a company with dedicated change resources. Adjust the timeline for the reality that your people are doing two jobs simultaneously.

Phase 4: Launch with a visible, credible win (Month 3)

The launch phase should be designed to deliver one visible, credible proof point within the first 60–90 days. Not a pilot. Not a proof of concept. A real operational result that the organization can see and that leadership can point to as evidence that the change is working. This early win has an outsized effect on organizational buy-in — it converts skeptics into observers and observers into supporters. Pick the win deliberately: it should be in an area where you have strong coalition support, where the change is well-designed, and where success is achievable within the timeframe.

Phase 5: Sustain through governance, not enthusiasm (Month 3 onward)

The most dangerous moment in a change program is when the initial launch energy fades and the hard work of sustaining the change begins. This is where most programs stall. The organizations that sustain change successfully do it through governance, not enthusiasm — weekly review cadences that measure behavioral change, not just activity; accountability structures that make backsliding visible and uncomfortable; and incentive alignment that rewards the new behavior rather than the old one.

Enthusiasm is not a governance mechanism. Weekly accountability is.

The COO's specific role in change management

In mid-market companies, the COO is typically the person who owns both the change program and the operations it's changing. This dual role is genuinely difficult — and it's the main reason that bringing in a fractional COO or a dedicated transformation lead is often the right call for major change initiatives. The person running current operations and the person designing the new operational model need to be in constant dialogue — and it's very hard to be both people simultaneously, especially for 12 months straight.