Meetings and One-on-Ones: The Full Playbook skill

Meetings and One-on-Ones: The Full Playbook

Table of Contents

• Two Species of Meetings
• The One-on-One
• Frequency by Task-Relevant Maturity
• The Subordinate's Agenda
• The Hold List
• Notes, "One More Thing", and Remote 1:1s
• The Staff Meeting
• The Operation Review
• Mission-Oriented Meetings
• Meeting-Cost Math and When to Kill a Meeting

Two Species of Meetings

Grove's claim is blunt: a meeting is the medium through which most managerial work — gathering and giving information, making decisions, nudging — is performed. You cannot oppose meetings any more than a carpenter can oppose hammers; you can only run good ones or bad ones.

• Process-oriented meetings run on a regular cadence with a known format: one-on-ones, staff meetings, operation reviews. Regularity is what makes them cheap — agendas are standing, expectations shared, setup cost near zero — and what makes them effective: problems get caught while they are small.
• Mission-oriented meetings are ad hoc and exist to produce one specific decision. They are expensive by nature (interrupt-driven, unprepared attendees, no standing format).

The design goal: process meetings carry the bulk of managerial work — on the order of a quarter of a manager's calendar — so that mission-oriented meetings become rare. Grove's malorganization test: if ad hoc mission-oriented meetings consume more than about 25% of a manager's time, the regular process is failing. And the corollary diagnostic: any "ad hoc" meeting that keeps recurring is a process meeting in denial — give it a cadence, a format, and a standing agenda, and its cost collapses.

The One-on-One

The 1:1 is a regular, scheduled meeting between a supervisor and one subordinate, and it is the subordinate's meeting: their agenda, their airtime, their problems. Its purposes: mutual teaching (the supervisor shares context and skills; the subordinate teaches the supervisor what is really going on below), exchange of information too awkward or early for any other forum, and the supervisor's single best source of organizational knowledge.

Grove's leverage math: ninety minutes of your time can enhance the quality of your subordinate's work for two weeks — eighty-plus working hours. There is no cheaper multiplier on the calendar, which is why "too busy for 1:1s" inverts the economics: the busier the period, the more the 1:1 pays.

Baseline mechanics:

• Length: an hour as the default. Anything shorter, Grove observed, makes the subordinate confine themselves to simple things; the hard topics need room to surface. 45 minutes is the floor for a working cadence; never 15.
• Setting: the subordinate's turf or neutral ground, not a summons to your office. Remote: cameras on, both in a shared doc.
• Scheduling: rolling and protected. Reschedule within the week when needed; cancellation is reserved for true emergencies, because each silent drop teaches the report their problems can wait.

Frequency by Task-Relevant Maturity

Set frequency per person by their task-relevant maturity on their current work — not by seniority, tenure, or how much you enjoy the conversation:

Situation	Frequency	Length
New to role, project, or domain (any seniority)	Weekly	60 min
Ramping: competent with support, task still changing	Every two weeks	45-60 min
Veteran on stable scope, strong indicators	Every three to four weeks	60 min
Anyone during a crisis, reorg, or major task change	Snap back to weekly	60 min

Re-rate at every task change. The principal engineer who just became a manager is low-TRM again; the weekly cadence returns even though they are your most senior person. When in doubt, err frequent — over-meeting costs an hour; under-meeting costs a surprise in month three.

The Subordinate's Agenda

The subordinate prepares and sends the agenda the day before. Preparing it is itself the point — it forces them to survey their own work, spot trouble early, and decide what matters. A copy-paste template:

1:1 — <name> / <manager>, <date>

1. Indicators since last time: what moved, what I think it means
2. Wins and what's finished
3. Problems and blockers — current, and ones I can smell coming
   ("anything that bothers me", half-formed worries explicitly welcome)
4. Plans: what I intend to do next, decisions I'm about to make
5. Hold-list items (accumulated small topics)
6. Career / growth / feedback item (at least monthly)
7. Manager's items (last, and they don't get to eat the hour)

Two supervisor rules. First, items 3 and 4 are where you earn your keep: the subordinate talks, you ask the second question — "what's underneath that?", "what would have to be true?", "what happens if it slips?" — until the real shape of the problem is on the table. Second, your own topics ride in seat 7. The fastest way to kill a 1:1 program is to convert it into a status extraction or a tasking session; reports stop bringing problems and start bringing performances.

The Hold List

Both parties keep a running list — paper, doc, or DM-to-self — of topics that are important but not urgent, batched for the next 1:1. Effects: interruptions drop on both sides (most "got a sec?" pings are hold-list items in disguise), small items actually get handled instead of evaporating, and the 1:1 always has a floor of concrete material. "Put it on the hold list" is the polite, complete answer to most non-urgent pings — and modeling it teaches the team to batch their interruptions of each other, too.

Notes, "One More Thing", and Remote 1:1s

The supervisor takes the notes, on the subordinate's agenda, during the meeting. Writing while they talk signals that what they said registered and will be acted on; the written trail forces follow-up on both sides. End by reading back the actions: who does what by when. Next meeting opens with that list.

"One more thing." When the agenda is exhausted and chairs start to push back, ask: "What else is on your mind?" — and wait through the pause. The genuinely important item — the resignation being considered, the conflict with a peer, the doubt about the project — surfaces disproportionately in the last five minutes, after trust has warmed and the formal agenda no longer protects it. Budget for this; ending a 1:1 ten minutes "early" without asking is leaving the most valuable item in the room.

Remote 1:1s. The agenda doc is open on both screens and notes are typed into it live — Grove's "both looking at the same paper", updated. Cameras on if at all possible; notifications off (a glance at Slack reads as "you don't matter" at distance). Because hallway leakage is zero remotely, the hold list and the "one more thing" question carry even more of the load — skip neither.

The Staff Meeting

The staff meeting is the supervisor plus all direct reports, weekly, 60-90 minutes. Its special value: it is where the manager watches and shapes how their reports interact with each other, and where issues touching two or more people get settled with everyone present.

The format Grove prescribed is controlled free discussion: more structured than a bull session, looser than a briefing. The manager's role is moderator — Socratic prodder — not lecturer. If the manager talks more than a quarter of the time, it has become a broadcast, which email does cheaper.

Copy-paste agenda:

Staff meeting — <team>, weekly, 60 min

1. (5)  Metrics minute: the team's 4-6 indicators on screen; anomalies flagged only
2. (10) Round: one minute each — top priority, top worry. No narration of the week
3. (35) Two or three debated topics, flagged in advance by anyone on the team:
        decisions touching 2+ people, cross-cutting risks, contested priorities.
        Owner states the question; manager moderates; end each with
        decision / owner / date, or an explicit "decide by <date> with <input>"
4. (5)  Announcements that genuinely can't be written down
5. (5)  Actions read back

Rules: anything that concerns only one person moves to that person's 1:1; status that can be written, is written; "open issues" without an owner do not survive the meeting. The debated-topics slot is the heart — it is where the manager teaches decision-making by moderating instead of pronouncing.

The Operation Review

The operation review is the periodic formal forum — monthly for a department, quarterly for an org — where line managers present their indicators and trends to people who do not see their work daily: adjacent teams, skip-level management, newer employees. It teaches, it cross-pollinates, and it motivates: work that will have an audience gets finished differently.

Four roles, each with a job:

• Organizing manager: owns logistics, picks presenters, enforces the clock, circulates pre-reads 48h ahead.
• Reviewing manager (the senior person): sets the tone, asks the questions juniors won't, sanity-checks trends — and never ambushes. Their most important behavior: visibly rewarding honest bad news.
• Presenters (2-4 line managers/leads): show trends and forecasts, not snapshots; show indicator pairs together; state misses before being asked; bring one problem and one ask.
• Audience: obligated to engage — questions are the mechanism. A silent audience converts the review into theater.

Copy-paste agenda (75 min):

Operation review — <org>, monthly

1. (5)  Reviewing manager: context; follow-ups from last review
2. (3 × 15) Presenters: indicator trends vs forecast (stagger charts),
        one problem being worked, one ask of the room
3. (15) Cross-area questions and discussion
4. (10) Reviewing manager: themes, decisions, actions with owners

Mission-Oriented Meetings

When an ad hoc meeting truly is needed, it exists to produce a decision, and it has a chairman — the person who called it — with non-delegable duties:

• Name, in the invite, the decision to be made and by when.
• Invite the necessary people only — for a decision discussion, six or seven is the ceiling; beyond that, people watch instead of deciding.
• Send the pre-read 24h ahead; open by restating the question, not by reading the deck.
• Close with the decision stated in one sentence, plus owner and date — or an explicit deferral naming what information will settle it and when.
• Send the one-paragraph summary the same day.

If the meeting could not state its decision in the invite, it was an information meeting wearing a costume — handle it in writing or fold it into a process meeting. And if you are scheduling substantially the same "ad hoc" meeting for the third time, stop: give it a cadence and a standing format, and it becomes cheap.

Meeting-Cost Math and When to Kill a Meeting

Grove's framing: a manager's time has a real dollar value, and calling a meeting is spending it — an unplanned meeting is an unplanned purchase order. Make the math explicit:

cost = attendees × duration (h) × loaded hourly rate

Ten people × one hour × $130 loaded ≈ $1,300 — roughly a new laptop per occurrence, $67k per year if weekly. The test for any standing meeting: would you sign a purchase order for this amount, for what this meeting produced last month?

Kill, shrink, or convert when:

Signal	Action
No decision, surfaced problem, or changed plan in the last 3 occurrences	Kill it; replace with a written update
Half the room never speaks	Shrink the list; minutes to the rest
Same two people do all the talking	Make it their 1:1 or a working session
Purely one-way status	Convert to a dashboard or memo; reclaim the hour
"We've always had it" is the only defense	Cancel for a month; reinstate only what is actually missed

Run a quarterly meeting audit: list every standing meeting you own, compute each one's annual cost, and re-justify it against what it produces. Default for borderline cases is cancellation — a genuinely needed meeting announces itself by the problems that appear in its absence, and it can always be reinstated leaner.