The Operating Cadence and GTM Council

The worst standing meeting I ever sat in ran ninety minutes every Monday and decided nothing. A sales manager read the pipeline slide out loud. Marketing read the leads slide. Customer Success read the churn slide. Every number on those slides was already sitting on a dashboard the whole room had open on a second monitor. We recited it to each other, nodded, and went back to our desks to do exactly what we were going to do anyway. The meeting reported the dashboard back to the people who had built it, and called that governance.

Module 6 ended with the instrument built. In Attribution and Pipeline Analytics we closed the loop on where pipeline comes from and how it converts, and across that module we stood up the live Bowtie dashboard: leading and lagging tiles, VM, CR, and Δt at the altitudes The Hierarchy of Metrics taught us to keep separate. A dashboard measures the business. It does not change it. The thing that converts a measured business into a changed one is a cadence: a fixed rhythm of meetings, each at its own clock speed, each ending in a decision. Revenue Architecture gives that rhythm two anchors, a monthly GTM Council (Action 11.20) and a recurring GTM Diagnostics meeting of sixty to ninety minutes (Action 11.21), both built on the Bowtie living on a permanent dashboard. This chapter is how you run them so they produce decisions instead of minutes.

The cadence stack

A single meeting cannot govern a factory that moves at four different speeds at once. Deal hygiene changes hourly. Conversion rates move week to week. Motion economics shift over a month. The choice of which model you are even running changes over quarters. So the cadence is a stack, not an event, and each tier reviews the altitude of metric that moves at its clock speed.

The rule that keeps the stack honest is the one the hierarchy of metrics already gave you: review a metric at the cadence at which a human can act on it, and no faster. Put executive lagging metrics (ARR, net revenue retention) in front of a daily standup and you get panic and thrash, because they cannot move that fast and the noise swamps the signal. Put a leading throughput metric (response time, discovery-to-opportunity conversion) in a quarterly review and the breach is a fossil by the time anyone sees it. Each tier owns the metrics that are both fast enough to have moved since the last meeting and slow enough that a decision can still bend them before the next.

Exception-only, not recitation

The single change that turned my Monday funeral into a working meeting was a rule: we do not read the dashboard. Everyone reads it before they walk in. The meeting starts at the exceptions.

An exception is a metric that has crossed a line you set in advance. The weekly scorecard I run carries a live qualified-pipeline coverage figure against the quarter’s goal (it has sat between 0.72x and 0.87x this quarter); the cell is built to flag when it drops under the line, not to be admired when it is fine. Coverage in the forecasting sense (roughly one divided by your win rate, from Forecasting) sets the threshold; the scorecard’s job is to shout when the live number falls through it. On-pace metrics get one word, “green,” and no airtime. The eight metrics that are fine do not need eight narrations. The one that broke needs a diagnosis, an owner, and a date.

The weekly GTM Diagnostics meeting

The weekly meeting is the engine room of the cadence. Revenue Architecture scopes it at sixty to ninety minutes with the Bowtie on a permanent dashboard (Action 11.21), and the discipline is entirely in the run of show. Recite nothing. Interrogate the exceptions. Leave with actions.

The tell that this meeting is working is mechanical: someone’s calendar is different on Tuesday because of what happened on Monday. If you could replace the meeting with an email that says “the dashboard is updated,” it was never a diagnostics meeting, it was a status meeting wearing a longer invite.

Tracing every exception to a Bowtie stage is what keeps the meeting from dissolving into blame. A coverage miss is not a “sales problem,” it is a specific volume or conversion metric at a specific stage. The diagnosis names the constraint, the action attacks it, and the log remembers both so next week’s opening step has something to close.

The monthly GTM Council

If the weekly meeting runs the engine, the monthly GTM Council decides whether the engine is the right one. Action 11.20 makes it the standing cross-functional body, the same three layers Revenue Architecture assembles to deploy an operating model in the first place: executives, managers, and the people doing the work. Where the weekly meeting asks “are we on pace and where are the exceptions,” the Council asks “is the model working.” It reads motion economics, not deal hygiene: cost to serve against lifetime revenue by motion, gross and net revenue retention by segment, whether a conversion rate that has slid for three straight weeks is a slump or a structural break.

The Council is also where the model stewards report. Revenue Architecture assigns each of the six models an executive owner (the CFO on the Revenue Model, the CMO on the Data Model, and so on), and the monthly cadence is where those stewards answer for their model’s health. That is the seam between running the system and changing it. A weekly meeting can reroute a lead or unstick a deal. It cannot decide to re-cut territories, retire a motion, or rebuild a stage definition. Those are structural changes, and structural changes get chartered at the Council and executed through the method in the next chapter.

Ground it in real instruments

A cadence is only as good as the instruments it reads, and the instruments have to be live, not rebuilt by hand every week. Three artifacts carry the weekly tier where I work.

The first is the weekly metrics scorecard: one sheet, metric families down the rows (ARR, pipeline, pipeline by solution, pipeline generation, BDR, marketing leads, renewals) and the last thirteen-plus weeks across the columns, every cell a live query against the same warehouse the dashboards read. It was deliberately modeled on the finance team’s board-reporting sheet so the operating number and the board number reconcile by construction, not by argument. When the weekly actuals foot to the same source the forecast reads, the meeting spends its time on what the numbers mean instead of on whose numbers are right.

The second is the weekly forecast scorecard. Its call is anchored to a single node, the top of the forecast hierarchy (the chief customer officer’s number), not the sum of everyone’s optimism, and it refreshes on a fixed schedule so the Friday review reads the same figure the automation pulled, not one that got hand-massaged on the way into a slide.

Handoff

You now have the rhythm: a stack of meetings at four clock speeds, a weekly diagnostics meeting that runs on exceptions and ends in a decision log, and a monthly Council that governs the model and holds the stewards to account. Installing the cadence is what makes the rest of this course operational, because it is the loop that keeps surfacing the same message: this part of the system needs to change.

Surfacing the change is the easy half. Landing it, across a team, without the initiative dying inside a quarter, is a discipline of its own. Next, in Deploying Change: Think Big, Act Small, Move Fast, we take what the cadence surfaces and roll it out with the twenty-one-action method, the model stewards you just met at the Council, and coaching sprints that compound ten percent at a time.