When the Client Doesn't Know What They Want from a Workshop

"We just need to get everyone in a room."

"Something's off with the team — I'm not sure what."

"Can you run a strategy day? It needs to feel energising."

These are real briefs. Facilitators receive them constantly. They're not laziness on the client's part. They're a signal that something is wrong and the client doesn't yet have the language — or the clarity — to name what.

Working with unclear briefs is one of the most underrated facilitation skills. It requires patience, structured inquiry, and the confidence to slow down when every commercial instinct says to start designing. The client who says "can you sort something out?" is often in the most acute need — and the most at risk of an expensive session that changes nothing.

Why Briefs Are Often Unclear

Understanding why briefs are unclear helps you respond to them more effectively.

The problem hasn't been diagnosed. The client knows something is wrong — productivity is down, decisions are slow, the team feels fragmented — but they haven't identified the root cause. They're asking for a workshop to solve a problem they haven't yet named. This is common and workable. Scoping becomes a diagnostic process.

The client is avoiding a difficult conversation. Sometimes the stated brief is a displacement activity. The real issue — a leadership team that can't agree on direction, a founding team in conflict, a manager who's lost the room — is too uncomfortable to name directly. The workshop is a way of "doing something" without confronting the actual problem. This is riskier. A workshop won't fix a conversation that needs to happen between two people.

Multiple stakeholders have different agendas. The brief is unclear because it's been assembled from several people who want different things from the session. Nobody has reconciled them. You've been handed an incoherent composite and asked to design for it.

The client is new to working with facilitators. They don't know what a workshop brief should contain, so they haven't written one. They know what they want but haven't been asked the right questions to surface it.

Each of these requires a different response. Your job in the scoping conversation is to figure out which one you're dealing with.

The Diagnostic Scoping Approach

When a brief is vague, the scoping conversation becomes a diagnostic conversation. You're not asking "what do you want the workshop to achieve?" You're asking questions that help the client discover what they actually need.

Start with Symptoms

Ask what the client is observing. Not what they think is causing it — what they're seeing, hearing, experiencing.

• "What's making you feel like something needs to change?"
• "What are you noticing about how the team is working together?"
• "When did this start to feel like a problem?"
• "Can you give me a specific example of what's not working?"

Symptoms are concrete. They're also easier to talk about than causes or solutions, which reduces the client's anxiety and opens up more honest conversation.

Move to Impact

Once you have symptoms, ask about impact. Why does this matter?

• "What's the effect of this on your team's work?"
• "What's not getting done because of this?"
• "What would you lose if this continued for another six months?"

Impact questions force specificity and raise the stakes in a productive way. They also help you understand what a successful workshop needs to actually change.

Ask About Attempts

What's been tried before? This tells you what's already been ruled out and often reveals more about the real problem.

• "Has anything been tried to address this? What happened?"
• "Have you spoken to people on the team about this directly?"
• "Is there a common understanding of what the problem is, or do people see it differently?"

A client who has already tried multiple solutions without success is often dealing with a more entrenched systemic issue. A client who hasn't tried to address the problem directly yet may need a simpler intervention than a full-day workshop.

Hypothesise Out Loud

After gathering enough symptoms, move to tentative hypotheses. This is a facilitation move — you're inviting the client to test a diagnosis, not accepting it.

"Based on what you've described, I'm wondering if the core issue is X. Does that resonate?"

The client's response to this hypothesis is often more revealing than their answers to direct questions. If they immediately confirm it with relief, you've probably hit the mark. If they push back or nuance it, you've learned something important. Either way, you're making progress.

When the Brief Is Contradictory

Some briefs aren't vague — they're contradictory. The sponsor wants a safe space for honest feedback AND they want a positive, energising session. They want the team to generate ideas freely AND they've already decided what to do. They want to "get everyone aligned" AND three people in the group have fundamentally different views that have never been directly addressed.

Contradictory briefs signal that the sponsor hasn't thought through the constraints. Or that multiple sponsors gave you conflicting instructions. Or that the sponsor knows what they want but suspects a good facilitator will give it to them anyway.

Your job is to name the contradiction explicitly, without judgment.

"I want to check my understanding — you've mentioned wanting the session to feel energising and positive, and you've also mentioned that there are some difficult conversations the team hasn't had. Those goals can coexist, but they require different designs. Which is the priority if we have to choose?"

Naming the contradiction often produces the most useful part of the scoping conversation. The client is forced to clarify, which clarifies the brief.

When the Real Issue Is Not a Workshop Problem

Some situations shouldn't be addressed through a workshop at all. A well-run workshop is a powerful tool, but it's not the right tool for every problem.

Signs that a workshop won't help:

The problem is between two specific people. If the real issue is a broken relationship between a founder and their CTO, or a manager and a senior team member, a group workshop doesn't fix it — it usually papers over it at best, surfaces it explosively at worst.

A decision has already been made. If the sponsor needs to communicate a decision rather than make one, a workshop is the wrong format. An announcement with a well-designed Q&A is more honest and more effective.

People are not safe to speak. If the organisational culture punishes honesty, participants will not speak frankly in a workshop regardless of how safe the facilitator tries to make the space. Psychological safety is a precondition for workshop effectiveness, not something facilitation can manufacture.

The sponsor wants validation, not exploration. If the sponsor's real need is confirmation that their preferred answer is correct, a workshop that genuinely explores the question will produce outcomes they don't want. Better to help them design a communication process than a facilitated inquiry.

When you identify that a workshop isn't the right intervention, say so. This is a professional obligation and, paradoxically, often builds more trust than accepting the brief and running the session anyway. A sponsor who discovers six months later that a workshop was the wrong tool will remember that you recommended it.

Naming What You're Seeing

When the brief is unclear and the diagnostic questions have done their work, name what you've found — clearly, directly, and without softening it to the point of uselessness.

"Based on our conversation, I think the core issue is [X], and I'm concerned that the workshop as originally described wouldn't address it. Here's what I'd suggest instead."

This kind of directness can feel risky commercially. It often isn't. Clients who are told clearly what they actually need — even when it's different from what they asked for — usually respond with relief. Someone has finally named the thing they couldn't.

And if the client disagrees, you've started a more honest conversation than you would have had by accepting the unclear brief and designing to it.

Moving Forward with an Unclear Brief

Sometimes, despite good scoping, the brief remains fuzzy. The client genuinely doesn't know what they need. In that case, design a workshop that is explicitly diagnostic — a session whose purpose is to surface the real problem, not solve it.

Frame it clearly: "I'd suggest we start with a half-day scoping session. The goal isn't to produce solutions — it's to create a shared diagnosis of what's going on. From that, we'll know what the next step needs to be."

A diagnostic session is a legitimate workshop design. It's often the right starting point when the client can't articulate the problem yet. What it isn't is a cover for proceeding without a clear purpose — it has its own specific purpose, which is clarity itself.

Unclear briefs are an invitation to do better contracting. The work is harder, the conversations are more demanding, and the design takes longer. The result is a workshop built on real understanding rather than polite assumption — and that difference shows up in the room.