Teams still identify as legacy-company groups
The former organizational boundary remains behaviorally consequential.
Why is this integration still two companies working beside each other?
Combining reporting lines, systems, and processes does not itself create a shared coordination system. The integrated outcome requires actors, authority, state, dependencies, and adaptation to coordinate across the former boundary.
A signal is evidence to investigate, not a diagnosis by itself.
Short Answer
Combining reporting lines, systems, and processes does not itself create a shared coordination system. The integrated outcome requires actors, authority, state, dependencies, and adaptation to coordinate across the former boundary.
Combining reporting lines, systems, and processes does not itself create a shared coordination system. The integrated outcome requires actors, authority, state, dependencies, and adaptation to coordinate across the former boundary.
What You're Seeing
The pattern is visible in the work.
Duplicate processes persist
Parallel operating systems continue even after formal consolidation.
Decisions require negotiation across former boundaries
Authority has not become unified around the integrated outcome.
Data and state remain fragmented
Actors cannot reconstruct a shared operating picture.
Customers experience inconsistent handoffs
The integration boundary remains visible in the delivered experience.
Synergies depend on a small number of bridge people
Individuals manually connect the two systems without eliminating the structural divide.
Why It Matters to the Business
The acquisition thesis cannot be realized by legal combination alone.
Value depends on the combined organization being able to coordinate capabilities that previously operated separately. When authority, state, dependencies, and operating assumptions remain divided, synergies arrive late, duplicated cost persists, and customers experience the seams.
Delayed synergies
Expected revenue or cost benefits wait on unresolved coordination across the former boundary.
Duplicated capacity
Parallel processes, systems, and decision paths remain in place longer than intended.
Execution risk
Conflicting state and authority create mistakes, delay, and customer inconsistency.
Common Interpretation
“We have a culture or change-management problem.”
Culture matters, as do systems migration and process integration. But an integration can remain structurally divided even when people are cooperative and the org chart has changed.
Structural Interpretation
Follow the symptom into the coordination system.
Boundary
The intended integrated outcome may not have a clearly established coordination-system boundary.
Authority
Decision rights may remain split across legacy structures.
State
Shared state may not be reconstructable across systems and teams.
Dependencies
Interfaces may still behave like external relationships rather than internal participation.
Failure
Problems may cross the old boundary without shared containment mechanisms.
Adaptation
Each legacy system may continue learning separately instead of adapting at the integrated-system level.
Evidence to Look For
What would support—or weaken—the structural interpretation?
The signal alone is not enough. Look for evidence that distinguishes a structural mechanism from other plausible explanations.
- SupportsRecurring issues cluster around former-company boundaries rather than around the actual work.
- SupportsBridge people are required to translate state, terminology, and decisions between groups.
- SupportsIntegrated outcomes lack a single usable authority structure.
- SupportsShared processes exist on paper but coordination still follows legacy networks.
- SupportsCustomers or partners still experience inconsistent behavior across the legacy divide.
- SupportsIntegration benefits depend on manual reconciliation rather than new structural conditions.
- WeakensDistinct operating units are intentionally independent and coordinate cleanly through explicit interfaces.
- WeakensThe integration thesis does not require a shared coordination system for the outcome in question.
Relevant Structural Characteristics
Where to look structurally.
Decision AuthorityState TraceabilityConstraint VisibilityFailure ContainmentAdaptation Capacity
The Question Underneath the Question
Move from symptom to mechanism.
Ask insteadWhat shared coordination system must exist for the integration thesis to be realized, and which structural conditions still stop at the old company boundary?
Related Signals
The same structural conditions can surface elsewhere.
What is this signal costing the outcome?
2ndSys helps make the coordination system producing the signal visible so you can see what is consuming capability and where attention belongs.