The job
A CEO wants a monthly leadership sync. Every second Tuesday at 10 AM. Same agenda. Same people. The brief arrives beforehand. The notes are published after. It’s the rhythm the business operates by. But someone has to calendar it. Prep the brief. Send the reminder. Publish the notes. Track the decisions. Without the infrastructure, the cadence gets skipped. The business drifts.
The dish holds the operating calendar. It knows when leadership syncs happen. When board meetings are scheduled. When quarterly reviews run. When budget planning starts. It preps the brief before each meeting. It publishes the notes after. It tracks decisions across months. The cadence runs. The Chef shows up to moments that are already prepared.
Plated well, this looks like: the business operates on a predictable rhythm. Leadership knows when decisions will be made. The team can plan around the cadence. Information moves consistently through the same channels. The Chef isn’t firefighting the calendar. The rhythm carries itself.
The recipe
All seven ingredients still apply. The leverage on this dish isn’t a single recipe ingredient. It’s the Chef’s stance. This dish stays in DECIDING on the Four D’s. The station does the heavy lifting on the mechanical parts (scheduling, prep work, tracking decisions). The Chef owns the design. The cadence, the agenda, the decision framework. Those come from the Chef’s taste.
Output Over Process (Ingredient #5) is the second lever. The destination isn’t “build a calendar.” It’s “ensure that when a leadership sync happens, everyone walks in prepared and the decisions that matter get made.” The output is working rhythm, not just scheduled time.
Context (Ingredient #2) runs through everything. The station needs to know what data each decision depends on. What prep work happens before each meeting. What gets published after. Where decisions are tracked. Without this context, the station can calendar a meeting but can’t prep for it.
Examples (Ingredient #4) are the three past operating cycles. The last three quarters. What the cadence looked like. What happened in each rhythm window. What decisions came from what meetings. The station learns not just the mechanics but the logic.
How to build it
-
Design your operating cadence. Weekly check-ins for what. Monthly reviews of what. Quarterly planning for what. Annually what gets decided. Write it down. This is the Chef’s design. The station holds it.
-
Name each meeting in the cadence. Leadership sync. Budget review. Quarterly planning. Customer council. Board meeting. For each, write: who attends, what gets decided, what prep is needed, what happens to the output.
-
Map the prep work for each meeting type. Leadership sync needs last week’s notes and project status. Budget review needs actuals and forecast. Quarterly planning needs market trends and backlog. You know what prep lands on the table. Name it.
-
Map the output of each meeting type. Leadership sync produces meeting notes and action items. Budget review produces variance analysis. Quarterly planning produces the Q roadmap. Where does each output go. Who needs to see it.
-
Build the decision tracker. From leadership sync to quarterly planning, decisions get made. Where are they tracked. How does the next meeting reference the previous decisions. Build the through-line.
-
Show the station the last three cycles. The actual rhythm. The actual prep. The actual outputs. The station learns your cadence as it lives, not as you theoretically describe it.
-
Have the station hold the calendar. Schedule the next month’s meetings. Prep the briefs. Track when outputs need to be published. Ensure nothing slips.
-
Review the rhythm quarterly. Does the cadence still serve the business. Are the right decisions getting made at the right time. Is the prep work actually preparing for the decisions. Refine if needed.
What breaks it
-
The cadence isn’t actually designed. You say “we do a monthly sync” but the agenda changes every month. The timing slips. Sometimes it happens. Sometimes it doesn’t. The station can’t hold rhythm if rhythm doesn’t exist.
-
The prep work is disconnected from decisions. You prep a brief but nobody uses it in the meeting. Or the meeting needs data that wasn’t in the brief. Prep becomes busywork. The station loses track of what actually matters.
-
Decision tracking is invisible. A decision gets made. Nobody writes it down. The next meeting, someone re-debates it. Decisions don’t accumulate into strategy. The cadence becomes theater.
-
The Chef isn’t actually designing. You tell the station “run a quarterly planning meeting” but you haven’t thought about what quarterly planning means for your business. The station runs a meeting. You don’t own it. The decision framework is weak.
When it’s working
By week one, the cadence is named and the station holds it. Meetings are scheduled. By week two, prep work is landing before meetings. The Chef walks in prepared. By week three, decisions are getting tracked. The decision register is current. By week four, the cadence is running. The Chef knows when decisions will be made. The team knows when information will move. The business operates on a rhythm the Chef designed and the station holds.
The signal that the recipe is sharp: three months later, a decision from the January quarterly planning is being referenced correctly in the April leadership sync because the decision tracking was thorough and the Chef designed a cadence where decisions accumulate into strategy.
Monday Move
Map your operating rhythm for the last quarter. Every meeting. When it happened. Who attended. What got decided. Where the output went. Show the station. This is what “holding the cadence” means. Have it design the calendar for next quarter based on the pattern. Does the rhythm stay the same. Does it adapt. How does the station know when to adapt versus when to hold.
Dish 10 of 10 on the Operations Station. Build-note leverage: Four D’s stance (DECIDING). Station holds the cadence; Chef owns the design.