How to Run a Process Workshop for Your Team
A process workshop is a structured, facilitated session in which the people who do the work map how a process runs today, identify what gets in the way, and agree how it should work in future. Designing or improving a process is not a one-person task; it needs the insight of the people who live it every day. Run well, a process workshop builds shared understanding, surfaces hidden problems and creates ownership of the improvements.
Why run a process workshop?
Process workshops align stakeholders around how work actually flows, expose inefficiencies and design improvements together. They make the process visible, create ownership and uncover problems that never surface in day-to-day work. They are also one of the best ways to bridge the gaps between technical teams, security, operations and the wider business.
Preparation is key
Define clear objectives
Decide exactly which process you are addressing and why. Are you designing a new workflow, improving an existing one, or looking for automation opportunities? A specific goal keeps the discussion focused and the outcome measurable.
Choose the right participants
Invite people who perform, manage or depend on the process, from different functions, so you see it end to end. Six to twelve people usually balances breadth of view with a manageable discussion.
Gather information in advance
Collect existing documentation, volumes, timings and feedback beforehand. A factual baseline lets participants prepare and keeps the session grounded in evidence rather than opinion.
Facilitating the workshop
Set the scene
- Open with introductions and restate the purpose.
- Agree ground rules: respect, openness and constructive challenge.
- Walk through the agenda and expected outputs.
Map the current process
Use a whiteboard, sticky notes or a digital mapping tool to lay out the current process step by step. Ask participants to describe each step, who does it and where it goes wrong. A shared visual quickly reveals handoffs, delays and workarounds. Our process mapping guide covers the mapping techniques.
Identify problems and opportunities
- Invite people to name the frustrations and barriers they meet.
- Record inefficiencies, duplication, delays and risks.
- Note any security, compliance or control concerns.
Redesign together
Sketch the improved process as a group. Consider simplification first, then automation, clear roles, checkpoints and escalation routes. Discuss trade-offs and constraints openly. Our article on improving processes before automating them explains why the order matters.
Agree next steps
- Assign actions with owners and dates.
- Plan follow-up reviews to check implementation and keep improving.
After the workshop
Circulate the notes and updated process maps promptly and keep them accessible. Track the actions, stay open to feedback and treat the process as something that will keep evolving.
Facilitation tips
- Timebox discussions: allocate time per agenda item to avoid tangents.
- Use the right tools: digital whiteboards help remote and hybrid teams take part equally.
- Stay neutral: draw out views from everyone rather than steering towards your own.
- Focus on outcomes: push for decisions and actions rather than open-ended debate.
- Use plain language: avoid jargon so everyone can contribute.
- Manage the room: make space for quieter voices and keep dominant voices in check.
For larger or cross-functional processes, an independent facilitator helps keep the discussion balanced. Intology's process mapping services run these workshops as part of wider improvement and transformation work.
Frequently asked questions
What is a process workshop?
A facilitated session where the people involved in a process map how it works today, identify problems and agree an improved future process with clear actions.
Who should attend a process workshop?
People who perform, manage or depend on the process, drawn from each function it touches, typically six to twelve people, plus a facilitator.
What should a process improvement workshop agenda include?
Objectives and ground rules, mapping the current process, identifying problems and their causes, designing the future process, and agreeing actions, owners and follow-up.
How long should a process workshop last?
Half a day to a full day for a single process is typical. Complex end-to-end processes may need a series of shorter sessions.