Most newly-promoted senior leaders inherit broken meeting structures and try to operate within them. They attend the meetings their predecessor attended. They keep the cadences they were given. They optimize within an architecture they didn't design.
This is a mistake.
The single highest-leverage hour of your month, in the first 90 days, is the hour you spend redesigning your operating cadence. Get the forum architecture right and the rest of your tenure runs on rails. Get it wrong and you spend years compensating for an inherited structure that doesn't fit your role.
The five forums every senior leader needs
An effective operating cadence has five distinct forums. Each does specific work. None can substitute for another. Most organizations conflate two or three of these into combined meetings that fail to do any of the underlying work well.
Strategy covers multi-quarter direction. Capability investments. Market positioning. Organizational design changes. Where the function is going. Cadence is monthly or quarterly. Attendees are your direct reports plus key cross-functional partners. Output is decisions that shape direction.
Operations covers how the function is running. KPI reviews, process performance, resource allocation within current quarter, removing blockers. Where the function is now. Cadence is weekly. Attendees are your direct reports. Output is decisions that adjust execution.
People covers talent reviews, succession, capability development, hiring decisions, performance conversations, organizational health. Cadence is monthly for major reviews, plus a recurring rhythm of one-on-ones with each direct report. Attendees vary by topic. Output is decisions about who, where, and how to develop.
Risk covers strategic risks to the function or business, including operational, financial, reputational, and capability risks. Cadence is monthly to quarterly. Attendees are your direct reports plus risk or finance partners as needed. Output is a prioritized risk register and mitigation decisions.
External covers customer, partner, board, regulatory, the world outside your function. Cadence varies by relationship, typically monthly or quarterly. Attendees vary. Output is decisions about how the function engages with the outside.
Most newly-promoted senior leaders have one or two of these forums functioning well, two or three barely functioning, and one missing entirely. The audit is honest. Walk through the five and identify which exist, which work, which need rebuilding, and which need to be created from scratch.
Forum design principles
Each forum needs deliberate design. Six questions to answer for each.
Who attends? Restrict ruthlessly. The wrong attendee, whether too senior, too junior, or not accountable, corrupts the forum's purpose. If someone attends because they want to know what's happening, that's the wrong reason. They can read the minutes.
What gets decided here? Be explicit. If a decision could plausibly be made in any of three forums, name which one is correct. Otherwise the decision gets relitigated in each.
What does not get decided here? Equally important. The Operations forum doesn't make Strategy decisions. The Strategy forum doesn't review weekly KPIs. The discipline of saying "that belongs in another forum" preserves each one's value.
What's pre-wired versus decided in the room? Most decisions in senior forums should be pre-wired before the meeting. The forum ratifies and aligns. If your meetings are where decisions actually get made for the first time, your pre-wiring discipline is broken.
What's the standing agenda? Each forum should have a recurring structure that occupies 70 to 80 percent of the meeting. The remaining time handles whatever is current. The structure prevents the forum from becoming a free-form discussion.
What's the follow-through discipline? What happens between meetings? Who tracks decisions, holds people to commitments, surfaces emerging issues? Without follow-through, the forum is theater.
The weekly, monthly, quarterly nesting
The five forums nest into a rhythm. Weekly Operations handles the tactical. Monthly Operations, People, and Risk reviews handle the operational arc. Quarterly Strategy and External handle the strategic and stakeholder work. Annual planning integrates everything.
The nesting matters because each scale of decision has its own appropriate scale of conversation. Weekly decisions made in a strategic forum produce overreach. Strategic decisions made in a weekly forum produce premature commitment.
The discipline is matching the conversation to the rhythm. A new piece of information that comes in mid-week may feel urgent. The question is, does it belong in this week's Operations review, or does it actually belong in the monthly Strategy session two weeks from now? Most newly-promoted senior leaders consistently treat strategic questions as if they require immediate weekly answers. They don't.
Escalation paths that actually work
Connected to forum architecture is escalation architecture. What gets escalated, to whom, by when, with what authority.
Most escalation paths fail because of unclear thresholds. The team doesn't know what merits escalation, so they either escalate everything, which overwhelms senior leadership, or nothing, which leaves issues to compound.
The fix is specificity. For each major decision class, document who has authority to decide what magnitude of decision. What triggers escalation upward. How long the escalating party has to receive a response. What the escalation must include, which is always a recommendation, not just a question.
The escalation discipline matters because it determines whether your forums work. If problems are being solved through ad-hoc escalation rather than within the designed forums, the cadence isn't serving its purpose.
Auditing your existing cadence
The audit takes 90 minutes. It's worth doing in week three or four of any new senior role.
List every recurring meeting you currently attend or run. For each, identify which of the five forums it belongs to.
Identify duplicates. Two meetings serving the same forum purpose is one too many. Combine them.
Identify gaps. Which of the five forums has no dedicated meeting? Create one.
For each meeting that's poorly designed, like wrong attendees, unclear purpose, no decisions made, decide whether to redesign it, replace it, or kill it.
For each meeting that's well-designed but inefficiently run, identify the specific change needed (sharper agenda, better pre-reading, tighter time, clearer follow-through).
Output is a one-page operating cadence document showing the five forums, their frequencies, their attendees, their purposes, and their interactions. This becomes your reference document and your team's operating model.
Why this is the highest-leverage work
An hour spent designing the operating cadence affects thousands of subsequent hours of organizational work. Every meeting that runs better is multiple people operating more effectively. Every decision made at the right altitude in the right forum is hours saved across the team. Every blocked issue that gets surfaced cleanly through the right path is days of delay avoided.
Most senior leaders never do this design work. They accept the inherited cadence as fixed. They optimize within it rather than redesigning it. The cost is a multiplier on everything else they do. Every other discipline operates against a backdrop of broken rhythm.
The leaders who do invest in cadence design have a structural advantage that compounds over their tenure. The first hour of design work pays off every week, for years.
Related: The First 90 Days as a Senior Leader and Decision Altitude.