gtm-operating-cadence

Design meeting rhythms, metric dashboards, and quarterly planning processes for scaling companies.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill gtm-operating-cadence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gtm-operating-cadence
Source: https://github.com/github/awesome-copilot/tree/main/skills/gtm-operating-cadence
Command: npx skills add https://github.com/github/awesome-copilot --skill gtm-operating-cadence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

As companies scale from 20 to 300+ people, meetings multiply while decisions slow down, alignment degrades, and leadership time disappears into status updates. This Skill provides a structured operating cadence covering meeting architecture, metric reporting, quarterly planning, and decision authority so organizations keep making fast decisions as they grow.

Core Features & Use Cases

  • Five-Level Meeting Architecture: Defines daily standups, weekly functional reviews, weekly all-hands, bi-weekly leadership alignment, and quarterly planning with formats, durations, and anti-patterns for each.
  • Weekly Metric Reporting: Provides a repeatable dashboard format with 8-12 metrics, traffic-light status, trend arrows, and escalation rules for RED items.
  • Quarterly Planning Cycle: Lays out a 3-week process (retrospective, priority setting, OKR cascade) producing 3-5 priorities with owners and metrics.
  • Decision Authority Matrix: Distinguishes Type 1 (irreversible) from Type 2 (reversible) decisions and assigns clear decision rights and timelines.
  • Use Case: A 120-person startup where leadership spends all week in meetings but decisions stall. Use this Skill to redesign the meeting structure, install a weekly metric dashboard, and assign decision owners per decision type.

Quick Start

Use the gtm-operating-cadence skill to design a meeting and reporting structure for my 80-person company where decisions are slow and alignment is breaking down.

Frequently Asked Questions about gtm-operating-cadence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a meeting structure for a scaling company?

Use a five-level meeting architecture: daily standups (15 min), weekly functional reviews (60 min), weekly all-hands (60 min), bi-weekly leadership alignment (90 min), and quarterly planning. Companies under 30 people need only levels 2-3; larger organizations add all five plus skip-level reviews.

How many metrics should a weekly company dashboard include?

A weekly dashboard should include 8-12 metrics with the same format every week, trend arrows, and traffic-light colors. Every RED metric needs an owner, specific action, and deadline. If a metric does not change behavior when it moves, remove it.

What is the difference between Type 1 and Type 2 decisions?

Type 1 decisions are irreversible and high-stakes, such as pricing models or market entry, decided by CEO or leadership within 1-2 weeks. Type 2 decisions are reversible and low-stakes, decided by the function owner same day or next day.

When should a company run quarterly planning?

Run a 3-week quarterly planning cycle: week 1 for retrospectives and data gathering, week 2 for leadership priority setting limited to 3-5 priorities, and week 3 for OKR cascade and resource allocation. The output should fit on one page.

Why do meetings stop producing decisions as companies grow?

Meetings fail when status updates replace decisions, attendee lists grow too large, and no single decider is named. The fix is making updates async, keeping meetings decision-focused, and assigning explicit decision authority per decision type.

What are the limitations of consensus-based decision making?

Consensus culture slows decisions by treating reversible choices as high-stakes and requiring universal alignment. The alternative is naming a single decider per decision, deciding with 70% information, and informing stakeholders afterward.