gtm-operating-cadence
A framework for scaling companies to design meeting rhythms, metric reporting, quarterly planning, and decision-making processes.
Is gtm-operating-cadence safe to install?
Safe to install: our audit of gtm-operating-cadence's source files found 0 shell commands, 0 external URLs, no file writes (none risk). Every command and URL listed appears verbatim in the skill's source. The skill provides documentation and frameworks for organizational management and does not execute code or perform network requests.
How we audit skills: our security review methodology.
Who is this skill for?
Scaling companies (20-300+ employees) experiencing slow decision-making, poor alignment, or inefficient meeting structures.
What can you do with it?
- Designing meeting architectures based on company size
- Implementing weekly metric reporting dashboards
- Executing quarterly planning cycles
- Establishing decision authority matrices
- Transitioning to async-first communication
- Structuring CEO weekly updates
How good is this skill?
Quality score: 5/10. The skill provides a comprehensive, structured, and actionable guide for organizational operating cadences with clear frameworks and anti-patterns.
What does the skill file contain?
# 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 / remot...
Frequently asked questions
How many meetings should a company have as it scales?
The framework suggests 2-3 levels for under 30 people, all 5 levels for 30-100 people, and adding skip-level reviews and sub-cadences for 100-300+ people.
What is the rule for determining if a meeting is necessary?
Every meeting must produce a decision. If a meeting does not produce a decision, it should be cancelled or moved to an asynchronous format.
How many metrics should be included in a weekly dashboard?
The framework recommends tracking 8-12 total metrics to ensure focus and actionable insights.
What is the recommended quarterly planning cycle?
A 3-week cycle: Week 1 for retrospectives and data gathering, Week 2 for leadership priority setting, and Week 3 for OKR cascading and resource allocation.
Related skills
lark-workflow-meeting-summary
219.7KUsers who need to summarize meeting minutes, generate weekly reports, or review meeting history within the Lark ecosystem
The lark-workflow-meeting-summary skill provides a structured workflow for agents to aggregate meeting minutes from Lark VC, generate summaries, and create or update reports in Lark Docs.
gws-workflow-email-to-task
17.9KUsers who manage tasks directly from their Gmail inbox via the command line
The gws-workflow-email-to-task skill converts a Gmail message into a Google Tasks entry using the gws CLI tool.
gws-workflow-meeting-prep
17.5KUsers who manage schedules and meeting preparation via the Google Workspace CLI
The gws-workflow-meeting-prep skill retrieves agenda, attendee, and document information for the next upcoming Google Calendar event.
recipe-save-email-attachments
16.9KUsers who manage email attachments and Google Drive storage using the Google Workspace CLI
This recipe automates the process of locating Gmail messages containing attachments and saving those files to a specified Google Drive folder.