neon-rutger/b2b-revops-skills/operating-cadence-designer

Operating Cadence Designer

Purpose

This skill helps design and install the operating cadence for your organization. The cadence is the calendar that makes the revenue operating system real. It connects strategy (strategy scorecard), visibility (revenue dashboard), and execution (weekly/monthly rituals).

Without a cadence, leaders waste time in meetings that produce no decisions. With a cadence, every ritual has a clear purpose, owner, and output. This skill walks through the design and installation process.

When This Skill Activates

Use this skill in three main situations:

1. No existing cadence

Your organization has no consistent rhythm for revenue decisions. Meetings happen ad hoc. Leadership time is fragmented across email, Slack threads, and back-channel conversations. There is no single source of truth for the week's agenda or the month's priorities.

Design task: Build a complete weekly, biweekly, monthly, and quarterly rhythm from scratch. Start with the simplest version (7 weekly rituals + 1 biweekly + 2 monthly + 1 quarterly) and adapt to your organization's size and stage.

2. Broken or inconsistent cadence

Your organization has some rituals, but they're inconsistent: some happen on schedule, some get canceled or rescheduled. No one knows which meetings are mandatory. There is no clear escalation path from a signal to a decision.

Design task: Audit existing rituals, apply the 5P gate, consolidate into a clean calendar, and install decision rules that tell people when to escalate.

3. Cadence exists but no decision rules

Your organization has the calendar but no signal-based decision rules. Meetings happen, data is reviewed, nods happen, but nothing actually changes. Decision latency is long. Experiment kill rate is low. The cadence is status theater, not a control system.

Design task: Install signal-based decision rules on top of the existing calendar. Define 8-12 key signals, set thresholds, route triggers to rituals, and train people on escalation.

The 5P Standard

Every meeting must pass the 5P gate. This is the non-negotiable foundation. If any P is missing or fuzzy, the meeting should be canceled or rescheduled.

The 5Ps

1. Purpose: One clear sentence: "By the end of this meeting, we will...". This must finish with a concrete outcome (decision, list, design, changed plan), not an activity (discuss, review, understand).

1. Product: A tangible artifact that proves the meeting was worth the time.

• Examples: 3 decisions in the Decision Log with IDs and owners; prioritized problem list; A3 draft; updated experiment backlog; changed forecast or strategy scorecard tile.
• Not: "discuss pipeline" or "update everyone" (these are verbs, not products).

1. People: The smallest set of roles that can create the product and own the actions.

• No spectators. Everyone must bring proof, make decisions, or leave with actions.
• Invite by role, not just by name. Example: "one VP Sales" instead of "everyone from Sales".

1. Process: How the time will be used.

• 2-5 bullet agenda with explicit timeboxes.
• Which panels in the revenue dashboard (if applicable).
• Who facilitates, who decides, who takes notes, how the close happens.

1. Proof: The facts and pre-work needed so time is spent deciding, not discovering.

• Bowtie metrics, GRR/NRR, customer quotes, win/loss summaries, A3 snippets.
• Pre-reads sent at least one working day in advance for decision sessions.
• Clear baseline so you can measure later if the decision worked.

5P gate rule: If any P is missing or fuzzy, cancel the meeting or replace it with an async update. A healthy cadence has a non-zero cancel rate (5-15% typical; practice-based).

Cadence Design Workflow

Follow this sequence when designing a cadence for your organization:

Phase 1: Assess Current State (Week 1)

1. Map existing meetings. What meetings happen now? List them with owner, frequency, duration, attendees, and stated purpose. Include 1:1s, team standups, leadership syncs, and functional reviews.

1. Run the 5P audit. For each meeting, can the owner write down all 5Ps clearly? Where are the gaps? Common failures: no clear Purpose, no Product (just "discuss"), no defined attendees, no pre-work or proof.

1. Identify decision gaps. Where are decisions made today? In the meetings, or in side channels and follow-ups? Is there a Decision Log? How long does it take from insight to decision?

1. Assess data readiness. Is there a revenue dashboard with live dashboards? Can people answer the key questions (pipeline health, GRR/NRR, constraint wall, experiment portfolio status) in minutes?

1. Interview key roles. Ask CRO, CEO, CMO, VP Sales, Head of CS: What decisions are you struggling to make? What meetings feel like waste? Where do you spend time that creates no value? What surprises you about the current system?

Output: A 1-page "Current State" document with audit findings, three pain points ranked by impact, and a rough sketch of what meetings should exist.

Phase 2: Design the Calendar (Week 2-3)

Use the operating cadence template. Adapt the rhythm to your organization's size and stage.

Weekly (7 rituals); 4.5 hours total

1. Revenue Dashboard: Pipeline and Decisions (75 min)

• Owner: CRO
• Purpose: Review bowtie, pipeline health, constraints, then make at most 3 decisions or A3 assignments
• Product: Decisions logged with IDs, owners, due dates
• Panels: Bowtie and segment views, pipeline by stage, constraint wall, experiment portfolio

1. Marketing Demand and Efficiency Loop (45 min)

• Owner: CMO or Head of Growth
• Purpose: Improve demand quality and SDR efficiency
• Product: Adjusted campaign focus, new experiments with stop rules

1. Sales Pipeline and Efficiency Loop (45 min)

• Owner: VP Sales
• Purpose: Improve pipeline health and sales efficiency
• Product: Clean pipeline, surfaced stuck items, problems framed as A3s

1. CS Value and Efficiency Loop (45 min)

• Owner: Head of CS
• Purpose: Improve retention and expansion
• Product: Account attention list, new countermeasures

1. Coaching and Revenue Craft Loop (45 min)

• Owner: Sales and CS leaders
• Purpose: Turn customer conversations into better plays
• Product: Coaching actions with check-in dates, playbook updates

1. Breach and Incident Huddle (30 min)

• Owner: RevOps on call
• Purpose: Catch and contain SLO breaches
• Product: Owner and containment plan for each breach

1. AI and Automation Integration (45 min, starting Week 3)

• Owner: RevOps and Platform lead
• Purpose: Embed AI into the revenue system at four levels: L1 (signal tagging and automation triggers), L2 (breach detection agents that alert decision-makers), L3 (experiment idea generation and analysis), L4 (autonomous agents making decisions within guardrails)
• Product: Prioritized automation experiments with cost-benefit, execution plan, and kill rules. Monthly AI rhythm advancement (L1 to L2, L2 to L3, etc.)
• Integration: Connects to the Breach Huddle (L2 agents feed incident alerts) and Demo and Retro (L3 and L4 results reviewed monthly)

Bi-weekly (1 ritual); 60 min

1. Demo and Retro (60 min)

• Owner: Rotating facilitator
• Purpose: Show shipped experiments and countermeasures, decide keep/kill/scale
• Product: Keep/kill/scale decisions logged in Decision Log

Monthly (2 rituals); 150 min

1. Strategy and Lever Review (90 min)

• Owner: CEO and CRO
• Purpose: Review strategy scorecard, choose levers, adjust WIP and SLOs
• Product: Updated WIP caps, next quarter lever list

1. Data Spine and Definition Review (60 min)

• Owner: RevOps and Data lead
• Purpose: Check data freshness, completeness, and activation. Ensure decision-to-execution loops close via reverse ETL (data changes trigger CRM updates, audience sync, and alert routing).
• Product: Data health status, definition change log, reverse ETL activation status (which signals route to which systems: Salesforce, email platforms, messaging tools)
• Integration: Validates that the revenue system feeds real-time data to decision-makers and that decisions propagate back to the stack (via Hightouch, Census, Segment, or native reverse ETL)

Quarterly (1 ritual); 180 min

1. Quarterly Reset (2-3 hours)

• Owner: CEO
• Purpose: Refresh strategy scorecard, confirm cadence, align next quarter targets and SLOs
• Product: Updated strategy scorecard, confirmed cadence changes, new SLOs

Key design rules:

• Keep weekly rituals short and focused. No meeting longer than 75 minutes.
• Most rituals feed the same revenue dashboard. No parallel streams.
• Reduce, never add. If you're tempted to add a meeting, cancel an existing one first.
• Schedule decision sessions early in the week. Leave space for countermeasures and follow-up.

Output: Color-coded calendar showing all rituals, owners, attendees, duration, and which revenue dashboard panels they use.

Phase 3: Build Ritual Cards (Week 3-4)

For each ritual, create a one-pager (the "ritual card") that shows:

• Purpose statement
• Inputs (which dashboards or documents are needed)
• Outputs (what gets decided or changed)
• RACI (Driver, Approver, Contributors, Informed)
• Tollgates (what has to be true for the meeting to happen)
• Cancel rule (when to cancel or shorten)
• Pre-work and proof checklist

Adapt owner names and timings to your organization. Print and laminate them. Put them in the revenue dashboard room so facilitators can see the standard at a glance.

Phase 4: Install Signal-Based Decision Rules (Week 8-10)

Once the calendar is stable and people are attending, layer in signal-based decision rules. This is Phase 2 of the 90-day rollout (see below).

1. Week 8: Choose 8-12 key signals from the four capability streams (Customer Insights, Revenue Motions, Enablement, Governance). Start with signals where you already have data.

1. Week 9: Set thresholds using 6 months of historical data. When a signal crosses a threshold, it becomes a trigger (something has changed enough that we need to act).

1. Week 10: Route each trigger to a specific ritual in the cadence. For example:

• Pipeline coverage SMB <2.5x for 3 weeks -> escalate to Marketing Demand Loop
• Win rate drops >5pp -> open A3 in Sales Pipeline Loop
• Decision latency >14 days -> escalate to Strategy and Lever Review
• 5P cancel rate 0% for 4 weeks -> challenge in Strategy and Lever Review

Print the signal map and post it in the revenue dashboard room. No new meetings. Just clearer escalation rules.

Output: Signal-based decision rules matrix with 8-12 signals, thresholds, and routing rules.

Phase 5: Transfer Ownership (Week 11-12)

In the final weeks of the 90-day program, transfer operational ownership of the cadence to your team. The Cadence Owner (usually the CRO or RevOps lead) becomes accountable for:

• Keeping the calendar on track
• Enforcing the 5P gate at the start of each meeting
• Logging decisions and actions in the Decision Log
• Monitoring cadence health KPIs
• Proposing cadence changes only in the Quarterly Reset

Run a "Cadence Keeper" workshop where the Cadence Owner and RevOps lead practice facilitating rituals, handling the 5P gate, and routing signals to the right forum.

90-Day Installation Program

The cadence installs in a 12-week program with clear phases and handoff points.

Phase 1: Stand-up (Weeks 1-2)

Goal: Assess the current state and design the ideal cadence.

• Audit existing meetings and run 5P gate
• Interview key roles (CRO, CEO, CMO, VP Sales, Head of CS)
• Map decision gaps and data readiness
• Design the calendar (weekly, biweekly, monthly, quarterly)
• Prepare ritual cards
• Brief the leadership team on the design