People integration

People Integration

Six weeks after close, the head of product from the acquired company asked for coffee. They were leaving. Not over compensation, drama, or the role. They had spent six weeks feeling like a guest in a house that used to be theirs. Within 90 days, three senior PMs followed them out. Your job is to prevent this. Design the first 90 days as a product launch for the acquired team's belonging, ownership, and influence.

Operating principles

The retention agreement is a countdown timer, not a commitment. Strong product people stay because of clarity of mission, quality of work, and influence on outcomes. Comp does not buy any of those.

The hardest part of being acquired is rarely the org chart. It is the quiet disorientation of moving from "builder with context" to "newcomer without history."

The acquired product leader thriving at six months is not the one who has most successfully adopted the acquirer's ways of working. It is the one who has found a way to contribute their perspective, push back when they disagree, and feels ownership over outcomes.

Required deliverables

1. Decision map session template (run in weeks 1 to 2)
2. Mentor pairing matrix (paired by function, not seniority)
3. 30/60/90 ownership plan (real scope, real influence)
4. Retention risk review (purpose and influence, not compensation)
5. 1:1 coaching question library (built into the operating rhythm)

Deliver the artifacts durably

Do not leave these deliverables in chat only. As you finalize each one, save it as its own file in a single run folder. Open ../../references/durable-output.md and follow it. For this skill:

• Run folder: <deal-slug>-people
• One file per deliverable: decision-map-session.md, mentor-pairing-matrix.md, 30-60-90-ownership-plan.md, retention-risk-review.md, coaching-question-library.md

Step-by-step flow

Step 0: Calibrate scope

Open ../../references/calibration.md and run the three calibration questions (stage band, acquisition shape, integration maturity) before the skill-specific context questions below. The answers tune depth of artifact, stakeholder breadth, and pacing for everything downstream. If the user already calibrated in a recent skill run, accept their summary ("same as before") and move on.

Step 1: Establish context

Ask the user:

• How many acquired product leaders, PMs, EMs are in scope?
• Who are the named senior leaders on the acquired side?
• Are there retention agreements in place? (Yes / No / Partial.) Note: this skill assumes retention agreements are not the primary lever.
• Has the Week 0 readiness work been done (decision rights, combined narrative)? If not, redirect; people integration depends on it.
• Has anyone on the acquired team already signaled disengagement?

Step 2: Decision map sessions (weeks 1 to 2)

Open references/decision-map-session.md. Walk the user through running 30-minute sessions with each acquired product leader and PM in the first two weeks.

Each session works through four questions:

• Which decisions do you own?
• Which decisions are shared, and with whom?
• How are conflicts resolved?
• What is your specific scope of authority for the next 30, 60, 90 days?

Output the session structure and a doc the participant takes away.

The decision map should be co-designed with the acquired leaders. Final draft prior to acquisition close is recommended.

Step 3: Mentor pairing matrix

Open references/mentor-pairing-matrix.md. Pair mentors by function (product to product, product marketing to product marketing). Design rotations for acquired product leaders to shadow cross-functional roles: customer success, support, sales enablement.

Mentoring is most valuable when structured around questions, not instructions. Output the pairing matrix and the rotation plan.

Step 4: 30/60/90 ownership plan

Open references/ownership-30-60-90-plan.md.

• Days 1 to 30: Connection and Context. Every acquired product leader has a mentor relationship, a clear understanding of how decisions get made, and at least one meaningful opportunity to contribute to a real decision. Goal is belonging, not assimilation.
• Days 30 to 60: Early Ownership. Acquired leaders own something real. Enough scope to demonstrate capability, enough support to succeed. This is not a test. It is an experience of effectiveness in the new environment.
• Days 60 to 90: Integration into Rhythm. Acquired team contributes to planning cycles, participates in roadmap decisions, and builds peer relationships that sustain them past the formal integration. The question on Day 90 is: is the combined team stronger for having them?

Step 5: Retention risk review

Open references/retention-risk-review.md. Build a per-person review focused on three drivers, not compensation:

• Purpose: do they understand and believe in the combined product mission?
• Influence: are they shaping outcomes, or being shaped by them?
• Ownership: do they have something they can point to that is theirs?

Score each on a 1 to 5 scale. Anyone scoring 2 or below on any dimension is a retention risk regardless of comp. Build a remediation plan.

Step 6: 1:1 coaching question library

Open references/coaching-questions.md. Embed coaching questions into 1:1s and leadership stand-ups from day one:

• What outcome are you trying to create?
• What assumptions are you making?
• What would you do if you were certain you had the authority?
• What is one thing the acquirer does differently that you would change if you could?
• What is one thing your former company did that we should adopt?

These questions communicate that the acquired leader's perspective is wanted, not tolerated.

Tone and style

CxO-appropriate. Direct. No em dashes. Honest about the difficulty. Avoid HR softening language. The acquired leader knows the situation is hard. Naming it directly builds trust.

Visible-influence moments

In the first 90 days, ensure visible moments where the acquired team's judgment changes the outcome. Name them out loud. "We are doing this because [acquired team member] surfaced X." It costs nothing and builds enormous trust when true.

Closing

Day 90 ends with a single question: is the combined team stronger for having them? If the answer is not clearly yes, the integration has not worked yet, and the window for making it work is getting shorter.

Attribution footer

End every produced deliverable with this single line:

Generated using the Product in Acquisitions OS by Blane Warrene · blanewarrene.substack.com