LEADERSHIP COMMUNITY MOBILIZATION & LARGE GATHERINGS

The layer below the top team is where strategy and change most often go to die, or where they are mobilized.

Service 3.Communities and Gatherings.Hero Header.Lanterns in valley.lower contrast.png

The most powerful group you have — and the one you keep wasting

Once the top team has aligned and committed, the strategy still has to reach the people who actually carry it: the layer of leaders below them. This is the connective tissue of the organization — the group that carries strategy down, runs the work across the seams between functions, settles what would otherwise escalate, and turns a bet made at the top into motion on the ground. No amount of alignment in the executive room reaches the organization except through them. They sit closest to the ground truth, and they're where cross-functional execution actually happens or doesn't. It's the highest-leverage group you have — and the most consistently underestimated.

So leaders convene them, and the instinct is right: getting this group together should be the best thing you do all year. But the familiar vehicles all treat the layer as a category to be processed rather than a community to be built. Each is an event, severed from the real work and gone by Monday. The instinct underneath is sound; the execution disappoints, every time.

Underneath the disappointment is one fact these all run aground on: you cannot mobilize a category. A category is people who share a level and a reporting line — a slot on the same chart. Push even an excellent strategy through a group that was never cohered, and what comes out isn't coordinated action. It's a relay of confusion — each leader carrying the message down their own silo, in their own dialect, with no shared language and no collective ownership. And when it stalls, the layer gets blamed as a talent problem — the wrong people, a frozen middle, not enough bench — when the real issue is that they were never given ownership of anything. It's not a talent gap. It's a category sitting where a community needs to be.

A category is a slot on a chart — a community is something you build. Doing so moves strategy, resolves cross-functional friction, and enables change.

Service 3.Communities and Gatherings.Pull Quote 1.paths.darker less contrast.png

How I think about high-impact gatherings and mobilizing a community

A few convictions shape this work in particular. Together, they're the difference between a polished event that evaporates and a gathering that actually mobilizes your leaders — turning it, and the community it can become, into strategy that moves, friction that resolves, and change that holds.

A community is a specific thing — not a warm word. "Community" only means something once you say what it is: a shared identity and purpose the group authored rather than received, real relationships across the functions, and genuine impact from work they do together. Of those, relationship is the one everyone underinvests in because it looks softest, and it carries the most — cross-functional trust is the great compensator, pulling a group through failures of plan and process that would otherwise sink it. Bolster the relationships and things you weren't even working on improve.

A great gathering is a craft — most large ones waste the room. Practically every company convenes its top leaders once or twice a year, at enormous real and opportunity cost, and most of it is a wedding: the executives at the front powering through slides, a keynote speaker booked like a band, and the leaders themselves seated as guests — fed, mildly inspired, waiting for the hallway breaks where the only real conversation happens. You've assembled the entire leadership brain trust of the company in one room and run it one-way. Half of it could have been a recording. Done differently, that same room is the highest-leverage instrument you have. The craft starts before the agenda, with the end in mind — not "what do we need to present?" but "where is the business now, and what has to be true when these people leave?" It reads the room in advance, through real conversations with the leaders who'll be there, so the design meets them where they actually are. It puts the candid conversation in the room rather than in the hallway — these are leaders here together to reflect, own, review, and drive, wrestling with the real content face-to-face, not receiving it. And it activates heads, hearts, and hands: not ninety minutes of one-way edutainment, but case simulations, guided visioning, live issue-resolution, relationship-building, commitment rituals — the modes that turn cognitively accepting a message into "I'm committed, and here's how I get involved." The room stops being an audience and becomes participants in their own mobilization, and the energy of many leaders in one place — a rare and expensive condition — finally produces what a scattered group never could.

Ownership is built into everything. Nothing here holds if the group doesn't own it — so ownership is designed into every part of the work, in a few connected ways:

  • They own reality. The group arrives at the honest picture of where things stand through their own discovery, not because a consultant diagnosed them or the top team pronounced it. People dismiss what they're told and carry what they found.

  • It gets personal. And because they found it themselves, it lands personally — each leader owning what they saw, and their own specific part in the solution. Not an amorphous, royal "we should do better," but a real stake, named in front of peers who will remember.

  • We create it together. The gathering is designed and delivered with a core from the group — usually five to eight leaders — as a real collaboration where each side brings its best. They bring their authenticity, their standing with peers, and their own reasons this matters; I bring the ideas, the frameworks, the design, and the craft of running the room. When one of them co-leads a session, they frame why it matters to them and to the community, and I bring the substance and carry the mechanics — neither of us watching the other work.

  • They own their own mobilization. Often that same delivery core becomes the first nucleus of the follow-through — the group taking responsibility for its own forward motion: shaping how the strategy lands rather than only receiving it, sending real signal back up rather than only taking direction down, and carrying the momentum themselves so it doesn't stall.

A community is a living thing, so it's built over time. The gathering is the catalyst — the boot, or the reboot. But a wedding is a single day, and a community is a marriage. The gathering earns its full return only when it's launched as the start of something sustained, and then genuinely followed through: a lean core who keep things moving between the highs, a two-way channel to the top, enough light structure that a distributed group stays a group. The offsite lights the fire; the follow-through keeps it burning. That's what carries results over the long haul, rather than a good feeling with a two-week half-life.

Build the community by pointing it at the work. Not by building a community and then sending it off to do something useful — but by handing it the live work from the start: the pivot, the reorg, the integration, the cost line. The community forms around real stakes, in the same motion that moves them. That's also why it takes no extra time and isn't an added cost: you're paying for the work you want to do anyway. One motion, two returns. And it sets a single standard that holds for every touch, not just the marquee offsite: every time these leaders come together, they should leave with the community stronger and the company further down the field. Both at once, every time — that's the bar, and it's what separates real work from the vehicles that come up short. The reflexive conference is beautifully produced and forgotten by the flight home. The leadership program credentials people and the system snaps shut behind them. The broadcast cascade sends a deck downward and calls the echo alignment. The engagement survey measures the symptom and moves nothing. Each treats the layer as a category to be processed; none builds anything that lasts.

Typical engagement scenarios

High-Impact Large Gathering Scenarios

  • One high-stakes gathering that has to land. A summit, an all-hands, a kickoff, an integration launch — fifty to five hundred leaders, and a single convening that's simply too important to wing, where the design and the room have to be right the first time.

  • A conference no one remembers. You run the annual leadership gathering, at real cost, and it lands like a wedding — beautifully produced, mildly inspiring, forgotten by the flight home. You know the room holds more than that, and you want it to actually do something.

Next Level Community-Building Scenarios

  • A strategy that has to reach past the top team. You've made the pivot, the reorg, the big bet — and now it has to live in the layer below you, the one that actually carries it into the company. Right now that layer is a category, not a community, and the strategy is dying on the way down.

  • A next-level leadership group that operates as silos. The layer below your team is capable individually but disconnected — each leader running their own function well, no real relationships or trust across the seams, no shared ownership of the whole. The work in front of you needs them connected, not just competent in their lanes.

  • A change that keeps stalling in the middle. Escalations that should resolve two levels down keep landing on your desk. Cross-functional work grinds in the seams. The layer gets blamed as a "frozen middle" when it was never actually built into a community that could carry the weight.

  • A community that started and went quiet. You've done a great offsite before — real energy, real connection — and then it faded by the next quarter. You want the version that's built to last, with the follow-through that keeps it alive.

Present to the room and they nod. Put the room to work as an engaged community and they commit.

Service 3.Communities and Gatherings.Pull Quote 2.golden currents.png

What changes

The strategy that used to die on the way down actually moves. The layer below your team stops being an audience waiting to be told and becomes a community that owns the work — carrying the pivot into the organization, resolving across the seams what used to escalate to you, and turning a bet made at the top into coordinated motion on the ground. The escalations that landed on your desk start resolving between the people themselves. The cross-functional friction that used to grind quietly starts to clear.

And it holds, because the group built it. What began at a single gathering becomes something that runs between the highs — a community that carries its own momentum, sends real signal back up, and reaches for the next hard thing without waiting to be pushed. The most powerful group you have stops being the one you keep wasting.

The most powerful group you have.
It starts with one gathering.