Onboarding Buddy

---
name: onboarding-buddy
description: Ramp up fast in a new role with a 30/60/90 plan, stakeholder mapping, and quick-win strategy.
category: career
---

## Overview

The first 90 days set the trajectory for your entire tenure — reputations form fast and harden
quickly. Yet most people onboard passively, waiting to be told what to do. This skill builds an
active ramp plan: learn the landscape, map the people, ship early wins, and establish the working
relationships that determine long-term success.

## When to use

- Starting a new job (IC or manager)

- Joining a new team internally

- Returning from extended leave

- Starting a consulting or contract engagement

- Helping a new hire ramp (as a buddy or manager)

## Core concepts

- - **The 30/60/90 frame.** Days 1-30: learn (people, systems, context — ask everything). Days
  31-60: contribute (small wins, start owning something). Days 61-90: lead (drive an initiative,
  show judgment). Announce this frame to your manager so expectations align.
- - **Stakeholder mapping.** In week one, identify: your manager (what do they care about?), key
  peers (who do you depend on?), skip-level (what's their agenda?), and customers/users. Schedule
  intros with all of them.
- - **Learn the unwritten rules.** Every team has them: how decisions really get made, which
  meetings matter, what "done" means, who the informal experts are. Ask your onboarding buddy
  explicitly: "what do newcomers usually get wrong?"
- - **Quick wins are currency.** Ship something visible in the first 30 days — fix a nagging bug,
  improve a doc, unblock a teammate. Early wins buy goodwill and learning time for bigger things.
- - **Document as you learn.** The questions you ask in week one are gold: turn answers into docs,
  runbooks, or onboarding improvements. It helps the next person and signals the exact mindset teams
  want.
- - **Manage up from day one.** Weekly check-ins with your manager: what I'm learning, what I'm
  unsure about, what I'll tackle next. No surprises, ever, in the first 90 days.

## Practical workflow

1. 1. **Before day one.** Clarify logistics (equipment, accounts, schedule), read everything
   available (team docs, recent launches, org chart), and prepare your intro story (background, why
   you joined, what you're excited about).
2. 2. **Week 1: map and meet.** Complete admin, meet the team, schedule 1:1s with every key
   stakeholder. Ask each person: what should I know, who else should I talk to, what's the team's
   biggest challenge right now?
3. 3. **Weeks 2-4: learn deeply.** Shadow workflows, read the codebase/docs/history, understand
   customers. Keep a questions log — and notice which questions nobody can answer (those are
   opportunities).
4. 4. **Draft the 30/60/90 plan.** Write it down and review with your manager in week 2. Include
   learning goals, 2-3 quick wins, and one 90-day initiative. Get explicit agreement on priorities.
5. 5. **Days 31-60: ship and integrate.** Deliver the quick wins, take ownership of a workstream,
   start contributing in meetings (questions first, opinions once informed). Build the peer
   relationships that make work flow.
6. 6. **Days 61-90: demonstrate judgment.** Drive something end-to-end, propose an improvement based
   on your fresh eyes (newcomers see what veterans miss), and establish your working cadence.
7. 7. **The 90-day review.** Self-assess against the plan with your manager: what landed, what
   didn't, what the next 90 days look like. Convert onboarding momentum into a normal operating
   rhythm.

## Common pitfalls

- - **Passive onboarding.** Waiting for assignments instead of seeking understanding. The best
  onboarding is self-directed — nobody will hand you the full picture.
- - **Opining too early.** Criticizing existing systems in week two before understanding why they
  exist. Ask "help me understand why X" before "X should be Y."
- - **Skipping relationships.** Focusing only on tasks while neglecting the people network. When you
  need help in month four, today's coffees pay off.
- - **No quick wins.** Spending 90 days "learning" with nothing shipped. Learning is invisible;
  small deliveries make your ramp legible.
- - **Misaligned expectations.** Assuming you know what success looks like without asking. The
  30/60/90 review with your manager exists to prevent this — use it.
- - **Burnout sprinting.** Trying to prove yourself by working 12-hour days. Sustainable pace from
  the start; exhaustion in month two helps nobody.