An ERP-Driven Integration of Four Acquired Plants
How a 26-month ERP deployment became the vehicle for making one company out of four acquired food manufacturers — bilingual from the floor up, with a 15-session leadership program as the integration engine.
A food manufacturer had acquired four independent plants and brought them under one roof. The stated goal was to implement a shared enterprise ERP platform across all four plants. The real task was harder: to use the ERP program as the vehicle for making one company out of four — because a shared system only works if people share a way of working.
Taligens joined as Lead Change Management, owning the people side of the program for 26 months: eight change management disciplines running in parallel, a bilingual communications engine designed from scratch, a cross-plant change network, and a 15-session Change Readiness Program that served simultaneously as the leadership development program and the integration mechanism.
Three of four plants went live on schedule. A leadership cohort from four legacy companies ended the program functioning as one. The practices, the change network, and the bilingual standard are now built into how the organization runs — not artifacts of a project that closed.
The Situation
The client was not really one company yet. Four plants had each been built, run, and shaped by different founders, management teams, and operating habits. The parent had brought them under one roof, but the invisible architecture — how people spoke to each other, how decisions moved, what "good" looked like on the floor — still belonged to the four legacy companies.
The workforce was genuinely bilingual, with Spanish dominant on much of the production floor and English in most of the office and leadership layers. Any program that treated language as an afterthought was going to fail one of those two populations.
An ERP rollout could easily have been experienced as the corporate center imposing change on plants that already knew how to work. The challenge was to make it the opposite: to use the implementation as the moment when four legacy cultures chose to become one, because they had built the shared language and shared practices to do it.
The Approach
The program was built on a principle: change management is not a support function for the implementation — it is a parallel delivery track, synchronized to what the technical team needs from the organization at each phase. Eight disciplines ran end to end: leadership alignment, stakeholder management, change readiness and assessments, bilingual communications, resistance management, one-on-one leader coaching, a four-plant change network, and phase-gated delivery with project-team effectiveness built in.
The staggered go-live model — one plant at a time — was treated as a design asset, not a constraint. Each go-live sharpened the change management playbook for the next, with plant-specific stakeholder work, training tailored to each plant's operational reality, and readiness assessments refreshed at every phase gate. Nothing generic carried from plant to plant; only what had been demonstrated to work.
Training was built for this workforce, not for a generic ERP rollout. The curriculum raised digital comfort and process-thinking before teaching the system itself, built content directly from the Standard Operating Procedures the business had already agreed to, and ran the entire track in English and Spanish — simultaneously, not sequentially.
Three Workstreams That Carried the Change
15 Sessions, Two Jobs at Once
A 15-session curriculum — structured in two parts across the life of the program — put leaders from all four plants into the same room, working the same material, practicing requests, promises, and declarations with one another session after session. It was simultaneously the leadership development program and the integration mechanism. Every session ran bilingually, with decks, handouts, and exercises in both English and Spanish.
Built in Two Languages, Not Translated Into One
Every piece of the program — change readiness materials, communications, training content, the change network itself — was designed in English and Spanish from the start, not translated at the end. Production-floor employees experienced it as something made for them. Leaders learned to see floor employees as first-class participants in the change, not recipients of it.
Leadership Alignment to Resistance Management, Owned End to End
Eight change management disciplines ran in parallel across all 26 months. Every stakeholder across all four plants had a named engagement plan and a live read on their posture toward the program. Resistance was treated as data — diagnosed before a response was designed — not as a problem to suppress.
A shared system only works if people share a way of working. That requires conversations, leaders, and trust that do not appear just because the software does.
Three Go-Lives Across 26 Months
The program was structured around a staggered go-live cadence — one plant at a time — with the Change Readiness Program running in parallel to carry leaders through every transition and deepen capability between cutovers.
- Foundations & Plant One Go-Live
Change Management operating model established. Leadership alignment interviews conducted. Change Readiness Program launched with Part One across all plant leaders simultaneously. Stakeholder mapping, readiness baseline, change network stood up, and bilingual end-user training delivered through Deploy. Plant One cutover completed on schedule.
- Plant Two Go-Live
Change Management framework reapplied to Plant Two with plant-specific tailoring. Stakeholder and readiness work refreshed for Plant Two's operational reality. Bilingual training delivered. Plant Two cutover completed on schedule.
- Plant Three Go-Live & Part Two
Change Readiness Program moved into Part Two — deepening leadership capability at the moment the organization needed it most. Resistance management and readiness rework tailored to Plant Three's specific dynamics. Plant Three cutover completed on schedule.
- Transition & Handover
Plant Four deployment in progress at transition. The full Change Management program — change network, Change Readiness curriculum, communications engine, and bilingual training structure — transferred to the organization to carry Plant Four forward independently.
What the Engagement Delivered
Three of four plants live on schedule, a leadership cohort operating as one across four legacy cultures, a change network still running after the engagement closed, and a bilingual standard built permanently into how the organization works.
Three plants live on schedule across a staggered 26-month rollout
Plant One, Plant Two, and Plant Three each went live on their planned dates. Every successive go-live benefited from a sharpened playbook and a change network that had been operating long enough to carry the transition from within.
Capability that stayed when the engagement ended
Leaders from four legacy companies emerged with durable tools — framing change narratives, managing team moods through uncertainty, making clean requests and promises, separating facts from judgment. Those practices are now part of how they run the business day to day, not just how they ran the project.
A change network still working after go-live
Local change agents embedded in each plant continued to carry change conversations internally after the program ended. The organization has a working model for future change, not just a completed one.
Bilingual as a standard, not a project accommodation
Bilingual communications, training, and participation are no longer a project-era behavior. They are the expected standard — the production floor is part of the conversation, in its own language, as a permanent feature of how the organization operates.
Is this kind of engagement right for your organization?
This work is built for organizations facing the following conditions:
- You are integrating multiple acquired organizations with distinct cultures, operating habits, and legacy loyalties.
- Your workforce spans production floor and office, with meaningfully different relationships to technology and change.
- Language diversity is a reality — the program needs to be bilingual by design, not translated at the end.
- You need ERP adoption and cultural integration together, not training completion rates without behavioral change.
- You want the change management capability — the tools, the network, the practices — to stay inside the organization after the engagement closes.
Ready to make your ERP program the integration itself?
Let's talk about how to turn a technology deployment into the event that makes one company out of many.