run-one-on-one

name	run-one-on-one
description	Run a 1:1 that serves the engineer — agenda from them, growth thread, blockers surfaced — not your status update. Reach for this before defaulting to a status read.

Skill: Run a 1:1

A 1:1 spent reading status is a standup you double-booked (§3 #2).

Step 1 — Pull the agenda from them

Default the agenda to the engineer's topics; you bring growth + feedback, not a status checklist (§3 #2).

Step 2 — Cover the durable layers

Blockers (what's in your way?), growth (where do you want to go?), feedback (both directions), and trust — rotate, don't cram all four every time.

Step 3 — Capture dated, observable notes

Write what happened, when, and the impact — continuous notes beat recency bias at review time (§3 #4). Keep sensitive PII out (§2).

Step 4 — Protect the time

Cancelling is the most expensive cheap decision a manager makes; reschedule, don't skip (§3 #2).

Output

A 1:1 operating model + this session's notes (engineer-owned agenda, growth thread, dated observations), as a draft you own (§2). Traverse Tree 1 if an underperformance signal surfaced. Use ../../templates/one-on-one-agenda.md.