02 Team onboarding No. 04 of 9 1 min read

Team Member Intake

Turn a PM's 1:1 notes with a contributing team member into a structured capture of commitments and needs, written to Notion, flagging conflicts against the Project Overview.

  1. 01 Intake
  2. 02 Team onboarding
  3. 03 Scheduling prep
  4. 04 Scheduling
  5. 05 Planning
  6. 06 Cadence

Source

pmo-team-member-intake.md Last updated Aug 17, 2026

When it triggers

Use this after a one-on-one with someone who’ll actually do the work on the project — as opposed to the sponsor — whether that’s a single team member or a couple of people from the same team interviewed together.

What it does

  • Works through the notes for eight things: what was briefed to them, their feedback or questions, any gaps versus the sponsor’s account, new risks or dependencies they surfaced, their confirmed contribution, their deliverables, what they need to do their part, and the workload impact of taking this on.
  • Weighs those eight differently depending on whether you already know this domain well or are new to it — unfamiliar domains get more space on contribution, deliverables, inputs, and workload.
  • Flags anything the notes don’t cover instead of guessing, and handles multiple people from one meeting by giving each person their own contribution/deliverables/inputs/workload section.
  • Writes the result as its own Notion page, and separately adds any genuine conflicts or unresolved questions directly onto the Project Overview page, so nobody has to open a second page to see them.

Inputs & outputs

  • You provide: notes or a transcript from the one-on-one, the Project Overview (recommended, so gaps against the sponsor’s account can actually be checked), and whether this is a domain you already know well.
  • You get: a Notion page titled “Team Intake — [Project] — [Person/Team]”, plus any conflicts or open questions flagged directly on the Project Overview.

Related skills