npbuilds Meeting Mastery — The Visible Senior Skill
A meeting is a small organizational system: limited time, multiple stakeholders, a goal that may or may not get achieved. The senior person in the room is the one who notices when the system is failing and intervenes — who names the unaddressed disagreement, who time-boxes the digression, who closes the meeting with a decision rather than letting it drift to "let's discuss again next week." This skill is the visible part of executive presence; everyone in the room sees it happen.
Key Concepts
Meeting Types and Their Distinct Logic
| Type | Purpose | Right Length | Right Frame |
|---|---|---|---|
| Decision meeting | Make a specific decision | 30–60 min | What's the decision; who decides; what's the criteria |
| Information meeting | Share or gather information | 15–30 min (often should be a doc) | What's the info; who needs it; how is it landing |
| Brainstorming | Generate options | 60–90 min | What's the question; what are the constraints; how do we evaluate |
| Status update | Surface progress and risks | 15–30 min | What's done; what's at risk; what asks for the room |
| Strategy session | Align on direction | 90–180 min | What's the situation; what are the options; what's the path |
| 1:1 | Manage relationship + work | 30 min recurring | What's on your mind; what do you need from me |
The most-common meeting failure is type confusion — running a decision meeting as a brainstorm, or treating a strategy session as a status update.
The Agenda
A good agenda has three properties:
- Specific objective — "By the end of this meeting, we will have decided X" — not "discuss Y"
- Time-allocated — Each segment has a budget
- Pre-read identified — What people should have read before arriving; without this, the first 15 min are spent reading
Send the agenda 24+ hours in advance. People who come unprepared self-select.
Opening Moves (First 5 Minutes)
The first 5 minutes set the meeting's frame:
- State the objective. "We're here to decide X."
- Name the constraints. "We have 45 minutes; we need to land on a decision today."
- Confirm the room. "Did everyone read the pre-read? Any questions before we dive in?"
- Acknowledge the elephant if there is one. "I know we've been circling this for two weeks; today we're closing it out."
These moves take 5 minutes and pay back across the entire meeting.
Decision Protocols
When the meeting is a decision meeting, the senior move is to name the decision protocol:
| Protocol | Mechanism |
|---|---|
| Consensus | Everyone agrees; rare and slow |
| Consultative | One person decides after hearing others |
| Voting | Majority rules |
| Owner | One person owns the decision; meeting informs |
| CEO call | CEO decides; meeting surfaces options |
Naming the protocol up front prevents the disagreement at the end about whether the decision was actually made.
Derailment Recovery
Meetings derail in predictable ways. The senior moves to recover:
| Derailment | Recovery Move |
|---|---|
| Deep dive into a tangent | "Hold that for offline; let's come back to the main thread" |
| Two people in a side argument | "Let me table this for the two of you to resolve and report back" |
| One person dominating | "I want to hear from [other person] on this" |
| Stuck on a non-decision | "Let me reframe; what we're actually deciding is X" |
| Out of time | "We have 5 minutes left; let's lock the decision and follow-ups" |
The pattern: name what's happening, redirect, move on. Naming is the senior move; tolerating is the staff move.
Closing Moves (Last 5 Minutes)
A meeting that ends without explicit close drifts into the next meeting. Closing moves:
- Confirm the decision. "So we've decided X. Anyone disagree?"
- Confirm the owner. "Who owns the next step?"
- Confirm the timeline. "By when?"
- Confirm the next checkpoint. "When do we re-touch?"
Without these four, "follow-up confusion" is guaranteed.
The Follow-Up Note
Within 24 hours, a brief note (Slack or email) to the meeting attendees:
- Decisions made
- Owners and timelines
- Items tabled
- Next checkpoint
The follow-up note is the artifact that makes the meeting durable. It also signals senior-org-discipline to everyone who reads it.
Common Failure Modes
| Failure | Looks Like | Fix |
|---|---|---|
| No agenda | Meeting opens with "what should we discuss?" | Pre-distributed agenda 24h+ in advance |
| Type confusion | Decision meeting run as brainstorm | Name the type; run accordingly |
| No objective | Meeting opens with "let's chat about X" | State decision/output as objective |
| No close | Meeting ends; no decision recorded | Closing 4-step ritual |
| No follow-up | No note after the meeting | Within-24h follow-up |
| Tolerating derailment | Letting tangents play out | Name them; redirect |
Self-Coaching Track
For your situation (MD → biotech VC/operator):
Audit your meeting calendar. For your last 10 meetings, classify each by type. How many were the right type? How many had an agenda 24h in advance? How many ended with a follow-up note?
Build agenda templates per meeting type. Decision-meeting template, status-update template, 1:1 template. Reuse the structure; vary the content.
Practice the opening 5 minutes. This is muscle that gets better with reps. State objective, constraints, confirm pre-read, address elephant.
Name the decision protocol when running decision meetings. The 30 seconds spent naming the protocol pays back enormously in the meeting's quality.
Practice the derailment moves. Have responses ready: "hold that for offline," "let me hear from X," "let me reframe." When the moment arrives, you don't have time to invent them.
Calendar 5 minutes after each meeting for the follow-up note. Without the calendar block, the note doesn't get sent.
Per high-stakes meeting, do a 10-minute pre-mortem. "What's the most likely way this meeting fails? How do I prevent that?"
Teach / Mentor-Others Track
When coaching a junior or peer through meeting mastery:
Type-classification is the first lesson. Mentees often run meetings without naming the type. Walk through the table; have them classify their last 5 meetings.
The agenda discipline transfers fast. Coach the 24h-in-advance standard. Once it's a habit, meeting quality improves immediately.
The opening 5 minutes are trainable. Show one good opening; rehearse with the mentee. Mentees often skip these and lose 10 minutes per meeting.
Decision protocol naming is high-leverage. Mentees often skip this and end meetings with ambiguous outcomes. Coach the 30-second naming.
The derailment moves are language-trainable. Walk through the recovery moves; rehearse the language. Without rehearsal, mentees freeze when derailment happens.
The follow-up note is a non-negotiable habit. Mentees often skip; the meetings then drift. Insist on the 24h follow-up; show one good example.
When This Applies
- Designing or running a high-stakes meeting
- Auditing why your meetings feel low-leverage
- Recovering a meeting that's going off the rails
- Onboarding to a new role with a new meeting cadence
- Coaching a junior on their meeting craft
Cross-Domain Connections
- executive-presence/executive-communication — Agendas and follow-up notes are exec-comm artifacts
- executive-presence/board-readiness — Board meetings are a special meeting type with strict protocol
- interview-mastery/panel-and-case — Panel dynamics share rules with meeting dynamics
- binding-vow/bluf-shaper, audience-classifier — Meeting communications benefit from BLUF and audience tuning
- product/the-loom — Meeting decision tracking integrates with decision-journal