Most team workshops are well-intentioned and largely forgotten. People leave feeling good, the sticky notes go on the wall, and by the following Thursday the team is back to the same patterns. The problem is usually not the people or the facilitator. It is the design. A workshop that produces something lasting is built differently from the start.
Start with the real question, not the presenting one ¶
The most common mistake in workshop design is starting with the question the team thinks they need to answer rather than the question underneath it. A team that says they need to align on strategy often actually needs to surface a disagreement that has been politely avoided for six months. A team that says they need a better process often needs to talk about a relationship that is not working. The intake conversation, done well, surfaces the real question before the day begins.
The intake conversation matters more than the agenda ¶
Before any workshop we run, Mara speaks with two or three participants individually. Not to gather information for a presentation, but to understand what people are actually thinking and what they are not saying in the group. Those conversations shape the design of the day more than any framework or template. The agenda is built around what the intake reveals, not the other way around.
Design for one decision, not ten ¶
A workshop that tries to resolve ten things resolves none of them. The most productive workshops are built around one decision or one question, with enough time to actually get to the bottom of it. If you have ten things to resolve, run three workshops. The temptation to pack the agenda is understandable but it is the single most reliable way to produce a day that feels busy and changes nothing.
The output has to be specific enough to act on ¶
A workshop that ends with 'we are aligned on our values' has not produced anything actionable. A workshop that ends with 'we are changing the project intake process to include a 30-minute scoping call before any brief is accepted, starting next Monday' has. The difference is specificity. Every workshop should end with at least one decision that is specific enough that someone could act on it the following morning.
What to do in the week after ¶
The week after a workshop is where the work either takes root or dissolves. The facilitator's job does not end when the day ends. A short written summary of what was decided, sent within 24 hours, gives the team something to refer back to. A brief check-in two weeks later, even just a short email, catches the things that have already started to slip and gives the team a chance to course-correct before the old patterns fully reassert themselves.
FlowShiftWaveMind runs half-day and full-day workshops for teams of four to twelve people, in person or remotely. If you are thinking about a workshop for your team this autumn, the free intro call is a good place to start the conversation.