What the Onboarding Document Creator actually produces

# 30-60-90 Day Plan: Senior Product Manager, Patient-Facing Mobile App **Welcome to Vantara Health.** We're thrilled to have you leading our patient app roadmap. This plan outlines how we'll set you up for success and how you'll drive impact in your first three months. --- ## 30 DAYS: FOUNDATION & IMMERSION **Goal:** Understand the product, users, business context, and team dynamics. Build relationships across engineering, design, and clinical teams. ### Key Activities - **Week 1: Onboarding Essentials** - Complete HR/IT setup, systems access, security training - Meet VP of Product (your manager); review org structure and product vision - Tour clinical workflows with clinical team lead; shadow a patient using the app - Review current roadmap, OKRs, and recent release notes - **Week 2: Product Deep Dive** - Product strategy session with VP of Product; clarify success metrics - Meet engineering lead; understand technical architecture, constraints, and pipeline - Meet design lead; review design system and current wireframes - Analyze 5-10 user interviews or support tickets to identify pain points - **Week 3-4: Stakeholder Alignment** - 1:1s with each direct collaborator (Engineering, Design, Clinical, Analytics) - Review data: usage metrics, retention, NPS, support volume, clinical efficacy data - Identify 2-3 immediate opportunities or concerns in current roadmap - Draft summary of initial observations ### Success Metrics (30 Days) - [ ] Complete all system access and orientation - [ ] Attend 2+ user observation sessions - [ ] 1:1s completed with VP of Product, engineering lead, design lead, clinical lead - [ ] Written summary of product landscape, user needs, and team strengths/gaps - [ ] Identify and document 3+ potential roadmap adjustments --- ## 60 DAYS: STRATEGY & OWNERSHIP **Goal:** Develop a validated perspective on roadmap priorities. Own your first small-to-medium initiative from conception through planning. ### Key Activities - **Week 5-6: Data & Validation** - Deep-dive analytics review with Analytics team; define leading/lagging indicators - Conduct 3-5 user interviews or focus groups on a specific feature area - Competitive analysis and clinical landscape research - Propose updated success metrics and product health dashboard - **Week 7-8: Roadmap Planning** - Lead roadmap planning session with engineering, design, and clinical stakeholders - Present 3-6 month roadmap draft with clear prioritization rationale - Define OKRs for your product area (align with company goals) - Secure sign-off from VP of Product and engineering lead - Plan first shipped initiative: write specs, acceptance criteria, design handoff ### Success Metrics (60 Days) - [ ] Product health dashboard live and reviewed weekly by leadership - [ ] 3-5 user interviews completed and synthesized - [ ] Updated 6-month roadmap approved by VP of Product and engineering - [ ] First initiative spec complete; design and engineering review complete - [ ] OKRs documented and linked to company goals --- ## 90 DAYS: EXECUTION & IMPACT **Goal:** Ship a meaningful feature or initiative. Establish yourself as a trusted decision-maker and thought leader on the product team. ### Key Activities - **Week 9-10: Ship & Monitor** - First initiative ships (soft launch or internal beta) - Daily standups during release; monitor technical and user feedback - Prepare launch messaging and communication plan - Plan data collection for post-launch analysis - **Week 11-12: Reflect & Reset** - Analyze launch metrics; conduct post-launch user interviews - Host retrospective with engineering, design, clinical teams - Update roadmap based on learnings; plan next 2-3 initiatives - 90-day check-in with VP of Product; discuss strengths, growth areas, and next phase ### Success Metrics (90 Days) - [ ] First feature/initiative shipped on schedule - [ ] Launch analytics reviewed; post-launch interviews conducted - [ ] Updated roadmap ready for next quarter; prioritization logic documented - [ ] Team feedback: engineering, design, and clinical stakeholders report strong collaboration - [ ] 90-day self and manager assessment completed --- ## KEY CONTACTS | Role | Name | Slack/Email | First Meeting | |------|------|-------------|----------------| | VP of Product | — | [manager Slack] | Day 1 | | Engineering Lead | — | [Slack] | Week 1 | | Design Lead | — | [Slack] | Week 1 | | Clinical Lead | — | [Slack] | Week 1 | | Analytics Lead | — | [Slack] | Week 2 | | Customer Success Lead | — | [Slack] | Week 3 | --- ## TOOLS & RESOURCES **Product & Data** - Figma (design files, design system) - Jira (roadmap, sprint planning, issue tracking) - Amplitude or Mixpanel (usage analytics) - Google Drive (strategy docs, research) - ProductBoard or Roadmunk (roadmap visibility) **Communication & Collaboration** - Slack (team communication) - Notion or Confluence (shared docs, knowledge base) - Zoom (meetings, user interviews) **Clinical & Compliance** - HIPAA training module - Clinical workflow documentation - Regulatory requirements guide **Onboarding** - Vantara Health 101 (company history, mission, culture) - Product strategy deck - User personas and journey maps - Recent board updates or investor materials --- ## EXPECTATIONS & WORKING NORMS **Decision-Making** - You own roadmap prioritization; escalate trade-offs to VP of Product - Decisions require input from engineering (feasibility) and clinical (safety/efficacy) leads - Data and user research inform strategy; assumptions are tested, not assumed **Communication** - Weekly check-ins with VP of Product (Tuesdays, 30 min) - Weekly stand-ups with full product team (engineering, design, clinical) - Async updates in Slack; thoughtful written specs in Jira/Confluence **Collaboration Style** - Clinical input is non-negotiable; clinical outcomes are a north star - Engineering constraints matter; build partnerships, not roadblocks - Design is strategic; involve design early and often - Users are the truth; validate frequently **Pace & Ownership** - You'll own the app roadmap; day-to-day execution is shared with engineering - Expect 1-2 weeks per iteration; shipping cadence is biweekly - You'll balance rapid learning with thoughtful planning --- ## QUICK REFERENCE: FIRST WEEK CHECKLIST - [ ] IT setup complete (laptop, email, VPN, systems access) - [ ] Security and HIPAA training completed - [ ] Meet VP of Product; review role expectations - [ ] Meet engineering, design, and clinical leads - [ ] Access Jira, Figma, analytics, roadmap tool - [ ] Read: company mission, product strategy, current roadmap - [ ] Attend: next sprint planning or team standup - [ ] Schedule user observation session (Week 2) --- ## NOTES FOR SUCCESS - **Be curious, not prescriptive.** You're new to this user base and clinical domain. Ask lots of questions before proposing changes. - **Build trust with clinical and engineering first.** These partnerships make or break your roadmap. - **Validate assumptions fast.** Use user interviews and data to de-risk roadmap decisions. - **Celebrate wins incrementally.** Shipping is hard; acknowledge team effort throughout the journey. - **Stay flexible.** A good plan adapted to reality beats a perfect plan ignored.

This 30-60-90 Day Plan guides a new Senior Product Manager through building product mastery, stakeholder relationships, and strategic ownership of Vantara Health's patient-facing mobile app. The plan is structured in three phases: (1) Foundation—learning the product, users, and team dynamics; (2) Strategy—developing a validated roadmap and owning a first initiative; (3) Execution—shipping a meaningful feature and establishing decision-making authority. Success is measured through concrete milestones (user interviews, roadmap approval, shipped features) and team feedback. Key resources, contacts, and working norms are provided to accelerate onboarding.

## Supporting Your New Senior PM **Your Role in Days 1-30** - Schedule introductions early; flag domain-specific context (regulatory, clinical workflows, user demographics) - Clarify what "success" looks like for the app in the next 12 months; align on metrics - Shield them from urgent-but-low-priority asks; protect time for deep learning - Normalize questions and iteration; this role requires forming new mental models **Potential Friction Points & How to Handle Them** - **Engineering/clinical gaps:** PM roles often sit between these teams. Coach them on translating between languages (clinical efficacy ↔ technical feasibility). Don't let them side with one side. - **Inherited roadmap debt:** They'll likely identify commitments that don't align with user/data reality. Help them surface these diplomatically; use 60-day roadmap planning as the reset point. - **Pace of decisions:** They may move fast coming from another org. Calibrate decisiveness with clinical rigor; "fast but wrong" is costly in healthcare. **Recommended Check-In Cadence** - Weekly 30-min 1:1s (first month), then bi-weekly - Explicit feedback at 30 and 60 days; full 90-day reflection at end - Use these to gauge engagement level, identify unspoken concerns, and adjust support **What Success Looks Like at 90 Days** - They understand user pain points from lived experience (not just data) - Engineering and clinical teams report clear spec-writing and collaborative decision-making - Roadmap reflects both data-driven prioritization and domain knowledge - They've shipped something (even small) on time - They're thinking strategically, not just executing