3 IMOs, 3 Industries

The first time I set up an Integration Management Office, I made a PowerPoint deck with fourteen slides describing the governance model. Roles and responsibilities. Escalation paths. A RACI matrix that looked like a spreadsheet had a child with a traffic light. I presented it to the steering committee. They nodded politely. Then they went back to doing whatever they were already doing.

The IMO existed on paper for six weeks before anyone used it for an actual decision.

That was over a decade ago. Since then I’ve built IMOs in specialty chemicals, pharmaceuticals, and a carve-out that was technically a divestiture but felt more like founding a startup inside a Fortune 500 company. The structure changed every time. The mistakes, unfortunately, did not. They just showed up wearing different clothes.

Here’s what I learned from three IMOs across three industries, and what I’d tell someone standing up their first one tomorrow.

IMO #1: The Specialty Chemicals Merger

Twenty-two thousand employees. Two companies that made similar products for similar customers and had been competing for decades. The acquirer had 16,000 people. The target had 6,000. The thesis was straightforward: combine the organizations, eliminate redundancies, capture synergies. The execution was not straightforward at all.

I came in to lead the HR transformation and ended up building the technology that runs the entire integration. Not because that was the plan. Because the plan assumed a team of four to six analysts would handle workforce tracking, synergy calculations, and executive reporting. By month two it was clear that team wasn’t coming. The budget had other priorities. So I built a platform that replaced them.

That sounds impressive in a resume bullet. In practice it meant I spent three months writing code at midnight so that the steering committee could see accurate numbers at 9 AM. The IMO’s authority came not from a governance charter or an executive sponsor’s email. It came from the fact that every leader in the organization, from the CHRO to the country HRBPs, opened the same system every morning and saw the same data.

This was mistake number 1, by the way, turned into a lesson. If your IMO depends on people voluntarily sending you updates, your IMO is a suggestion box. If your IMO owns the system where the work actually happens, updates aren’t a request. They’re a byproduct of doing the job.

The specialty chemicals IMO taught me that authority is a technology problem as much as it is an organizational one. The governance structure matters. The executive sponsor matters. But what matters most is whether the IMO controls the information that leaders need to make decisions. If you’re chasing people for status updates, you’ve already lost.

What worked

Single source of truth, enforced by tooling. Nine different persona types (executives, HRBPs, finance, vendors, country leads, external reviewers) all operating in one system. When the CFO wanted synergy numbers, they came from the same place the HRBP used to track dispositions. No competing spreadsheets. No “my numbers say something different” conversations.

Multi-level org design in the same platform as workforce planning. L1 through L3+ decisions happened in a tool that was directly connected to the employee data. You couldn’t design a future-state org without seeing the people who would fill it. This sounds obvious. It is not how most integrations work. Most integrations have an org design workstream that produces boxes on slides and a separate workforce planning workstream that produces names in spreadsheets, and nobody reconciles them until month four when the numbers don’t match and everyone is confused.

Disposition tracking with full audit trail. Every employee had a status. Every status change was logged. When a business leader asked “why is this person marked for exit?”, the answer was documented. When they asked three months later, the answer was still documented. Integration decisions have a half-life of about six weeks before someone remembers them differently.

Need help designing your IMO? We’ve built them across chemicals, pharma, consumer goods, and tech. Let’s talk.

What I’d change

I should have built the reporting layer first and the data entry layer second. I did it the other way around because I’m an engineer and engineers build the foundation before the facade. But the steering committee didn’t need a foundation. They needed a dashboard that showed them whether the integration was on track. I could have earned six weeks of organizational patience by shipping a dashboard on day one, even if the data behind it was manually loaded from spreadsheets.

(“But Josh, that’s just a fancy spreadsheet with extra steps!” I hear you squawking. You’re right. And it would have bought me the time to build the real thing.)

IMO #2: The $3.5 Billion Carve-Out

A Fortune 500 company was separating a business unit into a standalone entity. The unit had built its entire data and analytics capability on the parent company’s infrastructure. Every server, every database, every reporting tool, every login credential, every employee’s email address. All of it belonged to the parent. The carved-out entity needed to operate independently within the TSA window or start paying the parent company overage fees that would eat the deal economics alive.

The short version: we had to build a company that didn’t exist yet, and we had a deadline.

This is where I learned that an IMO for a carve-out is fundamentally different from an IMO for an acquisition. In an acquisition, two things exist and you’re combining them. In a carve-out, one thing exists and you’re building the second one from parts of the first. The IMO’s job isn’t coordinating an integration plan. It’s standing up a company.

The governance model reflected this. Instead of workstreams organized by function (HR, IT, Finance, Operations), we organized by capability. What does this entity need to operate on Day 1? Email and identity. Payroll. Financial reporting. Customer-facing systems. Regulatory compliance. Each capability had an owner. Each owner had a TSA deadline. The IMO tracked the gap between “what we have” and “what we need” and made sure the gap was closing faster than the TSA clock was ticking.

What worked

Organizing by capability instead of function. In a carve-out, the question isn’t “what does HR need to do?” It’s “can we pay people on Day 1?” Those are different questions with different owners. The payroll capability might require work from HR, IT, Finance, and Legal. Organizing by function would have created four workstreams that each owned a piece of payroll and nobody owned the whole thing.

TSA deadline as the only metric that mattered. We didn’t track percentage complete. We didn’t track tasks closed. We tracked one number: days until the TSA expired for each service. Everything else was noise. When a workstream lead told me they were “80% done,” I asked how many days they had left. If the answer was 30 days and the work remaining was 60 days of effort, we had a problem. If the answer was 90 days and the work remaining was 60 days, we had a buffer. Percentage complete is a feeling. Days remaining is math.

Zero business disruption as a hard constraint, not an aspiration. The steering committee made this non-negotiable on Day 1. We will not disrupt the business. Period. This meant every cutover had a rollback plan. Every migration happened on a weekend. Every go/no-go decision required sign-off from the business owner, not just the technical lead. It added friction to every workstream. It also meant we delivered without a single day of lost revenue.

What I’d change

We underestimated how long it takes to get a standalone entity set up in countries where the parent company provided all the legal infrastructure. Employment law in 14 countries is not 14 copies of the same problem. It’s 14 different problems that happen to share a deadline. I’d start the legal entity work six months earlier than we did. (For the full reality of what drives TSA timelines, it’s almost always payroll and legal entities.)

IMO #3: The Global Biopharma Transformation

This one breaks the pattern, which is why it’s useful.

A global pharmaceutical company was implementing SAP S/4 across multiple deployments. No merger. No acquisition. No carve-out. One company, rebuilding its own operating model from the inside. Finance, procurement, data and analytics, supply chain. All of it changing at once.

I ran a 12-person global OCM team. We were the change management arm of what was effectively a transformation office, but everyone called it the IMO because the structure was the same: steering committee, workstream leads, weekly cadence, escalation paths, decision log.

The problem was that nobody was being acquired. Nobody was being carved out. Nobody’s job was at risk because of a deal. The urgency that drives a merger IMO, the “we have 100 days to make this work or the deal economics collapse” pressure, simply didn’t exist. The timeline was measured in years, not weeks. And when the timeline is measured in years, people find reasons to delay.

This was mistake number 2 across my career, and the most expensive one: assuming that an IMO structure creates urgency. It doesn’t. A deal creates urgency. A TSA deadline creates urgency. An IMO just channels it. If there’s no underlying urgency to channel, you have a meeting cadence and a SharePoint site.

What worked

Executive partnership as the authority model. Without deal pressure, the only thing that moved the organization was executive alignment. I spent more time with the Finance, Procurement, and Data & Analytics leaders than I did with my own team. Workshops with global business leaders to design future organizations. Roadshows to generate buy-in. Monthly presentations to a change network of 300+ people across APAC, EMEA, and North America. The IMO’s authority didn’t come from a governance charter. It came from the relationships between the people in the room.

A change management playbook that created artificial deadlines. Since there was no deal clock, we manufactured our own cadence. Deployment waves with firm dates. Readiness assessments with pass/fail gates. Go/no-go decisions that required specific evidence, not opinions. The playbook was the accountability mechanism that a deal would have provided for free.

Focus on talent development and succession, not just process change. In a merger, org design is about who stays and who goes. In a transformation, org design is about who grows. The workshops I ran with global leaders weren’t about boxes on a chart. They were about which capabilities the organization needed in two years and who was going to develop them. This is a fundamentally different conversation, and it requires a different kind of IMO.

What I’d change

I’d have pushed harder for dedicated integration resources instead of borrowing people from the business. The “20% of your time” model doesn’t work for transformation any better than it works for integration. When people have a day job and a transformation job, the day job wins every time. (For more on this, see the first 100 days piece, where the same dynamic plays out in acquisitions.)

The Three Lessons That Didn’t Change

Across chemicals, pharma, and a carve-out. Across a decade. Across three completely different governance models, three different industries, and three different definitions of what “success” even meant.

1. The IMO’s authority comes from controlling information, not from org charts. Whoever owns the data that leaders use to make decisions has the real authority. A governance charter says who’s in charge. The system of record determines who actually is.

2. Organize around the work, not the org chart. In a merger, that means workstreams tied to value creation. In a carve-out, that means capabilities tied to TSA deadlines. In a transformation, that means outcomes tied to business cases. The structure follows the work. Not the other way around.

3. Urgency is not a feature of the IMO. It’s a feature of the situation. If you have a deal, a deadline, or a burning platform, the IMO channels that energy. If you don’t, no amount of governance will create it. Know which one you’re in before you design the structure.

If you’re standing up an IMO and aren’t sure which pattern fits, start with the full setup guide. If you already know your pattern but need help with the first 100 days of execution, that’s a different conversation. Both are worth having before you make your first PowerPoint deck with fourteen slides.

I’d know. I still have that deck somewhere.

Related Reading

• Integration Management Office (IMO): How to Set One Up That Works
• 100-Day Plan for M&A Integration: Practical Roadmap from Day 0 to Day 100
• M&A Integration Timeline: What Actually Happens After the Deal Closes
• Carve-Out Readiness: What to Build Before Day 1
• TSA Exit: Why Yours Will Take 18 Months (How to Cut It)