PM Onboarding

How we run a product manager apprentice’s first 180 days, day to day. This is the PM companion to PE Apprenticeship (the Product Engineer version); the hiring bar lives in Hiring & Internship and the ladder and attributes in Product Manager. It covers the milestones, the guardrails that make early autonomy safe, the 1:1 cadence, and the day-90 call. A per-person tracker to copy into a fresh doc is at the bottom.

A PM apprentice (APM) starts by learning how PMs decide, working under one, then owns a slice with guidance. The rhythm mirrors the engineer’s 7 / 30 / 60 / 90 shape, adapted to the PM craft: the first “ship” is not code but a real artifact the team uses.

Two people run it. The onboarding buddy (a senior PM) owns the day to day: pairing on Discover and Define, reviewing every artifact, transferring how we decide here. The manager owns growth and fit, using the Product Manager radar. The buddy is the first line for everything; the manager reads trajectory.

The milestones

What an apprentice can do unsupervised by each date, not a checklist to race through. The dates are targets; someone can arrive early or need longer, and that is what the day-90 call is for.

By	Milestone	What it means
Day 7	First artifact in the flow	Has written one real problem statement and gotten it into Glide, and owned one weekly update end to end. Small and guided, but real, none done for them.
Day 30	Runs the cadence	Has taken a small problem through Discover, sat in a Define session, kept the weekly update, and is comfortable in Glide: Requests, Roadmap, the story map.
Day 60	Owns a scoped slice	Takes a small, well-scoped problem from Discover through Define to a clean Build handoff with guidance: a metric defined before build, release notes drafted, the plan kept honest.
Day 90	Decision checkpoint	Enough signal for an honest call: on track for PM, extend the runway, or stop. Never a surprise.
Day 180	Owns a product surface	Owns one product surface end to end, the problem, the call on what to build, shipped and measured, with light supervision. Ready to be a PM.

Week one: get to the first artifact

The first week is built backwards from day 7. Front-load context so the week ends on a real artifact the team uses, not a reading list.

Day 1. Accounts, Glide access, calendars. Meet the buddy, set the standing daily time, walk the guardrails below. Start Core and How Systeric Works.
Days 2 to 3. Shadow the buddy’s cadence: sit in on a Discover conversation and a Define session, read the current roadmap and story map. Pick one small, real observation worth framing.
Days 4 to 5. Write the problem statement for that observation, take it to the buddy, and get it into Glide. Draft the weekly update alongside the buddy and send it. First artifact done.

By the end of week one they have touched the flow once, from a raw observation to a written problem and a shipped update. Weeks two to four widen it: a full Discover, a Define they help run, less pairing.

The day-one welcome messages are role-agnostic; they are in PE Apprenticeship.

Guardrails

These hold for the whole apprenticeship. They are what make it safe to give someone real product influence early. Walk them on day one.

No solutions in Discover. A problem statement carries no solution. If you cannot write the cost of inaction without a fix in it, you have not finished discovering.
Do not commit scope or dates alone. Nothing gets promised to a client or the team without a Define and the PE sign-off. Budgets and dates come out of the process, not a hallway.
Never skip a gate. A Request does not advance without the leadership review; an item does not reach Build without the solution sign-off.
Write it down. Decisions, changes, and asks live in Glide and the weekly update, not in DMs. If it is not written, it did not happen.
Escalate early. A slipping date, an overloaded week, or a doubt surfaces the same day. Silence is the failure mode, for a PM most of all.

The 1:1 cadence

Two 1:1s, two jobs. Same shape as the engineer program.

Buddy 1:1 (daily, then tapering). A senior PM, the first line. Daily for the first weeks to transfer how we frame problems and run sessions, then a few times a week as they find their feet. Unblocking, pairing on live work, reviewing every artifact before it goes out.
Manager 1:1 (weekly, then biweekly). Weekly for the first month, then biweekly. Growth and fit, run against the Product Manager radar: feed the spike, clear the one thinnest spoke holding them below PM. Delegate one rung ahead, then close the gap with review. No surprises: the day-90 call is discussed continuously, never sprung.

The 90-day checkpoint ([date])

Enough signal for an honest call. On track for PM, extend the runway, or stop. Written against the radar, with one concrete moment per attribute, never a surprise.

On track: owning scoped slices with guidance, the judgment spokes (product sense, user insight, strategy) visibly moving.
Extend: the trajectory is right but the reps need longer; re-base the plan and say so.
Stop: a non-negotiable is failing, or the judgment is not moving despite the reps. Kind, clear, early.

Per-person tracker

Copy this into a fresh doc for each apprentice. Keep it live; it is the spine of the manager 1:1.

[Name] · started [date] · buddy [name] · manager [name]

Milestones

Day 7: first artifact in the flow (problem statement in Glide + one weekly update)
Day 30: runs the cadence (Discover, a Define, the weekly update, fluent in Glide)
Day 60: owns a scoped slice (Discover to Build handoff, metric and release notes)
Day 90: decision checkpoint
Day 180: owns a product surface

Shape (the seven PM attributes)

Product sense · User insight · Strategy & prioritization · Delivery · Data & impact · Communication · Influence. Note the spike to feed and the one blocker to clear.

Buddy 1:1 log

[date]: [what they worked on, what to reinforce]

Manager 1:1 log

[date]: [trajectory, the spike, the blocker, the next rep]

90-day decision ([date])

[On track / extend / stop, with the concrete evidence]