Technical Lead & BPMN Educator·12 min read
Why process harmonization is the hidden risk in every merger
Most M&A integration plans focus on systems, headcount, and financial consolidation. Process harmonization rarely gets its own workstream until something breaks. A customer order falls through the cracks because the two fulfillment processes have different approval logic. Finance cannot close the books because procurement runs on different controls. Support tickets get routed to the wrong team because escalation paths were never aligned.
These failures are not technical. They are structural. The two organizations built their operations around different assumptions, different tools, and different definitions of what “done” looks like. Without a deliberate harmonization effort, those differences persist long after the deal closes.
McKinsey estimates that 70% of mergers fail to achieve their projected synergies. Process misalignment is a primary contributor. The cost is not just operational friction. It is the delayed realization of the value that justified the deal in the first place.
What process harmonization actually means
Harmonization is not about picking one company's process and forcing it on the other. That approach breeds resentment and usually fails because it ignores context. True harmonization means analyzing both organizations' processes, understanding why each works the way it does, and designing a target state that captures the best of both while meeting the combined entity's requirements.
In practice, harmonization produces three types of outcomes for each process area:
Adopt
One organization's process is clearly superior. The other team adopts it. This works when one side has a mature, documented process and the other has an informal or ad-hoc approach.
Merge
Both organizations have strong processes, but each handles different aspects well. The target process combines elements from both. This is the most common outcome and requires the most design effort.
Redesign
Neither process works for the combined entity. The new scale, customer base, or regulatory requirements demand something new. This is expensive but sometimes necessary, especially for customer-facing processes.
"Do not try to harmonize everything at once. Prioritize by business impact and integration timeline. Order-to-cash and customer onboarding usually go first because they directly affect revenue. Back-office processes like facilities management can wait."
A step-by-step harmonization framework
Step 1: Build both process landscapes
Before you can compare processes, you need to see them. Each organization should produce a process landscape at the L0 (value chain) and L1 (process group) level. This gives you a structural overview without drowning in workflow-level detail.
If one or both organizations lack formal documentation, this is the time to build it. Run focused discovery sessions with process owners from each side to capture the L0 and L1 structure. Even rough landscapes are better than nothing because they make the comparison possible.
Tip
Use the same leveling convention for both landscapes. If Company A uses “Order to Cash” and Company B calls it “Sales Operations”, normalize the naming before comparing. Inconsistent naming hides overlaps.
Step 2: Identify overlaps and gaps
Place both landscapes side by side. For each L0 area, ask: does the other organization have an equivalent? Where do the boundaries differ? Which L1 process groups exist in one organization but not the other?
You will find three categories:
- Full overlap: Both organizations have the same process area with similar scope. These are your harmonization candidates.
- Partial overlap: The same business function exists, but the scope or boundaries differ. These need careful analysis before deciding how to align them.
- Unique: One organization has a process area that the other does not. These are adopted as-is or evaluated for relevance to the combined entity.
Step 3: Assess at the L2 level where it matters
Not every process needs detailed comparison. Focus the L2 (detailed BPMN) analysis on the process areas with full or partial overlap that are on the critical path for integration. Typically these include: order management, customer service, procurement, financial close, and employee onboarding.
For each priority process, model the as-is state from both organizations. Use pools to separate the two organizations' versions visually. Look for differences in:
- Approval chains and decision points
- System touchpoints and handoffs
- Exception handling and escalation paths
- Roles and responsibilities within lanes
- Cycle times and SLAs
Step 4: Design the target operating model
For each overlapping process area, design the to-be state. This is where the adopt/merge/redesign decision happens. Involve process owners from both organizations. The people who run the processes daily have context that no integration consultant can replicate.
The target operating model should define:
- The harmonized process flow (documented in BPMN)
- Role assignments for the combined organization
- System decisions (which ERP, which CRM, which workflow engine)
- Transition rules (how to migrate from the current state to the target)
- KPIs and success metrics for the harmonized process
"Resist the temptation to optimize during harmonization. The goal is alignment, not improvement. Get to a single stable process first, then optimize in a separate initiative once the integration dust settles."
Step 5: Plan the transition
A harmonized process on paper is worthless if people do not adopt it. The transition plan should cover: training for affected teams, a migration timeline with clear cutover dates, a parallel-run period where both processes operate simultaneously, and rollback criteria if the harmonized process causes more disruption than it solves.
For complex processes, consider phased rollouts by region, business unit, or customer segment. A big-bang cutover for a critical process area is high risk. Phase it where you can.
Step 6: Govern and iterate
Harmonization is not a one-time project. The combined organization will continue to evolve. Assign process owners for each harmonized area. Schedule quarterly reviews. Track whether the synergies projected in the deal thesis are actually materializing at the process level.
This is where process governance becomes essential. If you do not have a governance framework yet, now is the time to establish one. Clear ownership, review cadences, and change control mechanisms prevent the harmonized processes from drifting apart again.
Common harmonization mistakes
Mistake: Winner takes all
Forcing the acquirer's processes on the acquired company destroys institutional knowledge and breeds resistance. Evaluate each process area on its merits, not on who bought whom.
Mistake: Harmonizing everything simultaneously
Prioritize by business impact and integration timeline. Trying to harmonize 50 process areas at once overwhelms teams and delivers nothing on time.
Mistake: Skipping the landscape step
Without a structured comparison at the L0/L1 level, teams jump into L2 details and lose sight of the big picture. Build the map before diving into individual processes.
Mistake: Confusing harmonization with optimization
The goal is one stable process, not a perfect one. Optimization is a separate initiative that comes after the combined organization is operating on a single foundation.
Mistake: Ignoring culture
Processes carry cultural assumptions. Company A's 4-level approval chain reflects a risk-averse culture. Company B's flat approval reflects speed-first thinking. The harmonized process needs to acknowledge these differences, not pretend they do not exist.
Tools for process harmonization
Process harmonization requires a tool that can hold multiple process landscapes, support collaborative editing across teams, and produce standards-compliant BPMN output that survives system migrations. The specific tooling depends on your organization's scale and existing investments.
Not sure which tool fits? Take our tool finder quiz or browse all 16 tool profiles.
When to harmonize
- +Customer-facing processes that directly affect revenue and experience
- +Financial processes that affect reporting, compliance, and auditability
- +Processes tied to shared systems (ERP, CRM) where duplication creates data quality issues
- +Employee-facing processes where inconsistency creates confusion and inequity
When to leave alone (for now)
- -Processes specific to one business unit with no cross-entity interaction
- -Back-office processes that can run in parallel without customer impact
- -Processes scheduled for sunsetting as part of the integration
- -Areas where regulatory or contractual constraints prevent changes in the short term
FAQ
How long does process harmonization take after a merger?
It depends on scope. Harmonizing the top 5 to 10 critical process areas typically takes 3 to 6 months. Full organizational harmonization can take 12 to 18 months. Prioritize by business impact and sequence the work across integration phases.
What is the difference between process harmonization and process standardization?
Harmonization aligns two different process sets into a coherent target state. Standardization enforces a single way of working across the entire organization. Harmonization comes first (post-merger); standardization follows once the combined entity has a stable operational foundation.
Who should lead the process harmonization effort?
Ideally, a dedicated integration manager or PMO with process expertise. They need authority to make cross-organizational decisions and access to process owners from both entities. Without executive sponsorship, harmonization stalls at the first political disagreement.
Can process harmonization be automated?
Parts of it can be tooling-assisted. Process mining can reveal how processes actually run (vs. how they are documented). BPMN tools can help compare and visualize differences. But the design decisions, stakeholder alignment, and change management are human work.
What happens if we skip process harmonization?
The organizations continue running on separate processes. This creates operational silos, duplicated effort, inconsistent customer experiences, and delayed synergy realization. The longer you wait, the harder and more expensive harmonization becomes.
Continue reading
- Process Landscapes: From Value Chain to Detailed Processes — the foundation for comparing two organizations
- As-Is vs To-Be Process Modeling — how to document current and target states
- Process Mapping for Digital Transformation — related methodology for large-scale process change
- Process Mapping for ERP Implementation — often a parallel workstream in M&A integrations
- Process Documentation Best Practices — how much detail to capture at each stage