If you happen to facilitate (animate) a research or design workshop, no doubt you have more or less sharp answers to these questions that you are sometimes asked: “why do we do it like that? », « why don't we do that? », « why do we have to draw? ".
In order to privilege the “how” to the “why”, it is necessary to answer with the right arguments.
Here are 10 principles from our feedback and the literature on the subject. Principles that are often known but that are always useful to remember.
State precisely the objective and expectations of the workshop
Because, and it's obvious, everything depends on the desired objective: Empathy map, UX story, prioritization grid... Where the questions asked will necessarily guide the reflection, vague goals and instructions are all factors of dispersion and failure (When it's blurry… there's a wolf!)
Break the ice
Because even if everyone knows each other, and this is not always true, personal positions, enmities, the constraints of taking initiative and speaking up, shyness, are potential brakes on personal expression . There are many icebreaker games.
Coffee-croissants
Because in addition to contributing to breaking the ice, this modest donation can call for a counter-donation which would be an increased investment in the workshop to come or in the next one... and if it is not possible before, that is maybe after…
Forget the hierarchies
Because there is no such thing as vertical truth in a research workshop. The N+x sitting at the "top" of the table can have a petrifying effect; and since Rabelais at least, we know how all the members of the herd always run in the same direction (thank you Panurge!), the opposite of what we expect! The hierarchy will legitimately return at the appropriate time.
Write rather than speak
Because we know the importance of speaking order in group dynamics. By calling up reactions, the very principle of interaction between speakers, the first intervention risks orienting the responses and narrowing the field of possibilities.
Draw rather than write
Because the same word does not necessarily have the same meaning for everyone. Hence the misunderstandings and misunderstandings… Okay, it may be ugly, but it's closer to a universal language.
Advocate for quantity
Because it is perhaps in the folds and folds of the most innocuous proposals that decisive elements are hidden. Nothing worse than a priori self-censorship. Quality is for later.
Listen to everyone
Because to ignore participants is to send them back to passivity and to deprive themselves of their activity and their creativity… or even to make enemies of them.
Involve all project stakeholders
Because it is always painful to hear oneself say at the end of the workshop: “It was great! Too bad Richard isn't here, I don't know if he'll agree. Where one suspects too late that without Richard, not much will happen.
Unfold ideas and proposals
Because an idea may only reveal its full potential by unfolding it. Do not forget to request this unfolding with the “and…”, or the “and therefore…”.
Admit your shortcomings
Because appearing as an infallible expert ends up undermining credibility and sterilizes initiative, while admitting (≠ spreading out) one's limits emphasizes the authenticity of reflection and can uninhibit the expression of others.
Here ! No doubt you have your own answers to the questions of methods that you encounter, and no doubt you could add other principles, but since in recent years the approaches have been intended to be more and more user-centered, and more or less tinged by Design Thinking (even if we are still often quite far from the optimum). We must take advantage of all opportunities to involve the user effectively when time is often limited. Avoiding errors that can neutralize a workshop is therefore an objective in itself.
