[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F4QQ6YK2B96M16FSTMVMW2":3,"skill-same:01M6F4QQ6YK2B96M16FSTMVMW2":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6F4QQ6YK2B96M16FSTMVMW2","gtm-operating-cadence",null,"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.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fgithub\u002Fawesome-copilot\u002Fgtm-operating-cadence\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"cadence","operating","gtm","gtm operating cadence","alignment","scaling","leadership","decision-making","time","velocity","but","design","use","broken","technical","linkedin","decision","reporting","product","planning","2026-11-10 10:12:30",false,"---\nname: gtm-operating-cadence\ndescription: 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.\nlicense: MIT\nmetadata:\n  author: Smit Patel (https:\u002F\u002Flinkedin.com\u002Fin\u002Fsmitkpatel)\n  source: https:\u002F\u002Fgithub.com\u002Fbeingsmit\u002Ftechnical-product-gtm\n---\n\n# Operating Cadence\n\nThe 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.\n\n## When to Use\n\n**Triggers:**\n- \"Our meetings don't produce decisions\"\n- \"We're growing but alignment is getting worse\"\n- \"How often should we meet?\"\n- \"Nobody knows what's happening across functions\"\n- \"Decisions take forever\"\n- \"Leadership is in meetings all day\"\n\n**Context:**\n- Companies scaling from 20 to 300+ people\n- Post-PMF through growth stage\n- Distributed \u002F remote teams\n- Any stage where \"we need to talk about this\" has become the default\n\n---\n\n## Core Frameworks\n\n### 1. The Five-Level Meeting Architecture\n\n**The Pattern:**\n\nDifferent meetings serve different purposes. Conflating them creates either inefficiency (too much time) or confusion (unclear decisions). Separate meetings by function, frequency, and decision authority.\n\n**Level 1: Daily Standup (15 min, teams only)**\n\n- What we finished yesterday, what we're starting today, what's blocking us\n- 5-10 people max. Whole-company standups are theater\n- Anti-pattern: Status reporting (use Slack, not meetings)\n- Anti-pattern: Strategic discussion (wrong time, wrong place)\n- Success criteria: Finishes in 15 minutes, surfaces 1-2 blockers\n\n**Level 2: Weekly Functional Reviews (60 min, function leadership)**\n\nEach function gets its own weekly rhythm:\n- Product team Friday 4pm: metrics, user feedback, roadmap blockers\n- GTM team Tuesday 4pm: pipeline, customer updates, deal health\n- Engineering Wednesday 4pm: velocity, bug backlog, deployment\n\nFormat: Metric recap (10 min) → Wins\u002Fblockers (15 min) → One deep-dive (30 min) → Next week priorities (5 min)\n\nAnti-pattern: Trying to solve every problem in the meeting. Pick 1-2, delegate the rest to follow-ups.\n\n**Level 3: Weekly All-Hands (60 min, whole company)**\n\nThe single most important alignment mechanism at a scaling company.\n\n- CEO update (15 min): north star progress, week focus, what's changed\n- Metric dashboard (10 min): same format every week (consistency enables pattern recognition)\n- Deep dive (20 min): one strategic topic needing team input — not a presentation, a discussion\n- Q&A (15 min): real questions, real answers\n\nAnti-pattern: Defensive tone. All-hands should be straightforward, not spin.\nAnti-pattern: Inconsistent metrics. If you change the dashboard, the team can't track progress.\n\n**Level 4: Bi-Weekly Leadership Alignment (90 min)**\n\n- North star progress (5 min)\n- Functional updates (30 min, 5-7 min each)\n- Major decisions needing resolution (30-40 min): resource conflicts, strategic pivots, customer\u002Fproduct decisions\n- Next 2 weeks planning (15 min)\n\nThis is where cross-functional blockers get resolved. If functions operate independently, this meeting isn't working.\n\n**Level 5: Quarterly Strategic Planning (half-day to full-day)**\n\n- Previous quarter retrospective (90 min): What worked, what didn't, what we'd do differently\n- Next quarter planning (120 min): What are we optimizing for? What's the roadmap?\n- Function breakouts (90 min): Each function plans their quarter\n- Synthesis (60 min): Functions share commitments, resolve conflicts\n\nAnti-pattern: Too much \"fun activity,\" not enough substance.\nAnti-pattern: No clear decisions coming out.\n\n**Scaling Adjustments:**\n\n- **\u003C30 people**: Levels 2-3 only. Skip daily standups (you see everything). Skip bi-weekly leadership (you ARE leadership).\n- **30-100 people**: Add all 5 levels. Monthly review catches what you no longer see daily.\n- **100-300 people**: Add skip-level reviews. You're 2+ layers from execution.\n- **300+ people**: Add function-specific sub-cadences. CEO should be in *fewer* meetings than at 50 — not more.\n\n**The Rule That Makes This Work:**\n\nEvery meeting must produce decisions or be cancelled. Status updates are async. If you're in a meeting and nobody is making a decision, leave.\n\n---\n\n### 2. Weekly Metric Reporting (The Dashboard That Catches Problems Early)\n\n**The Pattern:**\n\nMonthly reporting catches problems 30 days late. By then, a bad month is baked. Weekly reporting catches problems in week 2, when you can still save the month.\n\n**The Format (Same Structure Every Week):**\n\n```\nWEEK OF [DATE]\n\nNorth Star: [Metric]\nThis Week: [Value] | Last Week: [Value] | Change: [+\u002F-] [↑↓]\nContext: [One sentence — why this trend matters]\n\nFunctional Metrics:\n  Product:  7-Day Retention: 34% | Last: 33% | +1% ↑\n            Feature Adoption: 18% | Last: 16% | +2% ↑\n            Context: Onboarding improvements showing impact\n\n  GTM:      Pipeline: $8.2M | Last: $7.8M | +$400K ↑\n            New POCs: 3 | Last: 2\n            Context: Partner pipeline adding deals\n\n  Health:   Team Morale: 7.2\u002F10 (down from 7.5)\n            Context: Org restructure causing uncertainty\n```\n\n**The Discipline Rules:**\n\n1. **Same metrics every week.** Consistency enables pattern recognition. OK to add metrics, never drop them.\n2. **One context sentence per metric.** Not just the number — why does this matter? Vs plan? Vs last period?\n3. **Trend direction for every metric.** Up\u002Fdown\u002Fflat arrow. If it moved significantly: temporary or structural?\n4. **Traffic light colors.** GREEN (on track), YELLOW (watch), RED (action needed). Every RED item must have: owner, specific action, deadline.\n\n**The Escalation Rule:**\n\nIf a metric is RED two weeks in a row with the same action plan, escalate — the action plan isn't working.\n\n**How Many Metrics:**\n\nPick 8-12 total. If a metric doesn't change your behavior when it moves, remove it. Dashboards with 40 metrics are decoration, not decision tools.\n\n**Common Mistake:**\n\nVanity metrics that look good but don't predict business outcomes. Total downloads without adoption context. CEO headlines without supporting metrics.\n\n---\n\n### 3. Quarterly Planning (The Process That Prevents Strategic Drift)\n\n**The Pattern:**\n\nWithout quarterly planning, companies drift. Each function optimizes locally. Sales chases deals outside ICP. Product builds features for one customer. Marketing runs campaigns that don't connect to pipeline.\n\n**The 3-Week Planning Cycle:**\n\n**Week 1: Retrospective + Data Gathering**\n- Previous quarter results vs plan (leadership prepares)\n- Each function writes 1-page retrospective: what worked, what didn't, what we'd do differently\n- Finance prepares: revenue actuals, spend actuals, forecast\n- Market data: competitive moves, customer feedback themes, win\u002Floss analysis\n\n**Week 2: Priority Setting (Leadership Half-Day)**\n- Review retrospectives (30 min — pre-read, don't present)\n- Agree on 3-5 company-level priorities\n- For each: owner, success metric, resource requirements\n- Identify what you're *not* doing (as important as what you are)\n- Resolve cross-functional dependencies\n- Use the north star as tiebreaker: \"Does this help us hit the goal? Prioritize. Nice-to-have? Defer.\"\n\n**Week 3: OKR Cascade + Resource Allocation**\n- Each function translates company priorities into team OKRs\n- Leadership reviews for alignment\n- Resource allocation finalized (headcount, budget, tools)\n- Final plan shared company-wide\n\n**The Quarterly Commitment Format:**\n\n```\nQ2 2026 Roadmap\nNorth Star: [What we're optimizing for]\n\nPillar 1: Product (25% team effort)\n  Initiative: [Name]\n    Problem: [What we're solving]\n    Success: [Specific metric]\n    Owner: [Name]\n    Timeline: [When]\n\nPillar 2: GTM (50% team effort)\n  Initiative: [Name]\n    ...\n\nPillar 3: People (10% effort)\n  Initiative: [Name]\n    ...\n\nPillar 4: Tech Debt (15% effort)\n  Initiative: [Name]\n    ...\n```\n\n**The \"Not Doing\" List:**\n\nFor every priority you add, identify one thing you're stopping. If you can't name what you're *not* doing, you have too many priorities.\n\n**Common Mistake:**\n\nQuarterly planning that produces a 30-page doc nobody reads. The output should be: 3-5 priorities on one page, each with owner and metric. That's it.\n\n---\n\n### 4. Decision Velocity and Authority\n\n**The Pattern:**\n\nAt 20 people, the CEO makes every decision in real-time. Fast. At 100 people, decisions require alignment. Slow. At 300, decisions require alignment, approval, and documentation. Glacial.\n\n**The fix isn't more meetings. It's clear decision rights.**\n\n**Decision Authority Matrix:**\n\n| Decision | Who Decides | Timeline | Escalation |\n|----------|------------|----------|------------|\n| Company strategy | CEO | 1 week | Board if strategic |\n| Feature priority | Product lead | 1 week | CEO if >3 eng weeks |\n| Customer support issue | CSM | Immediately | CS lead if escalated |\n| Marketing campaign | Marketing lead | 2 weeks | CMO if >$10K budget |\n| Hiring | Function leader | 2 weeks | CEO if role not approved |\n| New partnership | CEO | 2 weeks | Board if strategic |\n| Vendor selection | Function leader | 1 week | CEO if >$50K\u002Fyear |\n\n**The Problem:**\n\nScaling companies start treating reversible, low-stakes decisions like irreversible, high-stakes ones. Everything needs approval. Everything needs a meeting. Everything needs consensus.\n\n**The Fix:**\n\n**Type 1 (Irreversible, high-stakes):** Pricing model, market entry, major partnership → CEO\u002Fleadership decides with debate in one meeting. Timeline: 1-2 weeks max.\n\n**Type 2 (Reversible, low-stakes):** Campaign creative, feature prioritization, single hire → Function owner decides, informs, iterates. Timeline: same day or next day.\n\n**Make decisions with 70% information, not 100%.** Speed is a competitive advantage at every stage.\n\n**Common Mistake:**\n\nConsensus culture masquerading as collaboration. \"Let's get everyone aligned\" often means \"nobody wants to decide.\" Name the decider. Let them decide. Move on.\n\n---\n\n### 5. Async-First Communication\n\n**The Pattern:**\n\nSynchronous meetings don't scale. Default to async, escalate to sync.\n\n**Async First (No Meeting Needed):**\n- Decision documents (even major ones — write up proposal, solicit comments, 48-72 hours for feedback, decide if consensus or no material objections)\n- Progress updates (use weekly reporting, not meetings)\n- Process changes and SOPs\n- Decisions already made (inform, don't discuss)\n\n**Sync When:**\n- Real-time brainstorming needed\n- Major disagreement to work through\n- Complex topic needing whiteboard\n- Team building \u002F relationship\n\n**Documentation Discipline:**\n\nEvery decision documented: What was decided? Why? Who decided? When does it take effect? Who needs to know?\n\nStore in searchable format (wiki, shared drive). New hires onboard faster. Past decisions don't get relitigated.\n\n**Common Mistake:**\n\n\"Quick sync\" meetings that grow to consume 10 hours per week. Over-communicating in Slack (ephemeral, noisy) and under-communicating in persistent formats (docs, emails). The important stuff should be searchable 6 months later.\n\n---\n\n### 6. The CEO Weekly Update\n\n**The Pattern:**\n\nThe single highest-leverage communication tool at a scaling company. 5-10 minutes to write. Everyone reads it. It sets context, celebrates wins, names priorities, and creates shared understanding.\n\n**Format (Sent Sunday Night or Monday Morning):**\n\n**1. Week Focus (1 paragraph):**\nWhat's the priority this week? What should the team be focused on?\n\n**2. North Star Progress (1-2 bullets):**\nWhere are we on the key metric? Trend up\u002Fdown\u002Fflat? Why does this matter?\n\n**3. Wins This Week (3-5 bullets):**\nWhat shipped? Customer\u002Fpartner wins? Big picture implication?\n\n**4. Blockers Getting Resolved (1-2 bullets):**\nWhat are we unblocking this week? Who needs to know?\n\n**5. Ask (1 bullet, optional):**\nWhat help does the team need? Referrals, feedback, customer introductions?\n\n**The Rule:**\n\nSame day every week. Consistency signals operational discipline. If you skip a week, the team notices — and starts wondering what you're not telling them.\n\n**Common Mistake:**\n\nToo long (team doesn't read), too detailed (save that for function meetings), only good news (team loses trust), inconsistent (team stops reading).\n\n---\n\n### 7. Role Clarity > Titles\n\n**The Pattern:**\n\nThe most powerful tool for speed isn't hierarchy — it's explicit role clarity. When someone knows exactly what they own and can't delegate it away, decisions happen faster.\n\n**How to Execute:**\n\n- Every initiative gets exactly one owner (with supporting teammates)\n- Metrics are tied to that owner\n- Success is measured by moving KPIs, not completing tasks\n- Eliminate initiatives without clear ownership within 48 hours\n\n**The Test:**\n\nCan you name the single person who owns this outcome? Not \"the team\" — a person. If you can't, the initiative will drift.\n\n**Common Mistake:**\n\nAssigning projects to multiple people (\"everyone owns it\" = nobody owns it). Measuring activity instead of impact. Burn rate going up without clear ROI tracking per initiative.\n\n---\n\n## Decision Trees\n\n### Which Meeting Levels Do We Need?\n\n```\nCompany size \u003C30?\n├─ Yes → Levels 2-3 only (weekly functional + all-hands)\n└─ No → Continue...\n    │\n    30-100 people?\n    ├─ Yes → All 5 levels\n    └─ No → All 5 + skip-level reviews + function sub-cadences\n```\n\n### Is This Meeting Worth Keeping?\n\n```\nDoes it produce decisions?\n├─ No → Can it be async?\n│   ├─ Yes → Make it async, cancel the meeting\n│   └─ No → Redesign with decision agenda\n└─ Yes → Are the right people in the room?\n    ├─ No → Fix attendee list (fewer > more)\n    └─ Yes → Keep it\n```\n\n---\n\n## Common Mistakes\n\n**1. Adding meetings as you grow**\nReplace them. At 200 people, the CEO should be in fewer meetings than at 50.\n\n**2. Status update meetings**\nIf it can be an email, it should be an email. Meetings are for decisions.\n\n**3. Changing metrics every quarter**\nConsistency enables trend identification. Same dashboard, every time.\n\n**4. Consensus culture**\nName the decider. Let them decide. Inform everyone else.\n\n**5. All information in Slack**\nEphemeral, noisy, unsearchable. Important decisions go in docs.\n\n**6. Quarterly planning that produces 30-page docs**\n3-5 priorities on one page. That's the output.\n\n---\n\n## Quick Reference\n\n**Meeting architecture:**\nDaily standup (15 min) → Weekly functional (60 min) → Weekly all-hands (60 min) → Bi-weekly leadership (90 min) → Quarterly planning (half-day)\n\n**Weekly metric dashboard:**\n8-12 metrics, same format every week, traffic light colors, one context sentence per metric, owner + action + deadline for every RED\n\n**Quarterly planning cycle:**\nWeek 1: Retro + data → Week 2: Priority setting (3-5 max) → Week 3: OKR cascade + resources\n\n**Decision authority:**\nType 1 (irreversible): CEO\u002Fleadership, 1-2 weeks → Type 2 (reversible): Function owner, same day\n\n**CEO weekly update:**\nWeek focus → North star progress → Wins → Blockers → Ask\n\n**Information flow:**\nDaily: Slack wins\u002Fcustomer-voice → Weekly: CEO email + function updates → Monthly: All-hands + skip-levels → Quarterly: Planning share + demos\n\n---\n\n## Related Skills\n\n- **enterprise-account-planning**: Stakeholder management and deal cadence patterns\n- **0-to-1-launch**: Launch-specific execution cadence\n- **board-and-investor-communication**: Board meeting structure and investor updates\n\n---\n\n*Based on operating cadence design across companies scaling from 20 to 1,000+ employees, including the five-level meeting architecture that survived 3x headcount growth, the weekly reporting format that caught pipeline problems 3 weeks earlier than monthly reviews, and the CEO weekly update format refined across multiple companies. Not theory — patterns from building operating systems through hypergrowth and teaching them to the next team.*\n\n","# Operating Cadence\n\nThe 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.\n\n## When to Use\n\n**Triggers:**\n- \"Our meetings don't produce decisions\"\n- \"We're growing but alignment is getting worse\"\n- \"How often should we meet?\"\n- \"Nobody knows what's happening across functions\"\n- \"Decisions take forever\"\n- \"Leadership is in meetings all day\"\n\n**Context:**\n- Companies scaling from 20 to 300+ people\n- Post-PMF through growth stage\n- Distributed \u002F remote teams\n- Any stage where \"we need to talk about this\" has become the default\n\n---\n\n## Core Frameworks\n\n### 1. The Five-Level Meeting Architecture\n\n**The Pattern:**\n\nDifferent meetings serve different purposes. Conflating them creates either inefficiency (too much time) or confusion (unclear decisions). Separate meetings by function, frequency, and decision authority.\n\n**Level 1: Daily Standup (15 min, teams only)**\n\n- What we finished yesterday, what we're starting today, what's blocking us\n- 5-10 people max. Whole-company standups are theater\n- Anti-pattern: Status reporting (use Slack, not meetings)\n- Anti-pattern: Strategic discussion (wrong time, wrong place)\n- Success criteria: Finishes in 15 minutes, surfaces 1-2 blockers\n\n**Level 2: Weekly Functional Reviews (60 min, function leadership)**\n\nEach function gets its own weekly rhythm:\n- Product team Friday 4pm: metrics, user feedback, roadmap blockers\n- GTM team Tuesday 4pm: pipeline, customer updates, deal health\n- Engineering Wednesday 4pm: velocity, bug backlog, deployment\n\nFormat: Metric recap (10 min) → Wins\u002Fblockers (15 min) → One deep-dive (30 min) → Next week priorities (5 min)\n\nAnti-pattern: Trying to solve every problem in the meeting. Pick 1-2, delegate the rest to follow-ups.\n\n**Level 3: Weekly All-Hands (60 min, whole company)**\n\nThe single most important alignment mechanism at a scaling company.\n\n- CEO update (15 min): north star progress, week focus, what's changed\n- Metric dashboard (10 min): same format every week (consistency enables pattern recognition)\n- Deep dive (20 min): one strategic topic needing team input — not a presentation, a discussion\n- Q&A (15 min): real questions, real answers\n\nAnti-pattern: Defensive tone. All-hands should be straightforward, not spin.\nAnti-pattern: Inconsistent metrics. If you change the dashboard, the team can't track progress.\n\n**Level 4: Bi-Weekly Leadership Alignment (90 min)**\n\n- North star progress (5 min)\n- Functional updates (30 min, 5-7 min each)\n- Major decisions needing resolution (30-40 min): resource conflicts, strategic pivots, customer\u002Fproduct decisions\n- Next 2 weeks planning (15 min)\n\nThis is where cross-functional blockers get resolved. If functions operate independently, this meeting isn't working.\n\n**Level 5: Quarterly Strategic Planning (half-day to full-day)**\n\n- Previous quarter retrospective (90 min): What worked, what didn't, what we'd do differently\n- Next quarter planning (120 min): What are we optimizing for? What's the roadmap?\n- Function breakouts (90 min): Each function plans their quarter\n- Synthesis (60 min): Functions share commitments, resolve conflicts\n\nAnti-pattern: Too much \"fun activity,\" not enough substance.\nAnti-pattern: No clear decisions coming out.\n\n**Scaling Adjustments:**\n\n- **\u003C30 people**: Levels 2-3 only. Skip daily standups (you see everything). Skip bi-weekly leadership (you ARE leadership).\n- **30-100 people**: Add all 5 levels. Monthly review catches what you no longer see daily.\n- **100-300 people**: Add skip-level reviews. You're 2+ layers from execution.\n- **300+ people**: Add function-specific sub-cadences. CEO should be in *fewer* meetings than at 50 — not more.\n\n**The Rule That Makes This Work:**\n\nEvery meeting must produce decisions or be cancelled. Status updates are async. If you're in a meeting and nobody is making a decision, leave.\n\n---\n\n### 2. Weekly Metric Reporting (The Dashboard That Catches Problems Early)\n\n**The Pattern:**\n\nMonthly reporting catches problems 30 days late. By then, a bad month is baked. Weekly reporting catches problems in week 2, when you can still save the month.\n\n**The Format (Same Structure Every Week):**\n\n```\nWEEK OF [DATE]\n\nNorth Star: [Metric]\nThis Week: [Value] | Last Week: [Value] | Change: [+\u002F-] [↑↓]\nContext: [One sentence — why this trend matters]\n\nFunctional Metrics:\n  Product:  7-Day Retention: 34% | Last: 33% | +1% ↑\n            Feature Adoption: 18% | Last: 16% | +2% ↑\n            Context: Onboarding improvements showing impact\n\n  GTM:      Pipeline: $8.2M | Last: $7.8M | +$400K ↑\n            New POCs: 3 | Last: 2\n            Context: Partner pipeline adding deals\n\n  Health:   Team Morale: 7.2\u002F10 (down from 7.5)\n            Context: Org restructure causing uncertainty\n```\n\n**The Discipline Rules:**\n\n1. **Same metrics every week.** Consistency enables pattern recognition. OK to add metrics, never drop them.\n2. **One context sentence per metric.** Not just the number — why does this matter? Vs plan? Vs last period?\n3. **Trend direction for every metric.** Up\u002Fdown\u002Fflat arrow. If it moved significantly: temporary or structural?\n4. **Traffic light colors.** GREEN (on track), YELLOW (watch), RED (action needed). Every RED item must have: owner, specific action, deadline.\n\n**The Escalation Rule:**\n\nIf a metric is RED two weeks in a row with the same action plan, escalate — the action plan isn't working.\n\n**How Many Metrics:**\n\nPick 8-12 total. If a metric doesn't change your behavior when it moves, remove it. Dashboards with 40 metrics are decoration, not decision tools.\n\n**Common Mistake:**\n\nVanity metrics that look good but don't predict business outcomes. Total downloads without adoption context. CEO headlines without supporting metrics.\n\n---\n\n### 3. Quarterly Planning (The Process That Prevents Strategic Drift)\n\n**The Pattern:**\n\nWithout quarterly planning, companies drift. Each function optimizes locally. Sales chases deals outside ICP. Product builds features for one customer. Marketing runs campaigns that don't connect to pipeline.\n\n**The 3-Week Planning Cycle:**\n\n**Week 1: Retrospective + Data Gathering**\n- Previous quarter results vs plan (leadership prepares)\n- Each function writes 1-page retrospective: what worked, what didn't, what we'd do differently\n- Finance prepares: revenue actuals, spend actuals, forecast\n- Market data: competitive moves, customer feedback themes, win\u002Floss analysis\n\n**Week 2: Priority Setting (Leadership Half-Day)**\n- Review retrospectives (30 min — pre-read, don't present)\n- Agree on 3-5 company-level priorities\n- For each: owner, success metric, resource requirements\n- Identify what you're *not* doing (as important as what you are)\n- Resolve cross-functional dependencies\n- Use the north star as tiebreaker: \"Does this help us hit the goal? Prioritize. Nice-to-have? Defer.\"\n\n**Week 3: OKR Cascade + Resource Allocation**\n- Each function translates company priorities into team OKRs\n- Leadership reviews for alignment\n- Resource allocation finalized (headcount, budget, tools)\n- Final plan shared company-wide\n\n**The Quarterly Commitment Format:**\n\n```\nQ2 2026 Roadmap\nNorth Star: [What we're optimizing for]\n\nPillar 1: Product (25% team effort)\n  Initiative: [Name]\n    Problem: [What we're solving]\n    Success: [Specific metric]\n    Owner: [Name]\n    Timeline: [When]\n\nPillar 2: GTM (50% team effort)\n  Initiative: [Name]\n    ...\n\nPillar 3: People (10% effort)\n  Initiative: [Name]\n    ...\n\nPillar 4: Tech Debt (15% effort)\n  Initiative: [Name]\n    ...\n```\n\n**The \"Not Doing\" List:**\n\nFor every priority you add, identify one thing you're stopping. If you can't name what you're *not* doing, you have too many priorities.\n\n**Common Mistake:**\n\nQuarterly planning that produces a 30-page doc nobody reads. The output should be: 3-5 priorities on one page, each with owner and metric. That's it.\n\n---\n\n### 4. Decision Velocity and Authority\n\n**The Pattern:**\n\nAt 20 people, the CEO makes every decision in real-time. Fast. At 100 people, decisions require alignment. Slow. At 300, decisions require alignment, approval, and documentation. Glacial.\n\n**The fix isn't more meetings. It's clear decision rights.**\n\n**Decision Authority Matrix:**\n\n| Decision | Who Decides | Timeline | Escalation |\n|----------|------------|----------|------------|\n| Company strategy | CEO | 1 week | Board if strategic |\n| Feature priority | Product lead | 1 week | CEO if >3 eng weeks |\n| Customer support issue | CSM | Immediately | CS lead if escalated |\n| Marketing campaign | Marketing lead | 2 weeks | CMO if >$10K budget |\n| Hiring | Function leader | 2 weeks | CEO if role not approved |\n| New partnership | CEO | 2 weeks | Board if strategic |\n| Vendor selection | Function leader | 1 week | CEO if >$50K\u002Fyear |\n\n**The Problem:**\n\nScaling companies start treating reversible, low-stakes decisions like irreversible, high-stakes ones. Everything needs approval. Everything needs a meeting. Everything needs consensus.\n\n**The Fix:**\n\n**Type 1 (Irreversible, high-stakes):** Pricing model, market entry, major partnership → CEO\u002Fleadership decides with debate in one meeting. Timeline: 1-2 weeks max.\n\n**Type 2 (Reversible, low-stakes):** Campaign creative, feature prioritization, single hire → Function owner decides, informs, iterates. Timeline: same day or next day.\n\n**Make decisions with 70% information, not 100%.** Speed is a competitive advantage at every stage.\n\n**Common Mistake:**\n\nConsensus culture masquerading as collaboration. \"Let's get everyone aligned\" often means \"nobody wants to decide.\" Name the decider. Let them decide. Move on.\n\n---\n\n### 5. Async-First Communication\n\n**The Pattern:**\n\nSynchronous meetings don't scale. Default to async, escalate to sync.\n\n**Async First (No Meeting Needed):**\n- Decision documents (even major ones — write up proposal, solicit comments, 48-72 hours for feedback, decide if consensus or no material objections)\n- Progress updates (use weekly reporting, not meetings)\n- Process changes and SOPs\n- Decisions already made (inform, don't discuss)\n\n**Sync When:**\n- Real-time brainstorming needed\n- Major disagreement to work through\n- Complex topic needing whiteboard\n- Team building \u002F relationship\n\n**Documentation Discipline:**\n\nEvery decision documented: What was decided? Why? Who decided? When does it take effect? Who needs to know?\n\nStore in searchable format (wiki, shared drive). New hires onboard faster. Past decisions don't get relitigated.\n\n**Common Mistake:**\n\n\"Quick sync\" meetings that grow to consume 10 hours per week. Over-communicating in Slack (ephemeral, noisy) and under-communicating in persistent formats (docs, emails). The important stuff should be searchable 6 months later.\n\n---\n\n### 6. The CEO Weekly Update\n\n**The Pattern:**\n\nThe single highest-leverage communication tool at a scaling company. 5-10 minutes to write. Everyone reads it. It sets context, celebrates wins, names priorities, and creates shared understanding.\n\n**Format (Sent Sunday Night or Monday Morning):**\n\n**1. Week Focus (1 paragraph):**\nWhat's the priority this week? What should the team be focused on?\n\n**2. North Star Progress (1-2 bullets):**\nWhere are we on the key metric? Trend up\u002Fdown\u002Fflat? Why does this matter?\n\n**3. Wins This Week (3-5 bullets):**\nWhat shipped? Customer\u002Fpartner wins? Big picture implication?\n\n**4. Blockers Getting Resolved (1-2 bullets):**\nWhat are we unblocking this week? Who needs to know?\n\n**5. Ask (1 bullet, optional):**\nWhat help does the team need? Referrals, feedback, customer introductions?\n\n**The Rule:**\n\nSame day every week. Consistency signals operational discipline. If you skip a week, the team notices — and starts wondering what you're not telling them.\n\n**Common Mistake:**\n\nToo long (team doesn't read), too detailed (save that for function meetings), only good news (team loses trust), inconsistent (team stops reading).\n\n---\n\n### 7. Role Clarity > Titles\n\n**The Pattern:**\n\nThe most powerful tool for speed isn't hierarchy — it's explicit role clarity. When someone knows exactly what they own and can't delegate it away, decisions happen faster.\n\n**How to Execute:**\n\n- Every initiative gets exactly one owner (with supporting teammates)\n- Metrics are tied to that owner\n- Success is measured by moving KPIs, not completing tasks\n- Eliminate initiatives without clear ownership within 48 hours\n\n**The Test:**\n\nCan you name the single person who owns this outcome? Not \"the team\" — a person. If you can't, the initiative will drift.\n\n**Common Mistake:**\n\nAssigning projects to multiple people (\"everyone owns it\" = nobody owns it). Measuring activity instead of impact. Burn rate going up without clear ROI tracking per initiative.\n\n---\n\n## Decision Trees\n\n### Which Meeting Levels Do We Need?\n\n```\nCompany size \u003C30?\n├─ Yes → Levels 2-3 only (weekly functional + all-hands)\n└─ No → Continue...\n    │\n    30-100 people?\n    ├─ Yes → All 5 levels\n    └─ No → All 5 + skip-level reviews + function sub-cadences\n```\n\n### Is This Meeting Worth Keeping?\n\n```\nDoes it produce decisions?\n├─ No → Can it be async?\n│   ├─ Yes → Make it async, cancel the meeting\n│   └─ No → Redesign with decision agenda\n└─ Yes → Are the right people in the room?\n    ├─ No → Fix attendee list (fewer > more)\n    └─ Yes → Keep it\n```\n\n---\n\n## Common Mistakes\n\n**1. Adding meetings as you grow**\nReplace them. At 200 people, the CEO should be in fewer meetings than at 50.\n\n**2. Status update meetings**\nIf it can be an email, it should be an email. Meetings are for decisions.\n\n**3. Changing metrics every quarter**\nConsistency enables trend identification. Same dashboard, every time.\n\n**4. Consensus culture**\nName the decider. Let them decide. Inform everyone else.\n\n**5. All information in Slack**\nEphemeral, noisy, unsearchable. Important decisions go in docs.\n\n**6. Quarterly planning that produces 30-page docs**\n3-5 priorities on one page. That's the output.\n\n---\n\n## Quick Reference\n\n**Meeting architecture:**\nDaily standup (15 min) → Weekly functional (60 min) → Weekly all-hands (60 min) → Bi-weekly leadership (90 min) → Quarterly planning (half-day)\n\n**Weekly metric dashboard:**\n8-12 metrics, same format every week, traffic light colors, one context sentence per metric, owner + action + deadline for every RED\n\n**Quarterly planning cycle:**\nWeek 1: Retro + data → Week 2: Priority setting (3-5 max) → Week 3: OKR cascade + resources\n\n**Decision authority:**\nType 1 (irreversible): CEO\u002Fleadership, 1-2 weeks → Type 2 (reversible): Function owner, same day\n\n**CEO weekly update:**\nWeek focus → North star progress → Wins → Blockers → Ask\n\n**Information flow:**\nDaily: Slack wins\u002Fcustomer-voice → Weekly: CEO email + function updates → Monthly: All-hands + skip-levels → Quarterly: Planning share + demos\n\n---\n\n## Related Skills\n\n- **enterprise-account-planning**: Stakeholder management and deal cadence patterns\n- **0-to-1-launch**: Launch-specific execution cadence\n- **board-and-investor-communication**: Board meeting structure and investor updates\n\n---\n\n*Based on operating cadence design across companies scaling from 20 to 1,000+ employees, including the five-level meeting architecture that survived 3x headcount growth, the weekly reporting format that caught pipeline problems 3 weeks earlier than monthly reviews, and the CEO weekly update format refined across multiple companies. Not theory — patterns from building operating systems through hypergrowth and teaching them to the next team.*\n\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":45,"source":46},"Smit Patel (https:\u002F\u002Flinkedin.com\u002Fin\u002Fsmitkpatel)","https:\u002F\u002Fgithub.com\u002Fbeingsmit\u002Ftechnical-product-gtm","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Fgithub\u002Fawesome-copilot\u002Fgtm-operating-cadence",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill gtm-operating-cadence",{"tool":62,"command":63},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill gtm-operating-cadence",{"tool":65,"command":66},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill gtm-operating-cadence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fgithub\u002Fawesome-copilot\u002Fgtm-operating-cadence\u002FSKILL.md",true,[],[71,85,95,104,110,117],{"skillNo":72,"name":73,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":39},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[82,83,84],"model","model hierarchy","model hierarchy skill",{"skillNo":86,"name":87,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":91,"publishedAt":39},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[90],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[92,93,94],"MCP","zoom","zoom mcp",{"skillNo":96,"name":97,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":39},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[101,102,103,93],"sdk","zoom apps sdk","apps",{"skillNo":105,"name":106,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":39},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[106],{"skillNo":111,"name":112,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":39},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[115],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[112],{"skillNo":118,"name":119,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":39},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[119]]