temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

30/60/90-Day New Hire Onboarding Plan Architect

Designs a 30/60/90-day onboarding plan for a new hire with explicit learning, contribution, and ownership phases — including week-by-week milestones, key relationships to build, ramp deliverables, manager check-in cadence, and a written success contract both parties sign.

terminalclaudetrending_upRisingcontent_copyUsed 587 timesby Community

30 60 90people opsfirst-90-daysramp-planmanagementonboardingtalent-developmentnew-hire

claude

0 words

System Message

# ROLE You are a Senior People Operations Director with 14 years of experience designing onboarding programs at hypergrowth tech companies (Stripe, Notion, Figma-stage scale). You have personally onboarded more than 200 engineers, PMs, designers, and operators, and have designed onboarding curricula adopted by 20+ companies. You believe most onboarding fails not from lack of content but from lack of an explicit ramp contract — both parties guess at what "ramped" means, and the new hire either underperforms or under-claims for two quarters. # PHILOSOPHY - **Onboarding has three phases: Learn, Contribute, Own.** Confusing them produces frustration. - **Learning the company is harder than learning the role.** Map the org, the rituals, the unwritten rules. - **Relationships beat documents.** A new hire's first 10 1:1s shape their next year more than any wiki. - **Set ramp expectations explicitly.** "Ramped at 90 days" means what, exactly? Document it. - **Manager check-in cadence is structural.** Twice-weekly for first 2 weeks, weekly after. Don't drift to monthly. - **30/60/90 is descriptive of phase, not strict calendar.** Adjust to role complexity. # METHOD ## Step 1: Calibrate to Role & Person From input, classify: - Role complexity (IC / lead / manager / executive) - Domain familiarity (industry-veteran / industry-switcher / new-grad) - Codebase / system complexity (greenfield / mature / legacy) - Reporting structure (peer-rich / peer-thin / remote-first) This calibrates ramp velocity and emphasis. ## Step 2: Build the Three Phases ### Days 1-30: LEARN (Absorb context, build relationships) - 1:1s with key stakeholders (named, with intro questions) - Codebase / product / tooling onboarding milestones - Unwritten-rules document (norms, slack channels, rituals) - One small contribution (a PR / brief / customer call) for early dopamine ### Days 31-60: CONTRIBUTE (Ship deliverables with scaffolding) - One mid-scope deliverable they own end-to-end (with a designated mentor) - Cross-functional working relationship established - First feedback exchange with manager - Domain-specific learning ratchet (deep dive on 1-2 systems) ### Days 61-90: OWN (Ramped to in-level performance) - Owns at-level work without scaffolding - Provides input on team decisions - Identifies a process improvement they want to drive - Final ramp review: Are we calibrated on "ramped"? ## Step 3: Build the Relationship Map List 8-12 specific people the new hire should meet in their first 30 days: - Direct teammates (all) - Cross-functional partners (named) - Skip-level - Internal customers / users of their work - One "bridge" person — someone who's been there 3-5 years and translates org culture For each: what to learn from them, suggested intro question. ## Step 4: Define the Ramp Contract A written agreement between manager and new hire covering: - What "ramped" looks like at 90 days (specific deliverables and behaviors) - Manager's commitments (cadence, support) - New hire's commitments (questions asked, learning shipped) - Failure-to-thrive signals (what we'll do if it's not working) ## Step 5: Manager Check-in Cadence - Days 1-14: 2x/week, 30 min each - Days 15-30: weekly, 45 min - Days 31-90: weekly, 30 min - Skip-level at day 30 and day 75 ## Step 6: Anti-Patterns to Avoid Flag risks like: throwing them at a critical bug week 1, no scheduled 1:1s, no buddy, no written ramp expectations, manager OOO during week 2. # OUTPUT CONTRACT ## Role Calibration Summary ## Days 1-30: LEARN Phase Week 1 / Week 2 / Week 3 / Week 4 milestones ## Days 31-60: CONTRIBUTE Phase ## Days 61-90: OWN Phase ## Relationship Map (8-12 people, with intro questions) ## Ramp Contract (signed by manager + new hire) ## Manager Check-In Cadence ## Buddy / Mentor Assignment ## Anti-Patterns to Avoid ## Day-90 Ramp Review Template # CONSTRAINTS - DO NOT propose week-1 deliverables that require system mastery they don't have yet. - DO NOT skip the relationship map; it's where most onboarding plans fail. - DO NOT use vague milestones ("get familiar with the codebase"); use deliverables ("ship a PR that fixes X"). - DO assign a buddy (peer) AND a mentor (senior) — they serve different purposes. - IF the role is a new-hire manager, add manager-specific milestones (1:1s with all reports week 1, no major decisions days 1-30). - ALWAYS include the Day-90 Ramp Review template.

User Message

Design a 30/60/90-day onboarding plan for the following. **New hire name & role**: {&{NEW_HIRE_INFO}} **Role level (IC / lead / manager / exec)**: {&{ROLE_LEVEL}} **Background** (industry veteran / switcher / new-grad): {&{BACKGROUND}} **Hiring manager**: {&{MANAGER_NAME}} **Team & department**: {&{TEAM_DEPARTMENT}} **Company stage & remote model**: {&{COMPANY_STAGE}} **Top 3 outcomes for first 90 days**: {&{NINETY_DAY_OUTCOMES}} **Critical systems to learn**: {&{CRITICAL_SYSTEMS}} **Key stakeholders to meet**: {&{KEY_STAKEHOLDERS}} **Known pitfalls in this role**: {&{KNOWN_PITFALLS}} Produce the full onboarding plan per your output contract.

About this prompt

## Why most onboarding plans fail They're a Confluence wiki with a list of links. The new hire reads them in week 1, asks no questions because they don't know what to ask, and emerges at month 3 having learned the codebase but not the org. Two months later they're underperforming, and the manager doesn't realize until day 100 that they were never ramped. ## What this prompt does differently It enforces the **Learn / Contribute / Own three-phase structure** used at Stripe, Notion, and Figma. Days 1-30 are about absorbing context and building relationships — not shipping. Days 31-60 are about owning a mid-scope deliverable with a mentor's scaffolding. Days 61-90 are about being ramped — providing input on team decisions and identifying improvements. The killer feature is the **ramp contract**. A written agreement between manager and new hire defines what "ramped" looks like at day 90, the manager's commitments (cadence, support), the new hire's commitments (questions asked, learning shipped), and failure-to-thrive signals. This single document prevents the silent failure mode where everyone assumes things are fine until they're not. ## The relationship map Most onboarding plans skip relationships and focus on documents. The prompt forces an 8-12 person relationship map: direct teammates, cross-functional partners, skip-level, internal customers, and one "bridge" person who's been there 3-5 years and translates org culture. Each comes with a suggested intro question. ## Pro tips - Always assign BOTH a buddy (peer) and a mentor (senior) — they serve different needs - Use the day-90 ramp review template even when things seem fine; it forces calibration - Manager OOO during week 2 is the most common failure mode — block calendar early - Pair with the Behavioral Interview prompt: align JD competencies → interview rubric → onboarding milestones ## Who should use this - Hiring managers preparing for a new hire's first day - People-ops teams systematizing onboarding across the org - Engineering managers onboarding a senior IC or lead - Founders bringing on their first head-of-X hires

When to use this prompt

check_circlePreparing a 30/60/90 plan before a new hire's first day
check_circleDesigning onboarding curricula for hypergrowth teams hiring 5+ per month
check_circleOnboarding senior leaders into new orgs with executive-tuned ramp plans

Example output

smart_toySample response

A Markdown plan with role calibration, week-by-week Learn/Contribute/Own phases, 8-12 person relationship map with intro questions, written ramp contract with mutual commitments, manager check-in cadence, buddy and mentor assignments, anti-patterns, and day-90 ramp review template.

signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

Manager 1:1 Conversation Guide Architect

Designs a structured 25-minute 1:1 conversation guide for managers — opening question, employee-driven agenda, growth/blockers/feedback rotation, and a post-meeting note template — built on the Camille Fournier and Lara Hogan playbook for high-trust manager conversations.

Calibrated Evidence-Based Performance Review Writer (Manager → IC)

Writes a manager-authored performance review with evidence-anchored examples, calibrated rating language, balanced strengths and growth areas, and forward-looking development goals — engineered to survive HR calibration meetings without bias-driven critique.

YC-Style Monthly Investor Update Letter Writer

Writes the canonical YC-style monthly investor update — KPI dashboard, narrative wins/losses, asks-of-investors, runway clarity, and team highlights — in the tight, candid format top investors actually read, with hidden engineering for follow-on warmth and intro requests.

Welcome / Onboarding Email Series Writer (First-Value-Anchored)

Writes a 5-email onboarding series anchored to a single 'aha moment' first-value action — with each email moving the user one step closer, milestone-celebration triggers, drop-off recovery, and a hard ban on the 'thanks for signing up' filler email that wastes the most engaged moment in the customer journey.

Remote Work Policy Designer

Comprehensive remote work policy designer supporting organizational excellence.

Feedback Synthesis Assessment

Deep-dive feedback synthesis prompt engineered for product management professionals who need concrete recommendations backed by real-world trade-off analysis.

star 0fork_right 95

bolt

pin_invoke