Gtm-Operating-Cadence

# Operating Cadence

The meeting structure that worked at 30 people collapses at 100. What worked at 100 collapses at 300. The failure mode is always the same: too many people in too many meetings making too few decisions.

When to Use

**Triggers:**

- "Our meetings don't produce decisions"

- "We're growing but alignment is getting worse"

- "How often should we meet?"

- "Nobody knows what's happening across functions"

- "Decisions take forever"

- "Leadership is in meetings all day"

**Context:**

- Companies scaling from 20 to 300+ people

- Post-PMF through growth stage

- Distributed / remote teams

- Any stage where "we need to talk about this" has become the default

---

Core Frameworks

1. The Five-Level Meeting Architecture

**The Pattern:**

Different meetings serve different purposes. Conflating them creates either inefficiency (too much time) or confusion (unclear decisions). Separate meetings by function, frequency, and decision authority.

**Level 1: Daily Standup (15 min, teams only)**

- What we finished yesterday, what we're starting today, what's blocking us

- 5-10 people max. Whole-company standups are theater

- Anti-pattern: Status reporting (use Slack, not meetings)

- Anti-pattern: Strategic discussion (wrong time, wrong place)

- Success criteria: Finishes in 15 minutes, surfaces 1-2 blockers

**Level 2: Weekly Functional Reviews (60 min, function leadership)**

Each function gets its own weekly rhythm:

- Product team Friday 4pm: metrics, user feedback, roadmap blockers

- GTM team Tuesday 4pm: pipeline, customer updates, deal health

- Engineering Wednesday 4pm: velocity, bug backlog, deployment

Format: Metric recap (10 min) → Wins/blockers (15 min) → One deep-dive (30 min) → Next week priorities (5 min)

Anti-pattern: Trying to solve every problem in the meeting. Pick 1-2, delegate the rest to follow-ups.

**Level 3: Weekly All-Hands (60 min, whole company)**

The single most important alignment mechanism at a scaling company.

- CEO update (15 min): north star progress, week focus, what's changed

- Metric dashboard (10 min): same format every week (consistency enables pattern recognition)

- Deep dive (20 min): one strategic topic needing team input — not a presentation, a discussion

- Q&A (15 min): real questions, real answers

Anti-pattern: Defensive tone. All-hands should be straightforward, not spin.

Anti-pattern: Inconsistent metrics. If you change the dashboard, the team can't track progress.

**Level 4: Bi-Weekly Leadership Alignment (90 min)**

- North star progress (5 min)

- Functional updates (30 min, 5-7 min each)

- Major decisions needing resolution (30-40 min): resource conflicts, strategic pivots, customer/product decisions

- Next 2 weeks planning (15 min)

This is where cross-functional blockers get resolved. If functions operate independently, this meeting isn't working.

**Level 5: Quarterly Strategic Planning (half-day to full-day)**

- Previous quarter retrospective (90 min): What worked, what didn't, what we'd do differently

- Next quarter planning (120 min): What are we optimizing for? What's the roadmap?

- Function breakouts (90 min): Each function plans their quarter

- Synthesis (60 min): Functions share commitments, resolve conflicts

Anti-pattern: Too much "fun activity," not enough substance.

Anti-pattern: No clear decisions coming out.

**Scaling Adjustments:**

- **<30 people**: Levels 2-3 only. Skip daily standups (you see everything). Skip bi-weekly leadership (you ARE leadership).

- **30-100 people**: Add all 5 levels. Monthly review catches what you no longer see daily.

- **100-300 people**: Add skip-level reviews. You're 2+ layers from execution.

- **300+ people**: Add function-specific sub-cadences. CEO should be in *fewer* meetings than at 50 — not more.

**The Rule That Makes This Work:**

Every meeting must produce decisions or be cancelled. Status updates are async. If you're in a meeting and nobody is making a decision, leave.

---

2. Weekly Metric Reporting