I still remember my first stakeholder workshop — mostly because I walked in thinking I needed to talk, and walked out realizing I needed to listen.
Like many business analysts early in their careers, I had studied the frameworks — I had even just achieved a requirements engineering certification. I understood the project goals — mostly. I had my agenda structured down to the minute, preparatory diagrams, and a confidence that was mostly bluff. 15 minutes in, I was already off-script. The conversation had gone sideways, one of the eight attendees was obviously frustrated, and I was rapidly losing control of the room.
What I lacked was the real-world experience that tells you: facilitation isn't about controlling the room — it's about guiding discovery.
Here's what I wish someone had told me before I ever stepped into that room.
1. Your job is to uncover, not convince
Early on, I thought the BA's role in a workshop was to guide the group toward the right answers. The problem is, you rarely know what the right answers are until you listen — really listen.
Stakeholder workshops aren't about showing what you know. They're about helping people articulate what they know, what they think they know, and what they assume to be true.
Your job is to surface it all, without judgment.
2. The loudest person in the room isn't always the key stakeholder
There's always someone who dominates the conversation. They speak first, most, and with confidence. It's tempting to treat them as the most important opinion.
But influence and insight don't always come with volume.
Look out for: • The quiet stakeholder who waits until everyone else is done before speaking. • The stakeholder who contradicts the dominant voice, gently. • The person in the back, scribbling notes — they often know more than they say.
A skilled BA knows how to read the room and redistribute the airtime.
One technique I've found helpful is to pause before moving to the next topic and ask, "Have we heard from everyone on this?" It signals that input is still welcome, without calling anyone out. Alternatively — or even additionally — I would direct a follow-up question to someone who's still been quiet — especially if their role suggests they have insights others might overlook (like Legal, Operations, or Support).
3. Not all conflict is bad
The first time two stakeholders disagreed openly in a workshop, I kind of panicked. I thought I had failed to prepare or align expectations. But I quickly learned that conflict is not a failure — misalignment is.
Healthy disagreement can reveal: • Conflicting business goals • Hidden constraints • Process pain points
Your role isn't to stop the tension. It's to manage it productively, and make sure it leads to clarity — not chaos. For example, one thing that has repeatedly helped me is naming the tension, without escalating it. I may say something in the lines of "It sounds like there are two different approaches here. Let's entertain both before we decide how to move forward." This slight shift helps people move from defensiveness to problem-solving.
4. A great agenda is a safety net, not a cage
My early agendas were detailed to the minute. I thought precision meant professionalism.
What I didn't realize is that workshops have a life of their own. Questions emerge. Unexpected problems surface. Time evaporates.
The solution isn't to abandon structure — it's to build in flexibility: • Prioritize the top 3 outcomes • Have backup activities if something stalls • Allow time for synthesis, not just input
The agenda is your guide. But your attention should always be on the room, not the clock.
I remember that I once ran a workshop where a heated discussion around one decision point took up more than half the session. My original agenda had us covering five different areas, but I realized mid-way that reaching alignment on just that one topic was far more valuable than time-boxing the discussion and cutting off contributions. The workshop didn't "stay on schedule," but it absolutely delivered value.
5. Silence isn't awkward — it's information
In my first workshop, every silence felt like a failure. I filled them with filler words, repeated questions, and awkward transitions.
Now, I know better.
Silence means: • People are thinking • Someone is weighing how honest they can be • You've asked a good question
Let it breathe. Give it space. You might be surprised what emerges after the pause.
6. The workshop doesn't end when it ends
The real value of a stakeholder workshop often appears after the session.
People reflect. They send clarifying emails. They open up in 1:1s. They share insights they weren't ready to say aloud in the room.
As a BA, you need to: • Follow up with a clear, accurate summary • Invite further thoughts • Keep the momentum going
A workshop is a starting point — not a checkbox.
After the session ends, I always send out a summary within 24–48 hours. I include key agreements, open questions, and next steps. I invite additional input with a simple prompt like: "Please let me know of any comments", or "Please, if you have any additional points, let me know." These follow-ups often lead to clarifications or reveal new concerns — especially from people who didn't feel comfortable speaking up live.
Final Thought
If you're prepping for your first (or fifth) stakeholder workshop, remember this: You're not there to have all the answers. You're there to ask the right questions, create the right space, and make the right sense of what emerges.
Looking back, I realize now that every workshop is a chance to learn how people think, not just what they want. You're not there to perform. You're there to listen deeply, ask wisely, and help the right ideas emerge. That's what turns a workshop from a meeting into a moment of progress.
Dive in, practice, reflect, and always stay humble, knowing you'll never stop learning how to do it better.
Christonikos Zonafos is a business analyst and project manager, focused on helping people and teams make better decisions through clarity and collaboration.