Austin-Boston Merger: Standardize, Preserve, or Hybridize After an Acquisition
After acquiring a 60-person product team in Boston, an 85-person engineering group in Austin is merging into one 145-person organization. Eight weeks in, attrition in the acquired Boston team is 14% annualized versus 6% in Austin, and engagement is 58% versus 74%. Three roadmap disputes have escalated to the VP in two weeks. Boston uses a two-week discovery cycle and local decision rights; Austin uses a quarterly stage-gate process and central architecture review. The Boston lead architect, who owns critical domain knowledge, has told HR she is one meeting away from leaving. The VP must decide whether to standardize on Austin's process, preserve Boston's autonomy, or design a hybrid. The CEO wants one operating model within 90 days and has tied 20% of the VP's bonus to retention of key talent.
1. Diagnose the integration problem using organizational behavior concepts. What explains the attrition and escalation pattern, and why is the architect a special risk?
Read the worked answer
The pattern is consistent with an integration being experienced as absorption rather than a merger. Boston is the acquired group, and the emerging operating model appears to be Austin's quarterly stage-gate process with central architecture review. That removes local decision rights and status from Boston leaders, which can trigger identity threat, loss of procedural justice, and in-group/out-group dynamics. The 14% versus 6% attrition and 58% versus 74% engagement are concentrated exactly where those losses are felt.
The three escalations in two weeks suggest unclear decision rights, not merely substantive disagreement. When teams do not know who decides, conflicts rise to the VP. Boston's two-week discovery cycle and Austin's quarterly gates also create a tempo mismatch: Boston experiences Austin's process as slow, while Austin experiences Boston's as undisciplined.
The architect is a key-person risk because she holds domain knowledge that is not easily documented and because losing her would confirm to Boston that the merger is a takeover. Her statement is a retention signal, not a routine complaint. The VP's bonus weighting makes retention a formal objective, but retention of one person without fixing decision rights would only postpone the problem.
2. Evaluate the three options: standardize on Austin's model, preserve Boston's autonomy, or design a hybrid. What are the tradeoffs?
Read the worked answer
Standardize on Austin. This is fastest and satisfies the CEO's one-model deadline, but it concentrates the loss on Boston, the group already showing 14% attrition. It risks losing the architect and other Boston talent, and it may destroy the discovery capability that justified the acquisition. The short-term compliance gain is likely to be outweighed by retention and knowledge loss.
Preserve Boston's autonomy. This protects Boston talent and speed but fails the one-operating-model requirement and leaves duplicate processes, unclear decision rights, and continued escalation. It also creates perceived unfairness in Austin, where 85 people may see a two-tier system.
Hybrid. A hybrid can work if it distinguishes principles from practices. Set shared principles for architecture review, roadmap prioritization, and release quality, but let Boston keep its two-week discovery cadence for early-stage work and Austin keep its stage-gate discipline for scaled releases. The critical design choice is decision rights: who decides roadmap priority, who decides architecture exceptions, and what must escalate. Without that, a hybrid becomes ambiguity rather than integration.
The hybrid has the best expected value if it is explicit about decision rights and if the architect is given a meaningful role in designing it.
3. Lay out a 90-day integration plan with decision rights, retention actions, and metrics.
Read the worked answer
Days 1–15: hold a joint operating-model workshop co-led by the VP, the Austin engineering lead, and the Boston architect. Publish a one-page decision-rights matrix: product roadmap priorities decided by a joint portfolio council with one vote per group; architecture standards owned jointly, with a 48-hour exception path; local team practices owned by each site within shared principles. Explicitly state what does not escalate.
Days 16–45: run a dual-track pilot on one product area. Boston keeps two-week discovery; Austin keeps stage-gate reviews at defined milestones. Measure time-to-decision, rework, and delivery predictability. Give the architect a named role as domain architect or integration lead with authority over the boundary, plus a retention package and a visible voice in the operating-model design.
Days 46–90: converge on one model with two documented variances, not two entirely separate systems. Retention actions should include stay interviews with the top 15 Boston and Austin key contributors, a 90-day no-layoff assurance for critical roles if true, and manager coaching on procedural justice.
Metrics: voluntary attrition in key talent, engagement pulse by site, number of escalations per month, time-to-decision, roadmap commitments met, and Boston knowledge-transfer coverage. Review at day 45 and day 90; if Boston key-talent attrition exceeds 8% annualized or escalations do not fall, revisit the model.