# Meetings Don't Have to Suck > [!question] Lingering Questions > - What triage rule resolves the case Kurt raised — two people legitimately needing the entire meeting for one top-priority issue — without derailing the group agenda or starving the issue of needed time? > - What's the actual failure rate of "emotional security blanket" client check-in calls when replaced by proactive self-serve status tooling? > - Is there a reliable early-warning signal for "well poisoning" (a chronically negative team member) that's distinguishable from normal new-hire ramp-up friction? > [!tip] Article Ideas > - Reusable meeting-hygiene template for maintainer/roadmap syncs: fixed agenda, hard stop, ranked issues list, persistent to-do/accountability review — worth trialing on one recurring meeting. > [!link] Cross Reference > - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — agency-operations and meeting-design practice > [!quote] Vocabulary > - **EOS** — Entrepreneurial Operating System, a business-consultancy methodology with a prescribed meeting agenda (fixed slot, identical structure, hard stop, ranked issues, accountability list) > - **"well poisoning"** — the hosts' term for a single chronically negative team member measurably (if hard to quantify) damaging team morale over time ## Bib capsule Agency Action podcast episode with agency owners Kurt and Toby, discussing Toby's live rollout of an EOS-style meeting agenda across his team, followed by a "drop me in a new city with $200" hypothetical on rebuilding a freelance WordPress client base from zero. ## Author's thesis A written, repeatable meeting agenda with a triage mechanism for tangents, ranked issues, and explicit to-do ownership converts a meeting from "information exchange nobody asked for" into "action tied to a decision" — and the same discipline (protect what's important, don't just react to what feels urgent) underlies both good meeting design and effective freelance client acquisition. ## Key arguments (≤3) 1. **EOS meetings pair a fixed agenda with a hard stop.** Same time weekly, identical agenda every time, and the meeting always ends on time — directly targeting chronic overrun as the specific complaint driving meeting hatred. 2. **Team meetings catch status gaps 1:1s hide.** Toby's counter-example to a pure-1:1 management model: he got contradictory status reports on the same project from different team members in separate 1:1s — a failure a shared team meeting is structurally better at catching. 3. **Perceived urgency crowds out actual priority without triage.** Credits *Tyranny of the Urgent* for reframing this: businesses that succeed protect time for what's important rather than reactively serving whatever feels urgent. ## Claim atoms ### EOS meetings pair a fixed agenda with a hard stop > [!quote] ID:transcript_eosformat > "same time every week... same agenda every meeting and it always ends on time." Where/why: Toby describing the EOS meeting template rolled out at his agency. Chronic overrun is named as one of the specific reasons meetings are hated; a hard stop directly targets that complaint. ### Team meetings catch status gaps 1:1s hide > [!quote] ID:transcript_statusgaps > "I'm getting different answers from different people. Oh, it's going great... The next guy is like, no, it's going off the rails." Where/why: Toby's counter-example to Kurt's 1:1-heavy management model — the strongest concrete evidence in the episode against relying solely on individual check-ins for status visibility. ### Perceived urgency crowds out actual priority without triage > [!quote] ID:transcript_tyrannyurgent > "perceived emergencies push everything down but there's no... great triage system to say... let's think about where this emergency fits amongst our other priorities." Where/why: Toby connecting the meeting-agenda discussion to *Tyranny of the Urgent* and time-blocking — the conceptual bridge between meeting hygiene and broader prioritization discipline. ## Permanent candidates - **Meeting structure should match decision scope, not team size** — strong candidate; synthesizes the episode's two competing meeting philosophies into one testable sizing rule. Promoted below. ## Processing checklist - [ ] Look into EOS's Level 10 meeting template directly (primary source) to compare against the version Kurt and Toby describe — https://www.eosworldwide.com/ - [ ] Read *Tyranny of the Urgent* (Charles Hummel) as a short primer on urgent-vs-important triage - [x] Connect into the relevant MOC — [[3. Resources/MOCs/Product & Startup Instincts MOC]] ## Metadata - Source: [[3. Resources/Readwise/Articles/Meetings Don’t Have to Suck]] - NAR-related: No ## Links - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — meeting-design and small-agency operations practice