gtm-operating-cadence
Design meeting rhythms, metric reporting, quarterly planning, and decision-making velocity for scaling companies. Use when decisions are slow, planning is broken, the company is growing but alignment is worse, or leadership meetings consume all time without producing decisions.
Security Assessment
About gtm-operating-cadence
This skill is an operating-cadence playbook for scaling companies, addressing the failure mode where growth brings too many people into too many meetings that produce too few decisions. It provides structure for meeting rhythms, metric reporting, quarterly planning, and decision-making velocity so alignment improves rather than degrades as headcount rises. It is a conceptual management framework, not executable software.
At its center is a five-level meeting architecture — daily standups, weekly functional reviews, a weekly all-hands, bi-weekly leadership alignment, and quarterly strategic planning — each with a purpose, format, time box, and anti-patterns, plus scaling adjustments for organizations from under 30 to over 300 people, anchored by the rule that every meeting must produce decisions or be cancelled. A weekly metric-reporting framework prescribes a consistent dashboard format with north-star and functional metrics, one context sentence per metric, trend arrows, traffic-light colors, an escalation rule for repeated reds, and a discipline of tracking only 8–12 decision-driving metrics. A three-week quarterly planning cycle covers retrospective and data gathering, planning, and synthesis to prevent strategic drift.
The target users are founders, executives, chiefs of staff, and operations leaders at post-product-market-fit companies scaling from roughly 20 to 300-plus people, including distributed and remote teams. Use cases include fixing meetings that don't produce decisions, speeding up slow decision-making, restoring cross-functional alignment, and standing up disciplined metric reporting and quarterly planning.
FAQ
What problem does this skill solve?
The scaling failure mode where a growing company ends up with too many people in too many meetings making too few decisions, causing alignment and decision velocity to worsen.
What is the five-level meeting architecture?
Daily standups, weekly functional reviews, a weekly all-hands, bi-weekly leadership alignment, and quarterly strategic planning — each separated by function, frequency, and decision authority, with the rule that every meeting must produce decisions or be cancelled.
How does the metric reporting work?
A same-structure-every-week dashboard with a north-star metric plus functional metrics, one context sentence and a trend arrow per metric, traffic-light colors, and an escalation rule when an item stays red two weeks with the same action plan. Track 8–12 decision-driving metrics.
Does the cadence change with company size?
Yes. Under 30 people use only a couple of levels; 30–100 add all five; 100–300 add skip-level reviews; 300-plus add function-specific sub-cadences, with the CEO in fewer meetings than at 50.
Who is this for?
Founders, executives, chiefs of staff, and operations leaders at post-PMF companies scaling from about 20 to 300-plus people, including distributed and remote teams.
Install gtm-operating-cadence
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
github/awesome-copilot