Workshop
Workshop
What is a workshop?
- A participatory session you build together, not a lecture
- Success depends on defining the deliverable and designing for it, not on the day itself
- Facilitation that prevents any one person from dominating is the key
Introducing a workshop changes the accountability structure of the room. In a lecture the instructor holds the conclusion, and in a meeting the most senior person does, but in a workshop the work of reaching a conclusion passes to the participants. So even the preparation changes. Instead of slides, you need flip-chart paper and sticky notes for the wall, a minute-by-minute schedule, and a single line stating what participants will have in hand when the day ends. If no file remains at the end, it is more accurate to call it a slightly longer meeting than a workshop.
In practice, workshops fall into four types by purpose. A strategy workshop leaves you with priorities and owners; a problem-solving workshop, with root causes and countermeasures; a training workshop, with hands-on outputs and an on-the-job application plan; and a team-building workshop, with an agreed way of working. Design standards are numbers, not gut feeling. Groups of 5 to 6 work best, one facilitator can handle around 30 people, and beyond that you assign a separate lead for each group. Allocate time roughly 6 parts to divergence and 4 to convergence, and share interim outputs with everyone every 90 minutes to check progress. Seminars and conferences are formats for 'listening and asking questions'; a workshop is a format for 'making something and putting it on the wall.' That is the dividing line.
The most common failure in the field is the workshop whose conclusion is already decided. When executives hold the answer and send participants to find it, group presentations become a guessing game, and from the next workshop on, nobody voices a real opinion. It is also a misconception that sticky notes and group assignments alone make a workshop. Without a defined deliverable and decision-making rules, 200 sticky notes on the wall end up as a few photos. Another common mistake with overnight events is pouring the budget into the evening program. Participants may remember the evening, but what stays with the organization is the sentence agreed on during the day and the owner's name written next to it. If you disband without a follow-up check schedule, the event ends with high satisfaction scores and zero execution.
Sungmin JooExpert in diagnostic-based coaching leadership, entrepreneurship education, and design thinking
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum ConsultingThe word comes from the workshop, the place where craftsmen worked with their tools. In the 20th century it broadened in theater and education to mean a participatory session where people build something together. In business, it became a standard collaboration format as organization development (OD) and facilitation techniques spread.
Consider a hypothetical case. Company A, a food manufacturer with 240 employees and annual revenue of about KRW 90 (≈ US$1) billion, had seen flat sales for three years. Every year it held a two-day 'Sales Division Workshop,' but all that was left was group photos and dinner expense reports. This year it redesigned the event as a strategy workshop for the 38 people in the sales division.
- At the kickoff, the head of sales laid down the rule: 'No more dinners that end with no conclusions. We go down with just three tasks.' The HR development team narrowed the issues to 8, based on 38 pre-survey responses and interviews with 6 team leads.
- An HR manager brought in one outside facilitator and split the 38 attendees into six tables. The head of sales scrapped the head table, sat at Table 3 as an ordinary participant, and spoke last.
- The first 3 hours of the afternoon were spent purely on divergence. Each person spent 20 minutes alone writing problems on sticky notes, and the notes were then grouped by team. 'The problem is delivery dates, not price' came up at the same time in 4 of the 6 groups.
- On the morning of day two, an anonymous sticker vote with 3 votes per person cut 17 candidates down to 3. For each task, the owning team lead and deadline were written up on screen, then compiled into a 2-page action plan rather than photos and distributed before everyone left.
- They held an execution kickoff two weeks later and reviewed progress monthly. Within 90 days, 2 of the 3 projects were complete, on-time delivery to key accounts rose from 78% to 91%, and 31 of 38 attendees agreed that 'what we decided in the workshop actually gets done.'