Start with the work the workshop must do
Before writing an invitation list, finish this sentence: “By the end of the workshop, we need to…” A session might need to uncover audience needs, generate visual directions, test early concepts or agree on priorities. Each purpose calls for a different mix of people. A workshop for exploring ideas benefits from varied perspectives; a workshop for selecting a direction needs people who understand the constraints and the decision process.
Define the expected output as well as the topic. “Discuss the brand” is difficult to prepare for or evaluate. “Identify three qualities the new identity must communicate and the examples that support them” gives participants a clear task. It also helps you distinguish people who need to contribute during the session from people who only need to review the result.
Choose for perspective, not just availability
List the perspectives needed to do the work well. For a small creative project, these might include someone who knows the audience, someone who will make the work, someone who will use or maintain it, and someone who understands the budget or approval process. One person may cover more than one perspective, but an important viewpoint should not be assumed to be present simply because a job title sounds relevant.
For example, a workshop on a community arts programme’s visual identity could include a designer, a programme organiser and a person who regularly creates event materials. If the team wants to understand how newcomers encounter the programme, it may also help to hear directly from people with that experience. Invite them to contribute to a specific question rather than asking them to speak for an entire community.
Keep the group small enough for everyone to take part in the planned activities. If the list grows because many people want updates, separate participation from communication: invite essential contributors to the workshop and send others a concise summary afterward. When participation requires preparation, travel or time away from other work, make those expectations clear in advance and consider how to reduce the burden.
Give each person a clear role
A useful role description says what someone will contribute and what they can decide. The facilitator guides the process and makes room for different voices; they do not need to be the subject expert. A project lead explains the brief and keeps the work connected to its purpose. Makers contribute practical knowledge about what can be produced and maintained. Audience representatives or users contribute their own experiences, which the group should treat as insight rather than automatic approval of an idea.
Identify the decision-maker before the session. Will the group choose a direction, make a recommendation, or simply generate material for later review? These are different promises. If someone outside the room will approve the outcome, tell participants who that is and what criteria they will use. Otherwise, a lively exercise can create the mistaken impression that the most popular idea has already been adopted.
One person can hold multiple roles in a small team, but some combinations need care. A project lead who also facilitates may find it hard to challenge their own assumptions while guiding the conversation. They can still run the session, but should state when they are offering an opinion rather than managing the process.
Write an invitation that prepares people to contribute
An effective invitation is a short working brief. Include the workshop question, the intended output, why that person’s perspective matters, the activities they can expect and any preparation needed. State what decisions will and will not be made. If participants will review examples or bring material, explain how those inputs will be used. Avoid requesting extensive preparation unless it is essential to the exercise.
Consider how people will participate, not only whether they can attend. Some may need the agenda or visual materials beforehand; others may contribute more easily through individual notes before group discussion. Building in a quiet first step can also prevent the fastest speakers from setting the direction too early. Ask participants about practical access needs in a way that gives them room to respond privately.
Close the loop after the workshop
Plan the follow-up before the session begins. Assign someone to capture decisions, open questions and the reasoning behind them, rather than trying to preserve every comment. At the end, confirm what the group agreed, what remains unresolved and who owns the next step. If the workshop produced options rather than a final choice, say so plainly.
Share a brief summary with participants while the work is still useful to the project. Show which contributions informed the next step, especially when a suggestion was adapted or set aside. This does not mean promising to use every idea. It means respecting the purpose for which people gave their time and making the path from workshop to creative work understandable.
