From Meeting Chaos to Meeting Mastery

Welcome to the inaugural edition of The Pink Elephant Papers, where we tackle the topics that leaders see but hesitate to discuss.

Introduction: Naming the Elephant in the Room

We live in volatile times. Geopolitical tensions shift overnight. Economic uncertainty challenges our assumptions. Technological disruption accelerates beyond our capacity to absorb it. In this turbulent environment, organizations face a fundamental choice: react chaotically to external forces, or respond with disciplined focus and clarity.

Yet here's what I've observed in my 29 years of working with executive teams and leaders: even as organizations face these external pressures, they often avoid addressing internal dysfunctions that everyone can see. Certain topics remain unspoken—the proverbial pink elephants in the room.

Team meeting dynamics is one of those elephants.

Everyone knows that meetings are often dysfunctional. CEOs sit through too many meetings. Senior leaders feel frustrated by disorganized discussions. HR professionals hear complaints about meeting overload. Yet somehow, we accept this reality. We don't name it. We don't address it systematically.

Why? Because it feels operational rather than strategic. Because it seems like complaining about a fact of organizational life. Because sometimes no one wants to be the person who says, "Our meetings are a mess."

But here's what leaders instinctively understand, even if they don't always articulate it: How an executive team organizes itself, discusses issues, and makes decisions reveals the DNA of the entire organization. Meeting dynamics aren't a peripheral concern—they're a window into organizational culture itself.

As a team coach specializing in executive team development, I've spent recent months sitting in on several leadership meetings, observing team dynamics, and helping organizations elevate their collaborative effectiveness. What I witness in these meetings isn't merely about operational efficiency or time management. It's about the behaviors and thinking patterns that define organizational culture.

The behaviors repeated in executive team meetings—whether functional or dysfunctional—cascade throughout the company. If an executive team operates chaotically, without clear processes or disciplined focus, that chaos becomes embedded in the organizational culture. It fractures workflows, undermines output quality, and leaves the organization vulnerable precisely when clarity and coherence matter most.

This is why I attend these meetings. My expertise lies in observing and understanding the specific behaviors and thinking patterns that show up in how people organize themselves, engage in dialogue, and arrive at decisions. These micro-behaviors are not trivial details—they're the building blocks of organizational culture and capability.

In my previous post, I shared five common meeting mistakes I've consistently observed—mistakes that even high-performing teams make. Today, in this inaugural edition of The Pink Elephant Papers, I'm providing the solutions. Not superficial tips, but fundamental shifts in how executive teams can transform their meeting dynamics and, by extension, their organizational culture.

These solutions work. I've watched teams implement them and experience transformations. The question is: are you ready to name the pink elephant and do something about it?

Mistake #1: Meetings for Anything

The Underlying Problem

When teams schedule meetings for virtually any topic or situation—information sharing, problem discussions, updates, brainstorming, or simply "touching base"—they reveal more than poor time management. They demonstrate a lack of strategic thinking.

Here's what most leaders don't say out loud: organizing meetings for everything is an operational mindset, while being selective about when and why you meet reflects a strategic mindset.

For any leader, regardless of rank, how carefully they organize meetings signals their level of strategic maturity. Meetings are the backbone of team functioning—a team truly comes together in meetings, not when members individually perform tasks. When meetings are unfocused and poorly designed, it's not just inefficient; it's a strategic failure.

The costs are significant:

• Time waste: Hours in unnecessary meetings compound to weeks of lost strategic capacity annually
• Disrespect: It signals you don't value colleagues' time or trust their ability to handle matters independently
• Meeting fatigue: When people attend too many low-value meetings, they disengage from all meetings, including critical ones
• Diluted strategic focus: Constant context-switching prevents the deep thinking and strategic work that actually moves organizations forward

The Strategic Solution: Meetings for Decisions

The transformation is both simple and profound: use meetings primarily for decisions, not for everything else.

This shift requires strategic discipline. When teams adopt a decision-focused meeting culture, they automatically filter out low-value agenda items. Information can be shared asynchronously. Updates can be posted in shared spaces. Discussions can happen in smaller groups or one-on-one. But decisions—especially those requiring multiple perspectives, trade-offs, and collective commitment—benefit from real-time collaborative dialogue.

Decision-focused meetings naturally orient teams toward the future and action. Instead of rehashing what happened or getting lost in theoretical discussions, teams ask: "What do we need to decide today?" and "What actions will follow from our decisions?"

Being careful about when and why you meet demonstrates strategic leadership. It shows you:

• Respect the scarcity of leadership attention
• Understand the opportunity cost of gathering your team
• Can distinguish between what requires collective presence and what doesn't
• Value execution and outcomes over activity and appearance

For senior leaders and CEOs, this discipline cascades throughout the organization. When the executive team models decision-focused meetings, it sets the standard for meeting culture across all levels.

Implementation steps

• Before scheduling any meeting, ask: "What decisions need to be made?"
• If there are no decisions, consider alternative communication methods
• Structure your agenda around decision points, not discussion topics
• Track how much time your team spends in meetings focused on decisions versus other activities
• Model this discipline consistently—the executive team's behavior shapes organizational norms

Mistake #2: The Manager Leads the Meeting

The Leadership Dilemma

This is perhaps the most common question I hear from leaders: "Should I lead and facilitate the meeting, or not?"

The answer reveals a deeper confusion about what leadership actually means in a meeting context. Most leaders unconsciously assume multiple operational roles: they facilitate discussions, manage time, take notes, sometimes even play "nanny" to manage interpersonal dynamics. They believe this is what leadership requires.

It's not. This is operational management, and it creates several problems:

When managers always lead operationally, it:

• Reinforces a parent-child dynamic rather than peer collaboration among professionals
• Prevents team members from developing leadership capabilities
• Overloads the leader with tasks that should be delegated
• Reduces the leader's capacity for strategic thinking, decision-making, and coaching
• Sends the message: "You're not trusted to manage this process"

The Delegation Solution: Keep Only What Matters

Here's the breakthrough: Delegate all operational meeting roles. Keep only the decision-maker role.

This is what strategic leadership looks like in meetings. The formal leader should never facilitate, never manage time, never take notes, never handle the operational orchestration of the meeting. These are tasks that team members can and should own.

What the leader SHOULD do in meetings:

• Make and validate decisions (the only role that requires their unique authority)
• Provide strategic context and direction
• Coach team members on their thinking, collaboration, and decision-making
• Challenge assumptions and ask difficult questions
• Create space for the team to grow and develop together

When leaders delegate operational roles and focus on strategic contributions, meetings become more than problem-solving sessions—they become opportunities for team development. The leader can observe how team members interact, identify growth opportunities, and coach in real-time.

This is the coaching mindset in action. The meeting isn't just about solving today's issues; it's about building the team's capacity to function at higher levels. The leader who delegates operational roles gains the perspective and space to see the team dynamics clearly and intervene developmentally.

For HR professionals reading this: this shift fundamentally changes how you should develop leaders. Leadership development isn't about better facilitation skills—it's about knowing what to delegate and how to coach while others lead operationally.

Implementation steps

• Identify all operational meeting roles currently held by the leader: facilitator, timekeeper, note-taker, etc.
• Systematically delegate each role to team members on a rotating basis
• Provide coaching and support as team members develop these capabilities
• The formal leader participates as a team member with a clear focus: decision-making and team development
• Resist the urge to "take over" when meetings feel uncomfortable—this discomfort is often where growth happens
• Debrief after meetings: "How did we function as a team today? What do we want to adjust?"

Mistake #3: No Agenda and No Clarity on Roles

The Chaos of Unstructured Meetings

When executive teams convene without clear agendas or defined roles, they reveal low competence in alignment—one of the most critical organizational capabilities. The absence of structure isn't a minor inconvenience; it's a cultural indicator of how the organization approaches planning, preparation, and collective work.

Meetings without structure waste time, prevent effective preparation, create unequal participation, generate unclear outcomes, and frustrate everyone involved. For CEOs and senior leaders, this dysfunction is particularly costly because executive team meetings should be the highest-leverage collaborative time in the organization.

The Structure Solution: Decision-Based Agendas

The transformation begins with a fundamental shift in how agendas are constructed: Populate the agenda with decisions, not just topics.

This is the breakthrough most teams miss. Instead of listing vague topics like "Strategy discussion" or "Q4 planning," frame each agenda item as a decision to be made:

• Topic (brief statement of what we're deciding)
• Pre-read materials (context participants need to review beforehand)
• Proposed solution or decision options (not dumping problems, but bringing proposals)

This shift demonstrates clear accountability. When someone adds an item to the agenda, they're not dumping a problem on the team—they're bringing proposed solutions for refinement and decision. They've done the thinking work. They've wrestled with options. Now they're bringing the team in at the right moment: to validate, refine, and decide.

This is strategic maturity in action. It shows respect for collective time and leverages the team's capacity appropriately.

Three Critical Meeting Roles

Beyond the decision-based agenda, clarity requires defining specific operational roles. I've identified three roles as critical for high-functioning team meetings:

1. The Meeting Facilitator This person focuses on team member dynamics and ensures everyone feels included and able to voice their ideas. They monitor participation, create space for quieter voices, manage dominant voices, and ensure the agenda is covered. This is about people and process, not content.

2. The Meeting Pacer Note: This is NOT a "timekeeper" because time cannot be kept—it flows. The Meeting Pacer constantly reminds the team of time passing within specific slots agreed upon in the agenda. They're pacing the rhythm of the meeting, helping the team demonstrate competence in using their time. This role keeps the team disciplined and prevents discussions from expanding to fill available time.

3. The Meeting Decision Catalyst This person has one focus: catalyzing decisions. They constantly invite the team to conclude by asking questions like:

• "Is this a decision?"
• "What is the decision we're making here?"
• "Are we ready to decide?"

The Decision Catalyst writes down decisions using a simple, clear format and sends them immediately to everyone. This role ensures the team doesn't mistake discussion for decision-making and maintains momentum toward outcomes.

In addition to these three operational roles, the formal leader holds the fourth critical role: Decision Maker. The leader validates and authorizes decisions, but doesn't manage the operational flow of the meeting.

Implementation steps

• Shift to decision-based agenda format: topic, pre-read, proposed solutions
• Require agenda items to include proposed solutions, not just problem statements
• Assign the three operational roles: Facilitator, Pacer, Decision Catalyst
• Rotate these roles to build capability across the team
• Leader focuses solely on decision-making and team coaching
• Review meeting effectiveness regularly and adjust processes based on what the team learns

Mistake #4: Meeting Minutes Are Recorded

The False Productivity of Comprehensive Minutes

Most organizations create detailed meeting minutes that document discussions, capture opinions, and record who said what. Teams believe this demonstrates thoroughness and professionalism. In reality, they're creating content almost no one will read or reference.

Comprehensive meeting minutes create wasted effort, false productivity, information overload, and confusion. They miss the fundamental point: what matters from meetings isn't the discussion content—it's the decisions and resulting actions.

The Clarity Solution: Decision Documentation

Mature teams focus exclusively on documenting decisions. But to make this truly effective, decisions need clear accountability built in.

This is where the RACI Matrix (as an example) can become invaluable. RACI describes four types of roles people can have in relation to a decision:

• R = Responsible: Who will do the work to implement the decision?
• A = Accountable: Who has ultimate accountability for the outcome? (typically one person)
• C = Consulted: Who needs to provide input or be consulted during implementation?
• I = Informed: Who needs to be kept informed about progress?

When the Meeting Decision Catalyst (the role I described earlier) documents decisions, they should capture:

• What was decided (clear statement)
• Who is Responsible for implementation
• Who is Accountable for the outcome
• Timeline (when it will be completed)
• Any critical Consulted or Informed parties

This format connects directly to the three critical meeting roles I outlined in Solution #3. The Decision Catalyst focuses on decisions and writes only decisions—short, simple statements with clear RACI accountability, sent immediately to everyone.

This focus on decisions with clear accountability significantly increases speed and dynamic in the team. No ambiguity about who's doing what. No confusion about timelines. No wondering if something was actually decided or just discussed.

For CEOs and senior leaders, this discipline cascades throughout the organization. When the executive team models clear decision documentation with accountability, it sets the standard for how the entire organization approaches decisions.

Implementation steps

• Replace "meeting minutes" with a "decision log"
• Use RACI format for every decision: What/Who (R)/Who (A)/When
• The Decision Catalyst sends the decision log immediately after the meeting (not days later)
• Keep decisions short and action-oriented
• Make the decision log easily accessible and searchable
• Train team members to distinguish between discussion and decision
• In subsequent meetings, review previous decisions and their implementation status

Mistake #5: Meeting Attendees Are Like Tourists

The Passive Observer Problem

When people attend meetings without clear purpose or active roles, they become tourists—physically present but not truly engaged. They're going through the motions, checking it off their list, but not contributing meaningfully.

This happens when invitations are sent broadly without careful consideration, or when organizational culture equates meeting attendance with importance. The result is bloated meetings with passive observers who drain rather than contribute energy.

The Active Participation Solution

The transformation requires multiple interconnected practices:

1. Carefully Select Participants—With Roles

Before inviting someone, ask: "Why does this person need to be here?" Valid reasons include:

• They need to make or influence the decision
• They're presenting information or a proposal
• They have unique expertise required for the decision
• They'll be responsible for implementing the decision
• They're fulfilling one of the operational meeting roles (Facilitator, Pacer, Decision Catalyst)

Assigning operational roles is crucial. When participants know they're the Facilitator, Pacer, or Decision Catalyst for a meeting, they show up prepared and engaged. They're not tourists—they're contributors with clear responsibilities.

2. Foster Collective Responsibility for Meeting Dynamic

Active participation isn't just about assigned roles. It's about participants taking ownership of the meeting dynamic. For example:

• If the Pacer forgets to call time, another participant can step in: "We have 5 minutes left on this topic"
• If the Facilitator misses that someone hasn't spoken, another participant can create space: "I'd like to hear Maria's perspective on this"
• If the Decision Catalyst doesn't capture a decision, someone else can prompt: "Should we document that as a decision?"

This collective responsibility emerges when participants are involved in outcomes. How? By reading the pre-work and reviewing proposed solutions before the meeting.

In my practice, I've noticed a dramatic difference when participants read pre-work and proposed solutions: the meeting can focus on fine-tuning proposals and answering questions rather than learning firsthand what the problem is. This significantly increases speed and efficiency, and participants become co-creators because they're part of the refinement process, not just passive receivers of information.

3. Regularly Evaluate Meeting Necessity

Build in a regular practice of asking: "Does everyone here need to be in this meeting?" If not, release people from the pressure of being invited.

But here's the nuance most organizations miss: before removing someone who regularly attends without contributing, the leader should discuss individually with that person. Explore what's happening. Why aren't they contributing? Are they unclear about their role? Do they lack confidence? Do they disagree with how the meeting is run? Is there something else going on?

This individual conversation serves two purposes: it provides insight into potential systemic issues, and it demonstrates that participation matters and is expected.

4. Create Collective Agreements

Another powerful approach is to put meeting dynamics on the table for the whole team and agree on working principles together. These collective agreements, when validated and supported by all team members, co-create a team of active participants.

For example, the team might agree:

• Every participant contributes at least once per topic with an idea, question, or perspective
• We hold each other accountable for reading pre-work
• We call out when we're discussing instead of deciding
• We support whoever is facilitating by managing our own participation

When these agreements are co-created rather than imposed, they become part of team culture. (I'll develop this topic of agreeing on ways of working in a future edition of The Pink Elephant Papers.)

Implementation steps

• Apply strict criteria for meeting attendance: why is each person needed?
• Assign operational roles (Facilitator, Pacer, Decision Catalyst) to participants
• Require pre-reading and proposal review before meetings
• Structure meetings to refine proposals, not to introduce problems
• Have individual conversations with non-contributors before removing them
• Create collective agreements about participation expectations
• Regularly evaluate: "Is everyone here needed? Are we all contributing?"
• Celebrate active participation and call out tourist behavior respectfully

Conclusion: The Pink Elephant Is Now on the Table

These five mistakes—meetings for anything, manager-led meetings, no agendas or clear roles, recording everything, and tourist attendees—have been the pink elephant in countless organizations. Everyone sees them. Few name them. Even fewer address them systematically.

But as I've shown in this inaugural edition of The Pink Elephant Papers, these issues are fixable. More importantly, fixing them transforms more than just meeting efficiency—it strengthens organizational culture, builds strategic capacity, and develops leadership throughout the team.

In volatile times, organizations cannot afford dysfunctional meeting dynamics. The teams that thrive respond to chaos with disciplined focus, clear processes, and effective decision-making. This capacity begins in the executive team's meeting room and cascades throughout the organization.

Teams that implement even two or three of these solutions report dramatic improvements. Meetings become shorter, more focused, and more energizing. Decision-making accelerates. Engagement increases. And organizational culture shifts toward clarity, accountability, and strategic focus.

For CEOs and senior leaders: Your meeting dynamics reveal your organizational culture. What do your meetings say about how your organization thinks, decides, and acts?

For HR professionals: Your role in supporting leadership development should include helping leaders transform meeting dynamics. This is where culture is built, one meeting at a time.

The question now is: Which solution will you implement first?

And perhaps more importantly: What other pink elephants are you ready to name?