How to run a workshop with senior executives

A workshop with senior executives succeeds or fails before anyone enters the room. Interview each executive beforehand, agree the one decision the session must produce, send a short pre-read that states the answer first, collect everyone's view in silence before the discussion, and close by reading the decision, the owner and the date aloud. Executives do not need games. They need a reason to be there, a structure that lets them disagree safely, and an outcome they can defend afterwards.

Why executive workshops fail differently

A team workshop usually fails because nobody owns the result. An executive workshop fails for the opposite reason: everyone in the room owns something, and each person is protecting it. Three patterns appear again and again.

• The room defers to the most senior voice. Once the chief executive speaks, the range of opinion narrows. People do not lie; they simply stop offering the view that differs.
• The real conversation has already happened. Positions were settled in corridors and side meetings. The workshop becomes a performance of a decision taken elsewhere, or a stage for a fight that should have been resolved in private.
• Time is the scarcest thing. Executives arrive late, leave early and step out for calls. A design that needs everyone present for four unbroken hours will break.

Good facilitation for this audience is therefore less about energising the room and more about engineering it: what happens before, the order in which people speak, and how the outcome is written down.

How to run it, step by step

1. Interview every executive before the day. Fifteen to twenty minutes each, one to one. Ask three questions: what would make this session worth your time, what worries you about the topic, and what do you think others in the room do not yet see. You will learn where the disagreements are, which ones are about facts and which are about territory. Map what you hear on a stakeholder map so you can plan who needs to hear what, and in what order.

2. Agree the decision with the sponsor, and write it as a question. Not "discuss the digital strategy" but "Which two of the five proposed initiatives do we fund in the first half?" If the sponsor cannot name the decision, the session is not ready. Say so. A postponed workshop costs less than a wasted one.

3. Send a short pre-read that puts the answer first. Two pages at most. Lead with the recommendation or the choice to be made, then the reasons, then the evidence. This is Barbara Minto's pyramid principle, and it suits executives because they can stop reading at any level and still know the point. Do not assume it will be read. Start the session with ten minutes of silent reading; Amazon is known for opening meetings this way with its written memos, and it works anywhere.

4. Collect views in silence before anyone speaks. Ask each executive to write their position, their main concern and one question on cards or in a shared document, individually, before the discussion opens. Then read them out or display them together, without names if the topic is sensitive. This removes the anchoring effect of the first senior voice. If the chief executive is willing, ask them to speak last; most good leaders agree once they understand why. The mechanics are in our piece on silent-first ideation.

5. Let a method do the challenging. Executives accept challenge from a structure more readily than from a facilitator. A premortem, Gary Klein's technique of imagining the decision has already failed and asking why, invites the hard questions without anyone having to attack a colleague's proposal. Assumption mapping does the same for the beliefs a plan rests on. When choosing between options, a weighted decision matrix with criteria agreed before the options are scored stops the loudest argument from winning by default.

6. Hold time, cut scope. Plan in blocks of 45 to 60 minutes with a clear output for each. When a block runs over, do not extend the day; ask the sponsor which item to drop or move. Keep a visible "parking" list for issues that are real but not for today, and promise, with an owner, how each will be handled.

7. Close by reading the decision aloud. In the last fifteen minutes, write the decision in one sentence, the owner, the first action and the date by which it will happen. Read it aloud and ask each executive to confirm or object, by name. A silent nod in an executive room is not agreement. Send the written record within 24 hours, and send it from the sponsor, not the facilitator.

Handling the moments that go wrong

The executive who dominates. Do not confront them in the room. Use the structure: "Let's hear from everyone on this before we go deeper," then go around the table. If it persists, use a break to speak with them privately, as a peer: "Your view is landing so strongly that others are holding back. Can you help me draw them out?"

The phone and the walk-out. Agree a phone norm with the sponsor in advance and have the sponsor state it, not you. Build two natural breaks into each half day so calls happen then, not in the middle of a decision.

The late arrival who reopens a settled point. Give them a one-minute summary of what was agreed and why, then ask whether they have new information. If not, the point stays closed. If yes, park it with a time to return to it.

The open disagreement between two executives. Name it plainly and neutrally: "There are two positions here." Write both on the wall in their own words and ask each to state what evidence would change their mind. Disagreement about facts can often be settled with a test. Disagreement about territory belongs to the sponsor, usually outside the room.

Illustrative example

Illustrative. A mid-sized insurance group in Europe had a leadership team of eight and three competing proposals for where to invest in customer service. Earlier meetings had gone in circles. The facilitator held eight short interviews and found that two directors agreed on the problem but disagreed on who would run the solution. The sponsor framed the decision as "Which one proposal do we fund for a six-month pilot, and who owns it?"

The pre-read was a page and a half, read silently at the start. Each director wrote a position card before any discussion. Five of eight cards favoured the same proposal, which surprised the room; in open debate it had sounded like a minority view. A twenty-minute premortem on that proposal surfaced a data-sharing risk nobody had raised. The team agreed the pilot, named an owner, and set a decision point at month three. The session finished ten minutes early.

Do's and don'ts

Do

• Interview every executive before the day, even briefly.
• Frame the session around one written decision question.
• Collect individual views in silence before open discussion.
• Agree criteria before scoring options.
• Read the decision, owner and date aloud at the end, and send the record within a day.

Don't

• Use icebreakers or games that feel childish to this audience. A sharp opening question works better.
• Present for more than ten minutes at a stretch. Executives came to decide, not to listen.
• Let the most senior person speak first on a contested topic.
• Extend the session when time runs out. Cut scope instead.
• Leave without a named owner. "The team will look into it" means nothing will happen.

Questions people ask

How long should an executive workshop be? Shorter than you think. Half a day with one clear decision is better than a full day with five. If the topic truly needs more, split it into two sessions a week apart, so that information gathered in between can inform the second.

Should the facilitator be internal or external? External facilitators find it easier to hold time and challenge senior people because they are not in the reporting line. Internal facilitators know the history. If you use an internal facilitator, make sure the sponsor visibly gives them authority over the process at the start.

What if the chief executive has already decided? Ask them in the pre-interview. If the decision is made, the workshop should be about how to deliver it, not whether. Pretending to consult on a closed decision damages trust more than announcing it openly.

Where to go next

For the full approach to sessions that end in decisions, read how to run a workshop that ends in decisions. If your organisation is strongly hierarchical, innovation in hierarchical cultures goes further on working with seniority. The method guides most useful for this audience are the premortem, assumption mapping, the weighted decision matrix and the stakeholder map.