Organizations are complex adaptive systems with lots going on that you can't directly control. So are communities. And families.

Which is why many of us grew up with elders who sighed often while muttering the serenity prayer under their breath. My favorite variation:

What goes on in meetings reflects organizational complexities, and meetings can feel pretty darn complex themselves. Many leaders conclude that complex = things I cannot remedy, making the search for a better meeting culture futile. So they "never mind it".

At many levels, they are right to do so. You, as an individual leader, can't control how other people lead meetings, the circumstances that determine what you'll need to meet about, or other people's behavior.

So, a lot of what contributes to a meeting culture lies outside of anyone's control, and if we're lucky, it all goes well. The question then is, how can we put our fingers on the scale to tip the odds in our favor?

That's the question behind the last 15+ years of our work at Lucid Teams. It turns out, leaders have control over a whole range of design decisions that strongly influence how meeting culture emerges.

There are decisions to be made by every level of leadership, from the most senior executives on through to whoever happens to be presenting to your group right now, in this moment. Groups that enjoy the most enviable meeting cultures have taken responsibility for these decisions and strive to make coherent choices at all levels.

This article provides an orientation to the range of these design decisions. Then, in future articles, we'll look more closely at the design patterns (or common sets of useful choices) people use at each layer.

I think of this as...

Ecosystem → Meeting Flows → Meetings → Interactions

The Meeting Culture Design Stack describes four interconnected layers of design decisions that shape how an organization meets.

The stack helps us identify the design decisions available to us, where they happen, how they influence one another, and who is positioned to make them.

It focuses on the design choices used to create meeting culture: the concrete arrangements that help organizations put their values into practice and achieve their goals. Those aspirations provide direction; the stack shows what we can design to pursue them.

What shapes how we meet across the organization?

Ecosystem design establishes the infrastructure, constraints, and expectations within which meetings happen.

Some choices are practical: which technology to use, what meeting spaces are available, or whether meetings can be scheduled on Fridays.

Others establish guidelines intended to shape behavior, e.g., decide transparently, connection before content, or my favorite, all meetings are optional.

These choices establish organization-wide defaults and boundaries for the layers below.

How do meetings connect to accomplish a larger body of work?

Meeting flows organize meetings and related activities in support of a workflow. That workflow may be ongoing, such as quarterly planning or sales management, or time-bounded, such as a strategic planning project.

Design decisions include which meetings are needed, what types they should be, how they’re sequenced, who participates, and how information, decisions, and work move between them.

Flows can include recurring cycles, parallel activities, feedback loops, and asynchronous work.

A well-designed flow establishes defaults for many of the meetings and interactions within it.

How should we structure this particular gathering?

Meeting design determines a meeting’s purpose, participants, timing, preparation, agenda, roles, and expected outputs.

Some of these choices may already be established by the meeting flow. Others remain with the meeting organizer or facilitator, who can adapt the meeting to its immediate purpose and circumstances.

What should people do together in the moment?

Interaction design determines how participants engage with one another and the work during a meeting.

Choices include structured rounds, reflection, brainstorming, dialogue, prioritization, and decision-making techniques.

Some interactions are prescribed in advance. Others are selected or adapted in the moment by meeting leaders, facilitators, or participants.

The stack is represented as a nested topography because decisions at the outer layers shape the design options available at the layers within.

An organization-wide guideline may say that teams should make time for connection in meetings. A meeting flow accounts for that expectation when establishing meeting patterns. A meeting organizer reserves connection time appropriate to the group and occasion, and the meeting host chooses a specific check-in activity.

At the ecosystem layer, you can prescribe rigid rules (like, we only use Microsoft Teams here) or establish a guideline without dictating every detail. When people understand what a guideline is meant to achieve, they can adapt how they apply it. A team that already connects regularly may move straight into the work during its daily huddle. A newly formed committee may need 20 minutes to get acquainted before tackling its agenda. Both are making time for connection, but varying how they connect based on their group's needs.

Experience also informs changes to the broader design, rippling from what happens during a meeting outward. If a default repeatedly gets in the way, the people encountering that friction can help identify what needs to change.

This reveals an important design principle:

Effective defaults reduce friction by constraining the number of decisions people must make.

When a useful choice can be established in an outer layer, it no longer needs to be reconsidered independently for every instance. So, while we know we have no ultimate control over how people behave in meetings, in practice, people mostly go with whatever is easiest that helps them get on with their day.

Good upstream design can reduce cognitive load, eliminate unnecessary design ambiguity, and make effective practices easier to sustain. The challenge is to establish good defaults at the highest appropriate level while preserving the flexibility needed for different contexts.

The four layers describe different design choices, each with its own scope and implications.

The people positioned to make these decisions often differ. Four questions help identify where a change can happen and who should be involved.

Changing an organization-wide meeting policy requires different knowledge, authority, and proximity than redesigning a planning process or choosing an interaction for tomorrow’s meeting. These qualities don’t always reside in the same person.

An executive may have the authority to establish a meeting policy but limited knowledge of its effects on day-to-day work. They're unlikely to know much at all about how a frontline team interacts in their weekly huddle. A facilitator may recognize a problem with the huddle but lack the authority to change the larger process causing it.

These same decisions apply to groups of any size and configuration. In smaller groups, a single person might make all of these decisions. Keep that in mind as you ponder who decides in your world.

Effective meeting culture design requires connecting the people who understand a problem with those who can authorize and implement change. Meetings are a team sport.

The first use of the Meeting Culture Design Stack is to notice how many design decisions are already at play.

The technology you use, the meetings on your calendar, the way decisions get recorded, and who speaks when—all of these shape your experience. Some were chosen deliberately. Others emerged from habit, convenience, or whatever the last person in charge preferred.

Once you recognize these as design choices, you can start asking useful questions. Which choices help us work well together? Which make things harder? Where are we repeatedly asking people to figure something out that we could make easier with a reasonable default?

You don’t need to redesign all four layers to make a difference. Start with the choices you can influence. A useful meeting template, a clear place to document decisions, or a shared expectation about preparation can remove friction from everyone’s day.

Over time, these choices can reinforce one another. Good defaults mean people spend less effort figuring out how to meet and more attention on the work they came together to do. Decent meetings become easy and normal

In the articles that follow, we’ll explore specific choices at each layer, with examples and design patterns you can adapt to your own situation.

Looking for support with your meeting culture? That’s what we do.
We’d love to work with you.