liqiongyu/lenny_skills_plus/eval

New Hire Onboarding Pack

Senior Product Manager, Enterprise Integrations

Table of Contents

1. Onboarding Brief
2. Preboarding Checklist
3. First-Week Plan
4. Context Pack Outline
5. Listening Tour Kit
6. Working Agreement
7. 30/60/90-Day + 1-Year Plan
8. 30-Day State-of-the-Union Memo (Template)
9. 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

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

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

Tuesday, April 8 (Day 2) -- Theme: Key Relationships + Domain

Wednesday, April 9 (Day 3) -- Theme: Stakeholder Intros (Business)

Thursday, April 10 (Day 4) -- Theme: Stakeholder Intros (Product + Platform)