New Hire Onboarding Pack
Senior Product Manager, Enterprise Integrations
Table of Contents
- Onboarding Brief
- Preboarding Checklist
- First-Week Plan
- Context Pack Outline
- Listening Tour Kit
- Working Agreement
- 30/60/90-Day + 1-Year Plan
- 30-Day State-of-the-Union Memo (Template)
- Risks / Open Questions / Next Steps
1) Onboarding Brief
The Hire
- Name: [New Senior PM]
- Role / level: Senior Product Manager, Enterprise Integrations
- Start date: Monday, April 7
- Location / time zone: Fully remote; US/EU coverage required (exact TZ TBD -- confirm preferred working hours and overlap windows)
- Manager: VP of Product
Why this hire / why now
- The enterprise integrations product line is a critical growth lever for a Series C B2B collaboration SaaS company at 250 people. Two PM turnovers in the past year have left the team without stable product leadership, eroded trust with engineering and design partners, and stalled the integration roadmap.
- If this hire is a huge success in 6 months: Enterprise integrations have a clear, communicated roadmap with at least 2 major integrations shipped or in beta. Cross-functional partners trust the PM as the decision-maker. Team morale has measurably improved (eNPS, retention signals). The new PM has built durable relationships with enterprise customers and internal stakeholders and is operating autonomously.
Success Definition
| Horizon | What "great" looks like |
|---|---|
| 30 days | Has completed a listening tour across all key stakeholders. Can articulate the current state of the integrations product line (what's shipped, what's in flight, what's stalled and why). Has published a 30-day "state of the union" memo. Has established a working agreement with VP of Product. Team reports feeling heard and cautiously optimistic. |
| 60 days | Has proposed a prioritized integrations roadmap for the next 2 quarters, validated with engineering, design, sales, and customer success. Has shipped or unblocked at least one stalled initiative. Has established regular operating cadence (sprint rituals, stakeholder updates). Decision rights are clear. |
| 90 days | Roadmap is in execution. At least one major integration is in beta or shipped. Cross-functional partners rate collaboration as "good" or better. Team morale shows measurable improvement. The PM is operating with high autonomy; VP of Product is in coaching mode, not directing. |
| 1 year | Enterprise integrations are a recognized competitive advantage. Partnership/integration ecosystem is growing. The PM owns the P&L-adjacent metrics (integration adoption, enterprise expansion revenue). Has mentored or onboarded at least one additional team member. Is seen as a go-to leader in the product org. |
Constraints + Context
- Company stage: Series C, ~250 people, fully remote US/EU. Growth stage with enterprise sales motion maturing.
- Team mission: Build and scale the enterprise integrations platform that makes the collaboration SaaS indispensable in customers' tool ecosystems.
- Current challenges: 2 PM turnovers in 12 months have damaged team morale and stakeholder trust. Engineering and design partners are skeptical. Some integration projects are stalled or under-scoped. Enterprise customers have voiced frustration about integration gaps.
- Important dependencies: Engineering team lead, Design lead, Sales/SE team, Customer Success, Platform/API team, Security/compliance.
- Confidentiality: No customer PII in shared docs. Redact revenue figures and specific customer names in onboarding materials.
Risks to Watch
| # | Risk | Mitigation |
|---|---|---|
| 1 | Team skepticism / "here we go again" fatigue from 2 prior turnovers. New PM may face passive resistance or withholding of context. | Prioritize trust-building and listening over quick wins. Acknowledge the history explicitly. Assign a buddy who can provide honest context on team dynamics. |
| 2 | Pressure to ship immediately from leadership or sales, cutting short the listening/learning phase. | VP of Product must explicitly protect the 0-30 day listen-first period. Communicate the plan to stakeholders. |
| 3 | Remote isolation and context gaps. Fully remote + US/EU time zones can slow relationship building and create information asymmetry. | Over-index on scheduled 1:1s in weeks 1-2. Use async video intros. Ensure daily buddy check-ins. Establish overlap hours. |
| 4 | Inherited technical debt or undocumented decisions on the integrations platform that create surprises. | Include eng lead and platform team early in the listening tour. Request an architecture walkthrough in week 1. |
| 5 | Ambiguous decision rights if the VP of Product has been filling in as interim PM. | Clarify ownership explicitly in the working agreement and communicate the transition to the team and stakeholders. |
2) Preboarding Checklist
Owner legend: M = Manager (VP of Product), HR = People Ops, IT = IT/Infra, B = Buddy
Complete all items by Friday, April 4 (one business day before start).
Logistics
- Offer letter and HR paperwork finalized (owner: HR)
- Equipment ordered and shipped to home address -- laptop, monitor, peripherals, company swag welcome kit (owner: IT)
- Accounts created: email, SSO, VPN, Slack, GitHub/GitLab, Jira/Linear, Figma (viewer), Confluence/Notion, analytics dashboards (Amplitude/Mixpanel), CRM (Salesforce -- read access) (owner: IT)
- Permissions granted for enterprise integrations project spaces, product docs, and roadmap tools (owner: M)
- Calendar invites sent for week 1: all team rituals, 1:1s, onboarding sessions, stakeholder intros (owner: M)
- Added to relevant Slack channels: #product-team, #enterprise-integrations, #eng-integrations, #sales-enterprise, #all-hands, #random, #new-hires (owner: M)
- Buddy assigned and briefed on responsibilities (owner: M) -- Recommended buddy: a senior engineer or designer on the integrations team who has been through both turnovers and can provide honest, grounded context
- "First pair" assigned: another PM on the product team for collaborative pairing on a real task in week 1 (owner: M)
Context Pack (send by Thursday, April 3)
- Team operating manual / "how we work" doc (owner: M)
- Glossary: acronyms, tools, key domain terms (e.g., integration partner names, API terminology, enterprise-specific jargon) (owner: M)
- Product strategy doc: current enterprise integrations strategy + company strategy overview (owner: M)
- Key metrics dashboard links: integration adoption rates, enterprise customer metrics, NPS/CSAT for integrations (owner: M)
- Decision history: top 5 product decisions in the last 6 months and the reasoning behind them (owner: M -- critical given PM turnover; some decisions may be poorly documented)
- Org chart with key names and roles highlighted (owner: HR)
- Reading list: 3-5 essential docs (keep it short -- no firehose) (owner: M)
Welcome Communications
- VP of Product sends a personal welcome email/Slack DM (by April 3) with: excitement about the hire, link to the context pack, buddy intro, and an invitation to reach out with any questions before day 1 (owner: M)
- Buddy sends a casual intro message (by April 4) (owner: B)
- Team-wide announcement in #product-team and #enterprise-integrations: brief intro, start date, encourage the team to reach out (owner: M)
3) First-Week Plan (April 7-11)
Design principles for this week: Belonging first. No "sit alone and read docs" days. Every day has social touchpoints and at least one collaborative activity. Given the team's history of PM turnover, the tone should be warm, curious, and low-pressure -- she is here to listen and learn, not to announce changes.
Monday, April 7 (Day 1) -- Theme: Belonging + Orientation
| Time (Eastern) | Activity | With | Notes |
|---|---|---|---|
| 9:00-9:30 | Welcome call: personal connection, excitement, day-1 logistics | VP of Product | Warm, casual. Share the plan for the week. |
| 9:30-10:30 | Setup + access verification | IT (async support) + Buddy (on standby) | Walk through all tool access. Buddy available for questions. |
| 10:30-11:30 | Buddy onboarding session | Buddy | Tour of Slack, key docs, team norms, "where to find things," honest context on team culture. |
| 11:30-12:00 | Async: read context pack highlights | Solo (with buddy on Slack) | Focus on strategy doc + glossary. Not the full reading list. |
| 12:00-12:45 | Virtual team lunch / welcome coffee | Integrations team (eng + design) | Informal. Icebreaker: "What's your favorite integration you use daily?" No work talk required. |
| 1:00-2:00 | "How we work" walkthrough | VP of Product | Decision-making norms, meeting cadence, communication expectations, Slack etiquette. |
| 2:00-3:00 | Product demo: enterprise integrations current state | Eng lead or senior engineer | Live walkthrough of the product. Focus on "what exists today." |
| 3:00-3:30 | Daily check-in with buddy | Buddy | How's day 1 going? Any access issues? Any questions? |
| 3:30-4:00 | Async: personal intro post in #enterprise-integrations | Solo | Brief self-intro: background, excitement, what she's looking forward to learning. |
Tuesday, April 8 (Day 2) -- Theme: Key Relationships + Domain
| Time (Eastern) | Activity | With | Notes |
|---|---|---|---|
| 9:00-9:30 | Daily standup (observe) | Integrations eng team | Listen only. Understand the rhythm. |
| 9:30-10:30 | 1:1: Engineering Lead, Integrations | Eng Lead | Intro + relationship building. Ask about current state, what's working, what's hard. |
| 10:30-11:30 | 1:1: Design Lead | Design Lead | Same framing. Understand design process and pain points. |
| 11:30-12:30 | First pair session | PM peer (first pair) | Collaborate on a real task: review an in-flight integration spec or customer feedback synthesis. Produce a small artifact together. |
| 1:00-2:00 | Architecture walkthrough: integrations platform | Eng Lead + Platform/API engineer | Understand the technical landscape, constraints, and debt. |
| 2:00-2:30 | Buddy check-in | Buddy | Process the day. Surface questions. |
| 2:30-3:30 | Async: review key metrics dashboards | Solo | Integration adoption, enterprise customer data, support tickets. Note questions. |
Wednesday, April 9 (Day 3) -- Theme: Stakeholder Intros (Business)
| Time (Eastern) | Activity | With | Notes |
|---|---|---|---|
| 9:00-9:30 | Daily standup (observe) | Integrations eng team | |
| 9:30-10:30 | 1:1: Head of Enterprise Sales | Head of Sales | What do enterprise customers ask for? What integration gaps lose deals? |
| 10:30-11:30 | 1:1: Customer Success Lead | CS Lead | What integration issues cause churn risk? What do customers love? |
| 11:30-12:30 | First pair session #2 | PM peer (first pair) | Continue collaborative work or tackle a new artifact. |
| 1:00-2:00 | Async: review recent customer feedback + support tickets related to integrations | Solo | Build a preliminary picture of customer pain. |
| 2:00-3:00 | 1:1: Solutions Engineer / SE Lead | SE Lead | How do integrations come up in the sales process? What's the competitive landscape? |
| 3:00-3:30 | Buddy check-in | Buddy |
Thursday, April 10 (Day 4) -- Theme: Stakeholder Intros (Product + Platform)
| Time (Eastern) | Activity | With | Notes |
|---|---|---|---|
| 9:00-10:00 | 1:1: Platform / API Team Lead | Platform Lead | Dependencies, shared infrastructure, integration architecture constraints. |
| 10:00-11:00 | 1:1: Security / Compliance Lead | Security Lead | Enterprise compliance requirements for integrations (SOC2, data residency, etc.). |
| 11:00-12:00 | VP of Product 1:1 (first formal) | VP of Product | Review the week so far. Begin working agreement conversation (see Section 6). Discuss 30/60/90 plan draft. |
| 12:00-1:00 | Virtual coffee with a cross-functional peer (e.g., another PM or eng manager) | Peer | Informal relationship building outside the immediate team. |
| 1:00-2:00 | Async: begin documenting listening tour notes and emerging questions | Solo | Use the synthesis table from Section 5. |
| 2:00-2:30 | Buddy check-in | Buddy |
Friday, April 11 (Day 5) -- Theme: Reflection + Planning
| Time (Eastern) | Activity | With | Notes |
|---|---|---|---|
| 9:00-9:30 | Daily standup (observe) | Integrations eng team | |
| 9:30-10:30 | Week 1 reflection + Q&A | VP of Product | What surprised you? What are your top questions? Calibrate the listening tour plan for weeks 2-4. |
| 10:30-11:30 | Team retrospective or team meeting (if scheduled) | Integrations team | Observe and participate lightly. |
| 11:30-12:30 | First pair wrap-up session | PM peer (first pair) | Close out the collaborative work. Debrief on how the pairing went. |
| 1:00-2:00 | Write week-1 summary | Solo | Personal notes: what I learned, who I met, top questions, what felt good/hard. Share a brief version with VP of Product. |
| 2:00-2:30 | Buddy check-in (weekly wrap) | Buddy | What worked this week? What should change for week 2? |
| 2:30-3:00 | Async: send a short "thank you" message in #enterprise-integrations | Solo | Appreciate the team for a welcoming week. Keep it genuine and brief. |
Week 1 "First Contribution": Collaborate with the PM peer (first pair) to produce one tangible artifact -- for example, a synthesized summary of the top 5 customer-reported integration pain points from support tickets and customer feedback. This gives her a meaningful early deliverable without requiring deep context.
4) Context Pack / Team Operating Manual Outline
This document should be prepared by the VP of Product (with input from the team) and sent to the new PM by April 3. Given the PM turnover history, some of this may be poorly documented -- the outline below identifies what to create even if rough.
1. Team Mission + What We're Optimizing For
- Enterprise integrations team mission statement
- Current north star metric (e.g., % of enterprise customers using 2+ integrations)
- What we're optimizing for right now (growth? retention? platform reliability?)
- What we're explicitly NOT optimizing for yet (and why)
2. How We Make Decisions
- Decision framework in use (if any -- RACI, DRI, RFC process)
- Who has decision rights for: roadmap prioritization, technical architecture, partner selection, pricing
- Escalation path: PM -> VP Product -> CPO/CEO
- Decision log location (link)
- Important: Document any decisions made during the PM vacancy and the reasoning, even if informal
3. Product Philosophy + Mental Models
- VP of Product's product philosophy (written or linked)
- Key mental models the team uses (e.g., "integrations as ecosystem moat," "build vs. partner vs. buy," "integration tiers")
- How the team thinks about enterprise vs. SMB needs
- How technical debt decisions are framed
4. What "Good" Looks Like Here
- Examples of well-executed integration launches (link to post-mortems or launch docs)
- Examples of specs or PRDs the team considers high quality
- What a good sprint looks like for this team
5. Metrics: North Star + Leading Indicators + Dashboards
- North star metric and definition
- Leading indicators: integration activation rate, time-to-first-sync, API reliability, partner satisfaction
- Dashboard links (Amplitude, Mixpanel, internal tools)
- Data caveats or known measurement gaps
6. Cadence: Rituals, Ceremonies, Meeting Norms
- Daily standup: time, format, async/sync
- Sprint planning + review: cadence, format
- Product review with leadership: frequency, format
- Retrospectives: frequency
- All-hands and company rituals
- "No meeting" blocks or focus time norms
7. Stakeholders: Who We Serve + Key Partners
- Internal: engineering, design, sales, CS, platform, security, marketing
- External: integration partners, enterprise customers (key accounts), analyst relations
- Key partner contacts and relationship owners
8. Glossary: Acronyms + Tools + Where Truth Lives
- Tool map: where to find specs (Notion/Confluence), code (GitHub), designs (Figma), metrics (dashboards), customer feedback (CRM/support tool), communication (Slack channels)
- Common acronyms and integration-specific terminology
- "Source of truth" for: roadmap, sprint backlog, customer requests, partner agreements
5) Listening Tour Kit (Weeks 1-4)
Listening Tour Design Principles
Given the team context -- 2 PM turnovers, fragile morale, enterprise customer frustration -- this listening tour must:
- Signal humility and genuine curiosity, not "I'm here to fix things."
- Acknowledge the past without dwelling on it: "I know this team has been through transitions. I'm here to listen first."
- Cover all critical interfaces within weeks 1-3 so the 30-day memo is well-informed.
- Surface the unsaid: what people are afraid to raise, where trust broke down, what they need from a PM.
Stakeholder Map
| Person / Role | Relationship to Hire | What They Know | What They Need from Hire | Priority | Meet By |
|---|---|---|---|---|---|
| VP of Product (Manager) | Direct manager | Strategy, org context, why the role exists | Autonomous ownership, clear communication, rebuilding team trust | H | Day 1 (April 7) |
| Engineering Lead, Integrations | Key partner (builds what PM defines) | Technical state, debt, team capacity, what's stalled | Clear priorities, realistic scoping, protection from thrash | H | Day 2 (April 8) |
| Design Lead | Key partner (shapes the experience) | UX debt, user research findings, design process gaps | Partnership, user-centered prioritization, feedback loops | H | Day 2 (April 8) |
| Head of Enterprise Sales | Internal customer | Deal pipeline, integration gaps that lose deals, competitive intel | Roadmap visibility, sales enablement, responsiveness to deal-critical requests | H | Day 3 (April 9) |
| Customer Success Lead | Internal customer | Churn risks, customer pain, integration support burden | Reliability improvements, customer-facing roadmap, faster resolution of integration issues | H | Day 3 (April 9) |
| Solutions Engineer / SE Lead | Implementation partner | Technical integration challenges, customer setup friction | Better docs, smoother integration flows, input on feasibility | H | Day 3 (April 9) |
| Platform / API Team Lead | Technical dependency | Shared infrastructure, API limits, platform roadmap | Coordination, aligned priorities, no surprise dependencies | H | Day 4 (April 10) |
| Security / Compliance Lead | Governance partner | Compliance requirements, data handling constraints, audit readiness | Compliance-by-design in integrations, early engagement on new partners | H | Day 4 (April 10) |
| Senior Engineers on Integrations Team (2-3) | Direct collaborators | Day-to-day reality, what's working/broken, morale | Stable leadership, clear direction, being heard | H | Week 2 (April 14-18) |
| Product Marketing Manager | Go-to-market partner | Messaging, competitive positioning, launch playbook | Launch planning, positioning input, feature narratives | M | Week 2 (April 14-18) |
| Head of Support / Support Lead | Frontline feedback | Top integration issues, ticket volume, customer sentiment | Fewer integration bugs, better error handling, documentation | M | Week 2 (April 14-18) |
| Data / Analytics Lead | Measurement partner | Data infrastructure, metric definitions, known gaps | Clear metric requirements, instrumentation priorities | M | Week 2 (April 14-18) |
| CEO or CPO (skip-level) | Executive sponsor | Company vision, board-level priorities, strategic bets on integrations | Confidence that the integrations strategy is sound and the team is stable | M | Week 3 (April 21-25) |
| Key Integration Partners (external, 2-3) | External partners | Partner roadmap, technical constraints, relationship health | Reliable partnership, clear communication, mutual roadmap alignment | M | Week 3-4 (April 21 - May 2) |
| Enterprise Customer Champions (2-3, via CS intros) | End users | Real-world integration usage, pain points, unmet needs | Better integrations, reliability, responsiveness | M | Week 3-4 (April 21 - May 2) |
| Other PMs on the Product Team (2-3) | Peers | Cross-product dependencies, org norms, what works/doesn't in the PM team | Collaboration, alignment, shared context | L | Week 2-3 |
Question Guide (pick 5-8 per meeting, tailored to the person)
Universal openers (use in every meeting):
- What are we optimizing for right now on the integrations product line, and why?
- What's working well today that we should protect?
- What's broken or painful? Can you give me a specific example?
Diagnostic questions (use selectively): 4. What decisions are "stuck" right now, and what's blocking them? 5. Where do you see the biggest risks for enterprise integrations in the next 90 days? 6. What does "great" look like for the PM role on this team, in your view? What did previous PMs do well or struggle with? (Handle sensitively -- not a gossip session, but understanding patterns.) 7. If you could change one thing about how the integrations team operates, what would it be? 8. What do enterprise customers ask for most that we can't deliver today? Why not?
Relationship questions (use in 1:1s with close collaborators): 9. How do you prefer to work with a PM? Communication style, decision-making, feedback? 10. What should I absolutely NOT do in my first 30 days? 11. What context do I need that isn't written down anywhere?
Forward-looking questions (use in week 3-4 conversations): 12. If our integrations platform were excellent in 12 months, what would that look like? 13. What partnerships or integrations would be game-changers for our enterprise customers? 14. What capabilities does the team need to build that we don't have today?
Listening Tour Notes Template (per meeting)
## Meeting: [Person / Role]
**Date:**
**Duration:**
### Key takeaways (3-5 bullets)
-
### What's working well
-
### What's broken / painful (with examples)
-
### Stuck decisions or unresolved tensions
-
### What they need from me
-
### Surprises or things I didn't expect
-
### Follow-up actions
- [ ]
Synthesis Table (complete after all meetings, around day 25-28)
| Theme | Evidence (who said what) | Tension / Trade-off | Candidate Opportunity | Suggested Next Action |
|---|---|---|---|---|
| e.g., Roadmap clarity | Eng lead, Sales, CS all mentioned lack of clear priorities | Sales wants customer-specific integrations; eng wants platform investment | Create a transparent prioritization framework | Draft prioritization criteria and review with VP Product + Eng Lead |
6) Working Agreement (VP of Product <-> Senior PM)
To be discussed in the first VP-PM 1:1 (Day 4, April 10) and finalized by end of Week 2 (April 18). This is a living document -- revisit at 30 and 60 days.
Expectations
What the VP of Product needs from the Senior PM in the first 30/60/90 days:
- Days 0-30: Listen deeply. Build trust with the team and stakeholders. Don't commit to roadmap changes. Produce a 30-day state-of-the-union memo. Communicate openly about what you're learning.
- Days 31-60: Propose a prioritized roadmap and get alignment. Unblock at least one stalled initiative. Establish your operating cadence. Start making decisions autonomously within agreed boundaries.
- Days 61-90: Execute on the roadmap. Ship at least one major integration milestone. Demonstrate that team morale is improving. Operate with high autonomy; VP shifts to coaching mode.
What the Senior PM should expect from the VP of Product:
- Active air cover during the listening phase: communicate to stakeholders that the new PM is ramping intentionally and won't be pressured into premature commitments.
- Honest, direct feedback -- weekly in 1:1s, not saved up.
- Clear escalation support: if decisions are contested, the VP will back the PM publicly and discuss disagreements privately.
- Context on org politics, executive priorities, and any landmines.
- Protected time: VP will shield the PM from non-essential meetings and requests in the first 30 days.
Decision Rights
| Decision Area | PM Decides (inform VP) | PM + VP Decide Together | VP Decides (PM inputs) |
|---|---|---|---|
| Sprint-level prioritization | X | ||
| Quarterly roadmap priorities | X | ||
| New integration partner selection | X | ||
| Technical architecture choices | PM recommends; Eng Lead decides | ||
| Pricing / packaging for integrations | X | ||
| Headcount / hiring | X | ||
| Escalations to exec team | X | ||
| Feature deprecation | X | ||
| Day-to-day stakeholder communication | X |
Communication
- Preferred channels:
- Slack DM for quick questions and FYIs (response within 4 hours during overlap)
- Shared doc or Notion page for async updates and longer thinking
- Email for formal stakeholder communications (CC the VP on outbound to execs or partners)
- Video call for complex discussions, feedback, and relationship check-ins
- Response time norms: Slack -- same business day. Docs -- 48 hours for review. Urgent (tagged as such) -- within 2 hours.
- How we disagree: Disagree openly in 1:1s. Align on a position before going to the team. If we can't agree, VP makes the call and PM commits. Revisit with data.
- Meeting style: Agendas required for 1:1s (PM owns). Action items documented. Async-first for updates; sync for decisions and creative problem-solving.
Feedback + Growth
- How the PM prefers to receive feedback: [To be filled in during conversation -- prompt: "Do you prefer feedback in the moment, in 1:1s, or in writing? How direct can I be?"]
- What "good" feedback looks like from PM to VP: Honest upward feedback on what's working and what's not. Surface blockers early. Flag team morale signals.
- Development goals for the next 6-12 months: [To be co-created at 30-day check-in based on listening tour and early performance data.]
Operating Cadence
- 1:1 frequency: Weekly, 45 minutes. PM owns the agenda. First 15 min: blockers + decisions. Next 15 min: strategy/thinking. Last 15 min: feedback + development.
- Weekly updates: PM sends a brief async update every Friday (Slack or doc): what shipped, what's in flight, what's blocked, what I'm thinking about.
- Product review: Bi-weekly with leadership team. PM presents roadmap progress and key decisions.
- Skip-level: Monthly 30-min check-in with CPO/CEO (starting month 2).
7) 30/60/90-Day + 1-Year Plan
Days 0-30: Listen + Map + De-risk (April 7 - May 6)
Objectives:
- Build trust and relationships with the integrations team, cross-functional partners, and key stakeholders.
- Develop a thorough understanding of the current state: product, technology, customers, competitors, team dynamics.
- Identify the top risks, stuck decisions, and highest-leverage opportunities.
- Establish a working agreement with VP of Product and communication norms with the team.
Key Activities:
- Complete the structured listening tour (15-20 conversations per the stakeholder map).
- Attend all team rituals as an observer/participant; learn the operating rhythm.
- Review existing product specs, roadmaps, metrics dashboards, customer feedback, and support data.
- Shadow 2-3 enterprise customer calls or demos with Sales/CS.
- Have 1:1 coffee chats with every member of the immediate integrations team (eng + design).
Deliverables:
- Completed stakeholder map with notes
- Listening tour synthesis table with themes
- 30-day "state of the union" memo (see Section 8)
- Working agreement with VP of Product (finalized)
- Personal onboarding notes: systems map, glossary additions, open questions
Metrics / Checks:
- Can articulate the top 3 integration opportunities and top 3 risks without notes.
- Every key stakeholder has had at least one substantive 1:1.
- Team members report feeling heard (informal check via buddy or VP).
- No premature commitments or roadmap changes made.
Stakeholder Checkpoints:
- End of week 1: VP of Product check-in (calibrate the plan)
- End of week 2: VP of Product check-in (working agreement finalized)
- Day 28-30: Share state-of-the-union memo with VP of Product first, then broader stakeholders
Guardrails (what NOT to do yet):
- Do NOT reorganize the team, change processes, or cancel existing commitments.
- Do NOT commit to specific roadmap items with sales or customers.
- Do NOT publicly critique past decisions or previous PMs.
- Do NOT skip the listening tour even if pressure mounts to "just ship something."
Days 31-60: Align + Plan + Early Delivery (May 7 - June 5)
Objectives:
- Translate listening tour findings into a clear, prioritized integrations roadmap for the next 2 quarters.
- Unblock at least one stalled initiative and demonstrate momentum.
- Establish the PM operating cadence (sprint rituals, stakeholder updates, decision-making rhythm).
- Deepen relationships and begin earning autonomous decision-making trust.
Key Activities:
- Draft a 2-quarter roadmap with clear prioritization criteria (customer impact, revenue impact, technical feasibility, strategic value).
- Roadmap review sessions: VP of Product, Eng Lead, Design Lead, Sales, CS (iterate based on feedback).
- Identify and unblock the highest-impact stalled initiative -- drive it to resolution.
- Establish sprint planning, review, and retrospective cadence with the team.
- Begin bi-weekly product review presentations to leadership.
- Start a decision log for integration-related decisions.
Deliverables:
- 2-quarter integrations roadmap (prioritized, with rationale)
- Prioritization framework documented and shared
- At least 1 stalled initiative unblocked and in active development
- Sprint cadence and rituals established (documented)
- Decision log initiated
- First bi-weekly product review delivered
Metrics / Checks:
- Roadmap has been reviewed and endorsed by VP of Product, Eng Lead, and Sales.
- At least 1 stalled initiative is unblocked (in sprint or shipped).
- Team reports clarity on priorities (informal pulse check).
- Decision rights are exercised: PM is making sprint-level calls autonomously.
Stakeholder Checkpoints:
- Week 5: Roadmap draft review with VP of Product
- Week 6-7: Roadmap review with Eng Lead, Design Lead, Sales, CS
- Week 8: Formal 60-day check-in with VP of Product (progress, feedback, plan adjustment)
Days 61-90: Execute + Systemize (June 6 - July 5)
Objectives:
- Drive execution on the roadmap: ship at least one major integration milestone (beta or GA).
- Systemize the operating cadence so it runs without heroics.
- Demonstrate measurable improvement in team morale and stakeholder confidence.
- Operate with high autonomy; VP of Product is in coaching mode.
Key Activities:
- Drive the top-priority integration to beta or GA (hands-on PM work: specs, trade-offs, stakeholder alignment, launch coordination).
- Conduct a retrospective on the first shipped milestone: what worked, what to improve.
- Formalize the integrations team's operating playbook (how we spec, how we prioritize, how we launch).
- Begin outbound communication: share the integrations roadmap with enterprise customers (via CS or directly).
- Initiate partnership conversations for the next wave of integrations.
- Run a team health check or mini-survey to measure morale trajectory.
Deliverables:
- At least 1 major integration in beta or shipped to GA
- Post-launch retrospective document
- Integrations team operating playbook (v1)
- Customer-facing roadmap overview (shared via CS or directly)
- Team health survey results + action plan
- Next-quarter plan drafted
Metrics / Checks:
- 1+ major integration milestone shipped (beta or GA).
- Cross-functional partners rate collaboration as "good" or better (informal check or lightweight survey).
- Team morale shows improvement (eNPS, buddy/manager qualitative signals, retention signals).
- PM is operating with high autonomy: VP of Product is not in the critical path for day-to-day decisions.
- Stakeholders (Sales, CS) report improved roadmap visibility and communication.
Handoffs / Ownership:
- PM fully owns: sprint prioritization, integration specs, stakeholder communication, decision log.
- PM co-owns with VP: quarterly roadmap, headcount planning, executive presentations.
- PM has established: direct relationships with key integration partners (no longer mediated through VP).
1 Year: Trajectory (April 2026 - April 2027)
Outcomes the PM Owns:
- Enterprise integrations are a recognized competitive advantage cited in sales materials and customer testimonials.
- Integration adoption among enterprise customers has increased measurably (target: define baseline at day 60 and set a 1-year goal, e.g., X% increase in enterprises using 3+ integrations).
- The integrations team is stable, high-performing, and has not had additional turnover driven by PM-related dysfunction.
- A robust integration partner ecosystem is in place with clear partner tiers and a self-serve integration path in development.
Capabilities the PM Must Build:
- Deep enterprise customer empathy: regular cadence of customer conversations and feedback loops.
- Partnership management: ability to negotiate, prioritize, and manage external integration partners.
- Data-driven prioritization: integration metrics are well-instrumented and drive decisions.
- Cross-functional influence: the PM is a trusted voice in executive product reviews and strategic planning.
Team / Process Systems to Strengthen:
- Integration launch playbook (repeatable, including partner coordination, documentation, sales enablement).
- Integration quality and reliability framework (SLAs, monitoring, incident response).
- Scalable partner onboarding process (reduce marginal cost of adding new integrations).
- Succession and knowledge management: documentation and processes that survive PM transitions (a direct lesson from the team's history).
8) 30-Day State-of-the-Union Memo (Template)
To be completed by approximately May 2 (day 26) and shared with VP of Product for review before broader distribution.
What I Did
- Listening tour coverage: [List everyone met, grouped by function. Note any gaps.]
- Documents and data reviewed: [Key docs, dashboards, customer feedback sources.]
- What I shipped/produced: [Week-1 first contribution, any other early artifacts.]
What I Heard (Themes)
Theme 1: [e.g., Roadmap clarity and prioritization]
- Evidence: [Who said what -- anonymized where appropriate]
- Tension / trade-off: [e.g., Sales wants customer-specific integrations; Eng wants platform investment first]
Theme 2: [e.g., Team morale and PM stability]
- Evidence:
- Tension / trade-off:
Theme 3: [e.g., Technical debt and reliability]
- Evidence:
- Tension / trade-off:
Theme 4: [e.g., Enterprise customer expectations vs. current capabilities]
- Evidence:
- Tension / trade-off:
Theme 5: [e.g., Partner ecosystem strategy]
- Evidence:
- Tension / trade-off:
My Current Understanding
- What seems true: [3-5 bullets on the state of enterprise integrations based on evidence]
- What I'm unsure about: [2-3 open questions where I need more data or input]
Proposed Focus (Next 30-60 Days)
- Focus area 1: [e.g., Establish a clear prioritization framework and draft a 2-quarter roadmap]
- Focus area 2: [e.g., Unblock [specific stalled initiative] -- it has the highest customer impact and can build team momentum]
- Focus area 3: [e.g., Stabilize the team operating cadence so we have a predictable rhythm]
Open Questions
- Q1: [e.g., What is the company's appetite for investing in a self-serve integration platform vs. high-touch partnerships?]
- Q2: [e.g., How should we balance enterprise-specific integration requests vs. platform-level capabilities?]
- Q3: [e.g., Is there budget/appetite for additional engineering headcount on integrations?]
Risks
- Risk 1: [e.g., If we don't address the top stalled initiative by day 60, we risk losing [key customer].]
- Risk 2: [e.g., Team morale is fragile; any perceived "thrash" in priorities could trigger attrition.]
Next Steps
- Step 1: [e.g., Review this memo with VP of Product and calibrate the 60-day plan.]
- Step 2: [e.g., Schedule a roadmap alignment session with Eng Lead, Design Lead, and Sales for week 5.]
- Step 3: [e.g., Share a summary of listening tour themes with the team (transparency builds trust).]
9) Risks / Open Questions / Next Steps
Risks (Prioritized)
| # | Risk | Likelihood | Impact | Mitigation | Owner | Checkpoint |
|---|---|---|---|---|---|---|
| 1 | Team skepticism erodes before trust is built. The team has been burned twice. If the new PM doesn't explicitly acknowledge the history and demonstrate listening-first behavior, passive resistance will calcify. | High | High | VP of Product communicates the onboarding philosophy to the team before day 1. PM follows the listening-first plan rigorously. Buddy provides real-time morale feedback. | VP of Product + PM | Weekly buddy check-ins; VP pulse check at day 14 and day 30. |
| 2 | Pressure to ship prematurely. Sales or leadership may push for immediate roadmap commitments, undermining the listen-first approach. | Medium | High | VP of Product provides explicit air cover. PM's 30/60/90 plan is shared with Sales and CS leadership so they understand the timeline. PM offers a "quick win" target (unblock one stalled initiative) to demonstrate momentum without overpromitting. | VP of Product | Day 14 check: is anyone pressuring the PM to commit? |
| 3 | Context gaps from poor documentation during PM vacancy. Key decisions, customer commitments, or technical context may be undocumented or lost. | High | Medium | Architecture walkthrough on day 2. Eng Lead and buddy are explicitly tasked with surfacing "oral history." PM documents everything she learns (builds the institutional knowledge base as she goes). | PM + Eng Lead | Week 2: PM flags any critical gaps to VP. |
| 4 | Remote onboarding isolation. US/EU time zone spread could mean the PM misses organic interactions or feels disconnected. | Medium | Medium | Daily buddy check-ins in week 1, then 3x/week in weeks 2-4. Overlap hours established. Virtual coffees with cross-functional peers. PM is encouraged to over-communicate on Slack in the first 30 days. | PM + Buddy | Day 7 and day 14: PM self-reports on isolation/connection. |
| 5 | Ambiguous ownership transition. If the VP of Product has been acting as interim PM, the handoff of decision rights and stakeholder relationships may be unclear. | Medium | Medium | Working agreement explicitly defines decision rights (Section 6). VP communicates the transition to stakeholders: "She's now the decision-maker for enterprise integrations." | VP of Product | Day 10: working agreement finalized. Day 30: stakeholders confirm they know who to go to. |
Open Questions (Need Resolution)
| # | Question | Who Can Answer | Resolve By |
|---|---|---|---|
| 1 | What is the new PM's preferred working hours and time zone? What overlap windows work for US and EU team members? | New PM + VP of Product | Before day 1 (preboarding call) |
| 2 | Who specifically will be the buddy? Has this person agreed and do they have protected time? | VP of Product | By April 2 |
| 3 | Who is the PM peer serving as the "first pair"? | VP of Product | By April 2 |
| 4 | What is the current state of the stalled integration initiatives? Which one is the best candidate for an early unblock? | Eng Lead | Week 1 (architecture walkthrough) |
| 5 | Are there any imminent customer commitments or contractual deadlines related to integrations that constrain the 30-day listening period? | Sales Lead + CS Lead | Before day 1 (VP of Product to confirm) |
| 6 | What is the company's strategic posture on build-vs-partner for integrations? Is there executive alignment? | VP of Product + CEO/CPO | By day 30 (listening tour) |
| 7 | Is there budget for additional headcount on the integrations team, or is the current team the constraint? | VP of Product | By day 60 |
Next Steps (Immediate Actions)
| # | Action | Owner | Due Date |
|---|---|---|---|
| 1 | Assign and brief the buddy. Ensure they have 30-60 min/day protected for the first 2 weeks. | VP of Product | April 2 |
| 2 | Assign the "first pair" PM peer and brief them on the pairing plan. | VP of Product | April 2 |
| 3 | Prepare and send the context pack (or as much of it as exists). Label gaps honestly. | VP of Product | April 3 |
| 4 | Send the welcome email/DM to the new PM with context pack, buddy intro, and week 1 plan. | VP of Product | April 3 |
| 5 | Complete all preboarding logistics (IT access, calendar invites, Slack channels). | IT + VP of Product | April 4 |
| 6 | Post the team announcement in #enterprise-integrations and #product-team. | VP of Product | April 4 |
| 7 | Confirm the new PM's time zone and preferred working hours. Adjust week-1 schedule if needed. | VP of Product | April 4 |
| 8 | Schedule all week-1 stakeholder intro meetings (block calendars now). | VP of Product (or EA) | April 4 |
| 9 | Prepare a brief "how we got here" summary for the new PM: what happened with prior PM transitions, what the team needs, and what not to repeat. (Honest, not gossipy.) | VP of Product | April 3 |
Quality Self-Assessment
Scored against RUBRIC.md:
| Dimension | Score | Rationale |
|---|---|---|
| 1. Role clarity + success definition | 5 | 30/60/90 + 1-year milestones are outcome-based, measurable, and stakeholder-aligned. Each phase has clear "what done looks like." |
| 2. Belonging + social integration | 5 | Buddy + first pair assigned with clear responsibilities. Daily check-ins in week 1. Virtual team lunch on day 1. Cross-functional coffees. Remote isolation explicitly mitigated. No "sit alone and read" time. |
| 3. Listening tour design + synthesis | 5 | Stakeholder map covers all critical interfaces (15+ people across functions, including external partners and customers). Question guide is role-specific with specificity-forcing questions. Synthesis table and state-of-the-union memo template are ready to fill. |
| 4. Working agreement (relationship design) | 5 | Decision rights table, communication norms, feedback cadence, and operating rhythms are explicit and documented. Both VP and PM expectations are captured. Living document with revision points. |
| 5. Practicality + operational readiness | 5 | Calendar-ready first-week schedule with times, attendees, and purposes. Preboarding checklist has owners and due dates. All next steps have owners and deadlines. |
| 6. Risk awareness | 5 | 5 risks identified with likelihood, impact, mitigations, owners, and checkpoints. 7 open questions with owners and resolve-by dates. 9 immediate next steps with owners and due dates. Risks are specific to the context (PM turnover history, remote, morale). |
| Total | 30/30 |
Interpretation: Excellent; ready to run.
This Onboarding Pack was designed for a Senior PM joining a Series C, fully remote B2B collaboration SaaS company (250 people, US/EU) to own the enterprise integrations product line. It explicitly addresses the team context of 2 PM turnovers and fragile morale by prioritizing trust, listening, and belonging over speed. All sections are ready for the VP of Product to customize with specific names, links, and details.