Marvourneen K. Dolor, PhD

Status Updates Don't Need a Meeting

Photo by Angela Pompermaier on Unsplash

Layer 3: Cadence

Clarity and Alignment are established in intensive sessions. Cadence maintains them through ongoing rhythm. Without cadence, entropy wins.

The Operating Rhythm

The meeting rhythm that maintains Clarity and alignment over time:
  1. Daily (optional): A short touchpoint, 10 to 15 minutes, for blockers and priorities. Not for problem-solving.
  2. Weekly: A staff meeting for real problem-solving and issue resolution, not status updates, plus 1:1s with direct reports focused on coaching and development.
  3. Monthly: A problem-solving session for cross-functional issues that require multiple perspectives.
  4. Quarterly: A strategic check-in to revisit the six questions, reflect on progress, and reset priorities.
  5. Annually: An offsite for deep strategic work, relationship building, and a full clarity refresh.

Here are a couple of helpful videos that drive home the key points:

  • Patrick Lencioni describes the four types of meeting, all of which are necessary for effective communication of organizational clarity - Meetings
  • Claire Hughes-Johnson, former COO of Stripe on why meetings require intentional design to be worth anyone's time - Running an Effective Staff Meeting

The throughline across all of these: meetings are for alignment and problem-solving, not status updates. Status should be visible asynchronously.

You’ll know this is working when people leave meetings with decisions made and next steps clear, and when the question “didn’t we already decide this?” stops being a recurring theme.

Cadence maintains Clarity and Alignment. But the rhythm only works if the people running it know how to bring out the best in those around them. That's Layer 4: Development.

References: Death By Meeting (Patrick Lencioni); The Four Disciplines of Execution (Chris McChesney, Sean Covey, and Jim Huling)

Every Conversation Either Grows Capacity or Diminishes It

Photo by Femke Schreurs on Unsplash

Layer 4: Development

Organizations invest significant resources to hire talented people, then often fail to grow them. This layer is about becoming a multiplier: a leader who makes everyone around them smarter and more capable.

Development is not a separate activity bolted onto the other three layers. It is the mechanism through which clarity and alignment propagate. Leaders who coach well are literally how the cascade works. Every 1:1 conversation, every delegation decision, every piece of feedback either grows capacity or diminishes it.

The Coaching Stance

Default to asking, not telling. The goal is to help people access their own knowledge and develop their own plans.

Stanier's core questions are deceptively simple: “What’s on your mind?” “What’s the real challenge here for you?” “What do you want?” “What was most useful for you?”

The discipline: Stay curious a little longer. Rush to action a little slower.

Wiseman's multiplier practices build on each other: start with the mindset shift to change how you show up: 
  • "Create space for others to contribute. Don't fill the air." This is a touchstone whether in a quarterly strategic check-in or a 1:1. 
  • Your monthly problem-solving meetings will improve if you "Ask questions that make people think harder, not questions that lead them to your answer" and "Invest in debate and constructive conflict. The goal is the best answer, not the fastest one." 
  • And finally, in line with the very practical advice from "The Effective Manager": "Give ownership of problems, not just tasks" and "Expect people's best work and hold them to it." If you've spent the time on Layers 1 & 2 (Clarity and Alignment) your people will know what they are doing and why, and you'll know this because of their back-brief telling you what they're going to do and how.

You’ll know this is working when your team starts solving problems you didn’t assign, when meetings generate better ideas than you’d have come up with alone, and when people seek out stretch assignments rather than waiting to be told what to do.

The Cascade

This framework isn’t just for the top team. Each leadership layer applies the same system to their own team:

Level 1: Executive team establishes clarity on the six questions
Level 2: Each executive briefs their leadership team and receives back-briefs
Level 3: Each leader applies the same cycle to their teams

Result: Aligned intent flows through the organization; commitment and feedback flow back up.

The cascade only works if every leader in it is doing this. That's what implementation actually requires.

Now that we've covered all four layers, the next question is how to actually implement them without losing momentum. That's what the first 90 days looks like.

References: The Coaching Habit (Michael Bungay Stanier); Multipliers (Liz Wiseman); The Effective Manager (Mark Horstman, Kate Braun, and Sarah Sentes)

The First 90 Days

Photo by Peter Campbell Smith on Unsplash

Implementation follows a deliberate sequence. Rushing to Layer 3 (Cadence) without establishing Layer 1 (Clarity) creates meetings without meaning.

Days 1–30: Establish Clarity

  • Senior leader commits to the process and communicates intent to leadership team
  • Schedule offsite or extended session (minimum half-day, ideally full day)
  • Facilitator conducts pre-work conversations with each leader
  • Leadership team works through the six questions together
  • Document answers in shared language; identify where alignment is weak

You’ll know this phase succeeded when team members describe the clarity work as “the conversation we should have had years ago.”

Days 31–60: Build Alignment

  • Senior leader delivers strategic intent briefing based on clarity work
  • Each leader prepares a back-brief: what they’ll do, how, what they need
  • Back-brief session surfaces gaps and misunderstandings
  • Iterate until alignment is genuine, not performative
  • Connect individual goals to shared strategic intent

You’ll know this phase succeeded when leaders stop asking “what are we supposed to be doing?” and start debating “how do we best accomplish this?”

Days 61–90: Establish Cadence

  • Implement new meeting rhythm or refine existing one
  • Shift staff meetings from status updates to problem-solving
  • Begin coaching-oriented 1:1s
  • Schedule first quarterly strategic check-in
  • Each leader begins clarity work with their own team (cascade begins)

You’ll know this phase succeeded when the meeting rhythm starts to feel like “how we work” rather than “another thing on the calendar.”

Ongoing: Develop and Maintain

Layer 4 (Development) is woven throughout, not a separate phase. Quarterly check-ins revisit clarity and alignment. Annual offsites provide a deep refresh. Without ongoing attention, entropy wins.

Who This is For

This framework is for any leader who manages other leaders, or who wants to. The symptoms described in It's Not a People Problem, show up in teams of five and organizations of five thousand. Drift happens at every scale. The sequence scales too.

The two conditions that actually matter are readiness and stability. The senior leaders needs to want to change and be willing to go first. This work requires vulnerability at the top. If the person leading the team treats this as something for everyone else to do while they observe, it won't work. And the team needs to be stable enough to invest in foundational work. In the middle of a crisis or major restructuring, tactical survival takes precedence.

If your relationships are completely broken or there's active hostility on the team, different work is needed first. But if you recognize the symptoms and have a team that's capable of honest conversation, this is for you.


Implementation Notes

Starting Points

Start with the leadership team you’re part of or lead
A single alignment session can be the entry point
Build credibility with small wins before proposing the full system
Use facilitation to create safety for honest conversation

What This Is Not

Not a rigid process. Adapt to context
Not a replacement for good judgment
Not about more meetings. About better ones
Not something the most senior person in the room should facilitate. Get someone else to run the process so you can focus on the content
Not a one-time fix. It’s an operating system that requires maintenance

In the final part of this Leadership Operating System series, we'll talk about why implementation fails and how to avoid these pitfalls.

Why This Fails


Being honest about what makes implementation hard increases the odds of success. This work fails when:

The Senior Leader Won’t Go First - This one is non-negotiable
This framework requires the most senior leader to model vulnerability. They need to admit uncertainty, invite challenge, and be open to changing their mind. If the CEO or department head treats this as something for “the team” to do while they observe, it won’t work. The cascade starts at the top, or it doesn’t start.

Conflict Gets Avoided Instead of Surfaced
The clarity and alignment work will surface disagreements that have been papered over. This feels worse before it feels better. Teams that retreat to false harmony when tension emerges will end up with false alignment: agreeing in the room, disagreeing in the hallway.

The Team Mistakes Activity for Progress
Holding a clarity session doesn’t create clarity. Documenting answers doesn’t mean people believe them. The six questions require genuine wrestling, not wordsmithing. If the team treats this as an exercise to complete rather than work that matters, the answers will be platitudes that no one references again.

It’s Treated as a One-Time Fix
This is an operating system, not a workshop. The clarity session establishes a foundation, but without ongoing cadence to maintain alignment and develop capability, entropy wins. Organizations that do the initial work but don’t commit to the ongoing rhythm will find themselves back where they started within six to twelve months.

The Time Investment Feels “Unproductive”
Leaders who can’t tolerate that discomfort will abandon the process before it produces results. The payoff is in reduced rework, faster decisions, and less wasted effort, but those benefits take time to materialize. The leadership team that spends 2 days on clarity work stops relitigating the same decisions for the next twelve months. That's the highest leverage use of their time.

That's the Leadership Operating System. Eight posts, four layers, one principle: culture change is leadership behavior change that propagates. Get the top team healthy first. Then cascade.

--
Which of these failure modes have you seen most often? I'd genuinely like to know. Please comment below or send me a message.

For a PDF of the full Leadership Operating System head to: https://articles.mkdolor.com/leadership-operating-system 
No email address required.