Most of what shapes an engagement happens before anyone would call it "the work" — in how it's diagnosed, designed, and led. If you want to see under the hood — how I think about this, and what makes it different from the room full of facilitators and team coaches you could hire instead — this is that. Read it straight through, or jump to what you're curious about:

• Strategy and team are one job — why the business and the human are the same work

• What "facilitation" really means — and why most people do a quarter of it

• Competent humility — expertise without the pretense of having the answer

• Not as dysfunctional as you think — how I see the teams I walk into

• How the work actually runs — before, during, and after the room

Strategy and team are one job

Most people who do this work come from one of two camps. On one side, consultants who can take apart the business problem — the strategy, the operating model, the decision on the table — but treat how the team functions as soft stuff, overhead, someone else's department. On the other, facilitators and coaches who can hold a room beautifully and go quiet the moment the conversation turns to what's actually being decided.

I've spent twenty-five years refusing to pick a side, because in real leadership teams the two were never separate to begin with. A strategy stalls because two people at the table don't trust each other. A team can't get honest because it has never agreed on where the business actually stands. What a group is trying to get done and how it works together are the same job, seen from two sides — and each one blocks the other until both are in the open.

So I work across the whole gradient — the strategy, the operating decisions, and the hard analytical work on one side; the trust and the interpersonal work underneath them on the other. But range is only the price of entry. The real work is reading how the sides fit together for this group: which strand to pull first, and when. Sometimes a team has to settle a business question and feel itself succeed before it can trust itself with the harder personal ones. Sometimes it's the reverse — nothing about the business moves until people have put their cards on the table and built enough trust to be honest. Which way round depends on the team, the culture, the moment, and reading it is most of the craft.

Done well, the sides compound — the business gets clearer because the team got honest, the team gets stronger because it did real work on something that mattered. That's the point of refusing the choice: a team that can tell each other the truth and decide together and have it hold; a strategy a group actually believes and will carry on Monday; leaders who grow into what the moment asks, in the doing. Neither camp, working one side alone, can produce that.

What "facilitation" really means

"Facilitation" is a word that hides more than it reveals. For one person it means mediation — the delicate work of leading a sensitive conversation. For another it's traffic control: keeping a discussion on time, on topic, everyone in it, agreements captured. For another it's guiding a group through a way of thinking rather than handing them the answer. For another it's leadership development, done live. These are genuinely different crafts, and most practitioners are good at one of them and call it "facilitation."

The engagement is all of them at once. In the same afternoon the work might move from surfacing what two people have been avoiding, to holding a hard decision to its deadline, to walking a group through a way of seeing their situation, to helping a leader grow into the version of themselves the moment is asking for. Reading which the room needs, minute to minute, and moving cleanly between them — that's the part that took twenty-five years, and it's most of what you're actually buying.

Competent Humility

I was trained to be the person with the answer. Most of what I've learned since has been the opposite discipline: how to walk in without the answer, and trust that the people who live inside the company know things about it I never will. That's not modesty. Whatever I know about strategy and how teams work, they know their business, their history, and each other in ways no outsider can. The work is built to draw that out, not to override it.

It's the old parable of the blind men and the elephant, and the part everyone forgets is that the consultant is one of the blind men too. Each leader has a hand on a different part of the animal, each read accurate and partial. The know-it-all consultant doesn't escape that — they just add one more partial view, with more presumed authority attached, which makes it more distorting, not less. I'd rather be curious like everyone else: introduce my part deftly, as one more hand on the elephant, and put most of my skill into stirring the whole thing into view — where the group can finally see the animal none of them could see alone. That's also why there's no silver bullet for this work — not a book, not a program, not a guru with a single framework. One of my favorite lines is Hamlet's: there are more things in heaven and earth than are dreamt of in your philosophy. I take it as a working rule.

So I carry a deep toolkit and I'm a devotee of none of it. The design comes after the diagnostic — built for this team, this decision, this moment — never pulled off a shelf and imposed. What I bring is real expertise and no pretense of having all the answers, and I've come to believe those two things need each other: the expertise to know what might be going on and what could help, the humility to stay genuinely curious about a group I'm still learning. The breakthroughs come from what a team discovers in dialogue with itself. My job is to make that dialogue possible — and to know enough to recognize it when it arrives.