Empowered Acquisition Integration Model
Give successful acquired teams authority instead of burying them under failed incumbents
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 96%
When a company buys a successful product to replace or accelerate a failed internal effort, placing the acquired team beneath the leaders responsible for the failure can recreate the original problem. The empowered model first diagnoses why the internal team struggled, then preserves the acquired group's proven product judgment and execution practices. Reporting lines and decision rights are designed around the outcome the buyer needs rather than inherited hierarchy. The acquired leaders receive meaningful authority, and their scope expands as they demonstrate success. Integration still connects the team to the broader company, but it does not reduce new people to extra capacity for the old plan. This turns the acquisition into a source of organizational renewal rather than a staffing supplement.
Origin
Schultz contrasted an older integration pattern with Microsoft's later approach of empowering successful acquired teams and expanding their scope, citing the mobile Outlook experience.
Core principles
- 01Reporting structure can preserve or destroy acquired capability
- 02A failed incumbent system should not automatically control its replacement
- 03Successful acquired leaders earn expanded scope
- 04Integration should amplify the team's strengths rather than reproduce old behavior
How to run it
- 1
Diagnose the internal failure
Determine whether the existing effort failed because of strategy, leadership, incentives, skills, process, or resources. Make the diagnosis explicit before selecting the reporting structure.
Pro tip Interview both operators and stakeholders rather than accepting the incumbent leadership narrative.
Watch out Without diagnosis, integration may reproduce the same constraints with different employees.
- 2
Identify acquired strengths
Document the product decisions, execution habits, and leadership capabilities that made the acquired team successful. Decide which of these must remain intact.
Pro tip Ask the acquired team what conditions are essential to its performance.
Watch out Preserving job titles while removing decision rights does not preserve capability.
- 3
Design authority around outcomes
Give the acquired team enough control to deliver the product outcome that justified the purchase. Avoid automatically placing it beneath leaders whose existing approach failed.
Pro tip Define decision rights for roadmap, hiring, architecture, and release timing.
Watch out Using the new team merely to continue the old plan wastes the acquisition.
- 4
Connect without smothering
Provide access to the buyer's platform, customers, and resources while retaining the acquired team's effective operating model. Integrate dependencies deliberately rather than uniformly.
Pro tip Use interfaces and shared goals before imposing every central process.
Watch out Immediate total absorption can erase the speed and accountability the buyer sought.
- 5
Expand proven leadership
Evaluate results and increase the team's scope when it succeeds. Use the acquisition as a source of product leadership, not just headcount.
Pro tip Tie expanded authority to clear delivery and organizational outcomes.
Watch out Promising autonomy without a path to broader influence may undermine retention.
In the wild
A large software company acquires a team with a successful mobile client after its internal effort stalls. Rather than having the acquired group simply execute the old roadmap under the prior chain of command, it gives the team authority over the mobile product and expands its responsibilities after successful delivery.
→ The acquired capability improves the product while creating a new source of leadership inside the buyer.
Common mistakes
Putting new talent under failed leadership
The acquired team is likely to inherit the same decisions and constraints that caused the original effort to fail.
Treating the deal as extra staffing
More people cannot fix a flawed product model when they lack authority to change it.
Confusing integration with uniformity
Connecting systems and goals does not require immediately imposing every incumbent process.
Is it for you?
Best for
Companies acquiring a successful team to repair, replace, or accelerate a struggling internal product effort.
Not ideal for
Acquisitions requiring immediate absorption into tightly regulated or standardized operating processes.
From the transcript
“now that startup that you just acquired is reporting to the same people who are failing before.”
“that usually ended up being a recipe for for just not let's just say that the acquired companies usually more excited to be in that…”
“we've taken those folks and empowered them and and assuming they've been successful, we've continued to expand their scope and given them more and more.”
From the episode
Special: A Conversation with Microsoft's Head of Strategic Investments Brian Schultz
Brian Schultz