👋 Product Onboarding (New team members)

Sessions
6

The process in detail

01

1. About our product

5 steps
  1. 1

    Product Team Onboarding Guide

  2. 2

    Product Overview & Demo

  3. 3

    Value Proposition & Key Differentiators

  4. 4

    Target Audience & Persona Overview

  5. 5

    Who Are Our Competitors?

Read the full text
1. Product Team Onboarding Guide

Welcome to the Product Team! This guide is designed to get you up to speed on our product, processes, team dynamics, and expectations.

In here you will find the team.

Choose one or more
  • 👤 [ NAME] Role
  • 👤 [ NAME] Role
  • 👤 [ NAME] Role
2. Product Overview & Demo

Product Summary: [Insert 2–3 sentence overview of the product, key target audience, and primary use cases].

Product Demo Video: [Link to 5–10 min product walkthrough video / Loom recording]

Try It Yourself. Here is a link to our product staging/demo environment. Link here.

3. Value Proposition & Key Differentiators

[Describe the primary value we deliver to customers and the key problem we solve].

Key Differentiators:

•[Differentiator 1]: [e.g., Unmatched speed-to-value, proprietary automation engine]
•[Differentiator 2]: [e.g., Seamless integration ecosystem]
•[Differentiator 3]: [e.g., Intuitive user experience tailored for enterprise teams]
4. Target Audience & Persona Overview
•Primary Persona: [e.g., Product Leaders / Operations Managers] – [Key pain points and priorities].
•Secondary Persona: [e.g., End Users / Individual Contributors] – [Key pain points and priorities].

User Persona Documentation below:

Upload files or add links
5. Who Are Our Competitors?

Direct Competitors:

•[Competitor A]: [Strengths vs. Weaknesses / How we position against them]
•[Competitor B]: [Strengths vs. Weaknesses / How we position against them]

Here is our Competitive Analysis Board / Deck:

Upload files or add links
02

2. How We Define Our Roadmap

3 steps
  1. 1

    Cadence & Cadence Placeholder

  2. 2

    Translating Strategy & Goals into Initiatives

  3. 3

    Problems, Not Solutions

Read the full text
1. Cadence & Cadence Placeholder
•Roadmap Planning Cycle: [Annually / Bi-annually / Quarterly — Default Placeholder: Annually]
•Review & Adjustment Frequency: [e.g., Monthly check-ins / Mid-year calibration]
Choose one
  • Option 1
  • Option 2
2. Translating Strategy & Goals into Initiatives

Our roadmap is directly tied to business outcomes. Here is how company goals translate into our roadmap:

1.Company Objectives & Key Results (OKRs): Company leaders set high-level strategic priorities for the period [Link to current Company OKRs].
2.Identification of Key Initiatives: Product leadership turns high-level goals into target problem spaces and strategic initiatives.

Cross-Functional Inputs:

◦Client & User Requests: Voice of Customer feedback gathered via research, support tickets, and product analytics.
◦Sales & Revenue Needs: High-impact features required to unlock new deals or retain key accounts.
◦Technical Health & Architecture: Platform stability, tech debt, security, and scalability requirements.

Prioritization Framework:

•We evaluate potential investments based on Cost vs. Benefit (e.g., ROI, RICE framework, implementation effort vs. expected revenue/retention impact).
Choose one
  • Option 1
  • Option 2
3. Problems, Not Solutions

Focus on Outcome, Not Output: Roadmap items define the problem statement and desired customer/business outcome, not the final feature design or technical architecture.

•Solution Discovery: How a problem gets solved is determined during the discovery and initiative phase by cross-functional feature teams, not dictated upfront on the roadmap.
•Current Roadmap Board
Upload files or add links
03

3. How We Work Based on Initiatives

3 steps

In this session, you will learn how initiatives move from initial problem framing to impact evaluation, including core artifacts and cross-functional RACI handoffs. Please review each lifecycle phase, verify how your role collaborates with neighboring teams, and submit your questions or boundary checks.

  1. 1

    🧭 Understand the Five Lifecycle Phases

  2. 2

    📄 Review Core Initiative Artifacts

  3. 3

    🔄 Check Role Handoffs & Boundaries

Read the full text
1. 🧭 Understand the Five Lifecycle Phases

Every major product initiative moves through five sequential phases designed to minimize risk and maximize delivery velocity.

Here is the operational breakdown:

1.Problem Definition & Framing: Establishing business rationale, high-level scope, measurable target metrics, and primary target personas before committing design or engineering capacity.
2.Discovery & Validation: Running customer research, testing technical feasibility, and validating early prototypes to de-risk assumptions.
3.Execution & Build: Decomposing validated scopes into epics and sprint stories, followed by iterative development, QA, and integration testing.
4.Launch & Enablement: Aligning GTM collateral, internal customer-facing training, release notes, and deployment readiness.
5.Impact Evaluation: Reviewing live telemetry and post-launch outcomes against the original baseline success metrics established in phase 1.

Select the statement below that best describes your baseline familiarity with this delivery model.

Choose one
  • 🟢 Clear and familiar — I understand all five phases
  • 🟡 Mostly clear — Need a refresher on discovery vs. execution boundaries
  • 🔴 New to me — Need walkthrough on when initiatives transition
2. 📄 Review Core Initiative Artifacts

Standardized artifacts ensure smooth cross-functional coordination and prevent knowledge silos across delivery cycles.

The two central repositories used throughout an initiative are:

•Product Brief / PRD: Captures problem context, user stories, acceptance criteria, edge cases, and success metrics. Review the baseline format here: [Link to PRD Template].
•Decision Log & Research Repository: Houses customer interview summaries, prototype usability testing results, technical trade-off records, and architecture reviews: [Link to Research & Decision Repository].

Review the linked templates, then acknowledge that you know where to consult and document initiative progress.

Choose one
  • ✅ I have reviewed the templates and know where to access them
  • ⚠️ I need access permissions or clarification on template usage
3. 🔄 Check Role Handoffs & Boundaries

High-performing cross-functional teams depend on explicit handoffs and shared ownership at boundary transitions.

Review the core functional boundaries:

•Product Management (PM): Owns problem definition and strategic priority. Hands validated requirements to Design and Engineering; receives market demand and churn themes from Sales and CS.
•Product Design (UX/UI): Owns user journeys, prototypes, and usability/UI testing. Hands component specs and interactive flows to Engineering; receives validated briefs and success metrics from PM.
•Engineering (Dev/QA): Owns architecture, code implementation, automated testing, and deployment. Hands stable release candidate builds and technical release notes to PM and PMM; receives acceptance criteria from Design and PM.
•Product Marketing (PMM): Owns positioning, sales enablement, and launch campaigns. Hands training decks, battle cards, and collateral to Sales and CS; receives launch dates and scope details from PM.
•Sales & Customer Success (CS): Owns prospect pipeline, onboarding, and customer retention. Hands synthesized user feedback and churn trends to PM; receives release announcements and training from PMM and PM.

Reflect on your daily interactions: identify the single handoff interface that currently has the most friction or ambiguity for your discipline.

Write a note
04

4. Roles and Responsibilities

05

5. Meetings & Focus time

4 steps

Review our operating principles around protecting focus time, defaulting to asynchronous tools, and participating in structured ceremonies. Acknowledge these team standards and commit your personal focus routine so we maintain high velocity without calendar drag.

  1. 1

    ⏱️ Adopt Our Async-First Mindset

  2. 2

    🛠️ Review Approved Async Workflows

  3. 3

    📅 Check Recurring Ceremony Cadence

  4. 4

    🛡️ Establish Your Focus Schedule

Read the full text
1. ⏱️ Adopt Our Async-First Mindset

Time is our most critical non-renewable asset. Booking a 30- or 60-minute meeting is easy, but it often creates an illusion of progress while delaying actual delivery.

Waiting days for an open calendar slot stalls decisions, while constant context-switching fragments deep work across product, engineering, and design.

Our baseline operating rules:

•Default to async: If an update, spec review, or decision can be solved with a recording and a Nova Session - without a meeting.
•Write before talking: Formulate the context, problem, and trade-offs in writing first so people can digest on their schedule.
•Protect focus blocks: Consolidate required discussions to preserve contiguous half-days for build work.

Confirm your alignment with our async-first culture below.

Choose one
  • 🚀 I understand and commit to defaulting to async communication
  • 🤔 I understand the principles but have questions regarding day-to-day edge cases
2. 🛠️ Review Approved Async Workflows

We use specific channels to communicate complex work asynchronously without scheduling status calls.

Core patterns:

•Screen recordings (Loom): Use short, 3- to 5-minute video walkthroughs to demo UI flows, explain user stories, or frame complex PRDs before requesting feedback.
•Contextual session threads: Keep discussions where the work lives. Use Nova to lead that discussion.
•Centralized decision logs: Document final choices, assumptions, and trade-offs in the project Decision Log (inside Nova) so teammates stay informed without being present in real-time.

Below discover how to lead each type of meetings async:

Choose one or more
  • Informative meetings
  • Discussion meetings
  • Decision meetings
3. 📅 Check Recurring Ceremony Cadence

When live collaboration is required, we run lean, agenda-driven ceremonies with pre-reads. Review our standard team rhythm:

•Async Daily Check-in: Daily by 9:30 AM via Slack #team-standup (blockers, yesterday's wins, today's focus).
•Sprint / Cycle Planning: Bi-weekly Mondays at 10:00 AM (requires pre-groomed backlog).
•Backlog Refinement: Bi-weekly Thursdays at 11:00 AM.
•Sprint Retrospective: [Add]

Select all recurring ceremonies that you have reviewed and added to your calendar.

Choose one or more
  • 💬 Async Daily Standup (Slack)
  • 📐 Cycle Planning (Bi-weekly Mondays)
  • 🎨 Design Reviews & Critiques (Weekly Wednesdays)
  • ⚙️ Backlog Refinement (Bi-weekly Thursdays)
  • 🔄 Sprint Retrospective (Bi-weekly Fridays)
4. 🛡️ Establish Your Focus Schedule

To prevent fragmented days, every team member defines recurring deep work blocks on their public calendar.

Use this format to publish your working cadence:

•Core Deep Work Hours: (e.g., Tuesday & Thursday mornings 9:00 AM - 1:00 PM)
•Async Communication Window: (e.g., 9:30 AM - 10:30 AM and 4:00 PM - 5:00 PM)
•Meeting Availability: (e.g., Monday & Wednesday afternoons)
•Slack Status Habit: (e.g., "🎧 Deep Focus - checking messages at 1:00 PM")
Choose one
  • Option 1
  • Option 2
06

6. Your Success

3 steps

Welcome to our company standards on workplace mindset, feedback cadences, and performance evaluations. Please review each core standard, acknowledge your understanding, and outline your growth goals for your direct manager to review in your first 1:1.

  1. 1

    🌟 Acknowledge Workplace Mindset Standards

  2. 2

    🔄 Confirm Feedback and Evaluation Cadences

  3. 3

    🎯 Frame Your Initial Growth Commitments

Read the full text
1. 🌟 Acknowledge Workplace Mindset Standards

At our company, supporting your success means establishing clear behavioral expectations and problem-solving standards from day one. Our day-to-day culture rests on three foundational pillars:

•Proactivity & Ownership: Take full accountability from initial problem discovery through post-launch delivery. This includes owning your estimation alignments and proactively surfacing blockers before they become delivery crises.
•Customer-Centric Mindset: Ground product and operational decisions in verified user problems, qualitative insights from Sales and Customer Success, and empirical data rather than gut assumptions.
•Constructive Conflict Resolution: Focus discussions on objective data and user outcomes rather than personal perspectives. We actively practice Disagree and Commit: engage in rigorous, healthy debate during the discovery phase, but once a decision is finalized, align fully behind execution.

Review these core cultural behaviors and select the statement below that reflects your alignment.

Choose one
  • 🚀 I understand and commit to these cultural standards
  • 💬 I have reviewed the standards and have questions for my manager
2. 🔄 Confirm Feedback and Evaluation Cadences

We foster continuous growth through predictable, transparent feedback loops rather than unexpected evaluation surprises.

Our feedback architecture includes:

•1:1 Meetings: monthly structured syncs with your direct manager dedicated to tactical unblocking, long-term career growth, and immediate course corrections.
•Peer Feedback: Continuous informal peer input alongside formal quarterly reviews to ensure multi-perspective development.
•Evaluation Cycles: Formal Annual performance reviews evaluating Objective Delivery (OKRs and initiative execution), Product Quality & Craft (documentation clarity and discovery rigor), Collaboration & Leadership (cross-functional handoffs and async communication), and Continuous Learning.

Acknowledge your understanding of these rhythms and note any scheduling considerations.

Choose one
  • ✅ Clear on the feedback rhythms and review cycles
  • ❓ Need clarification on how peer reviews are conducted
3. 🎯 Frame Your Initial Growth Commitments

To operationalize these standards, draft your initial development focus areas for your upcoming manager 1:1.

Structure your reflection across these four key evaluation dimensions:

1.Objective Delivery: One practice you will adopt to maintain estimation accuracy and initiative velocity.
2.Product Quality & Craft: How you plan to incorporate cross-departmental insights (such as Customer Success or Sales feedback) into your daily workflow.
3.Collaboration & Ownership: Your personal standard for transparent asynchronous communication across teams.
4.Growth & Learning: One technical or domain skill you intend to develop over the next evaluation cycle.
Choose one
  • Option 1
  • Option 2