# UX/UI workshops: bringing stakeholders along, from framing to delivery

> UX/UI workshops with stakeholders: who to invite, the script of a 90-minute workshop, six workshops from kickoff to delivery, and what happens in between.

- URL: https://vladispala.fr/en/blog/ux-ui-workshops-with-stakeholders/
- Author: Vladimir Spalaikovitch (Vladispala), Senior UX/UI Designer, Product Designer and Digital Art Director, Paris
- Updated: 2026-11-15
- Version française: https://vladispala.fr/blog/ateliers-ux-ui-parties-prenantes/

## Key facts

A good UX/UI workshop produces a decision, not minutes. It brings the right people together (decision maker, business, tech, support, users) in a short, scripted format: open, diverge, converge, decide, commit. Six workshops mark out a project, from kickoff to handoff, and asynchronous exchanges keep the thread between sessions.


A good UX/UI workshop ends with a decision, not with minutes. It brings the right people together in a short, scripted format: open, diverge, converge, decide, commit. Six workshops mark out a project, from kickoff to delivery, and written exchanges keep the thread between sessions.

## Why workshops rather than meetings

A meeting moves information around. A workshop gets people working together on something visible: a journey, a wireframe, a mockup. The difference shows at the end. After a meeting, everyone leaves with their own version of what was said. After a workshop, everyone has seen the same thing, has been able to challenge it, and the decision is written on the board.

It is also the best way to avoid the classic scenario: six weeks of design, a final presentation, and a business lead who discovers the product does not handle the case that makes up 40% of their activity.

## Who to invite

Five to eight people, no more. Beyond that, the workshop turns into a talk.

| Role | What they bring | When to invite them |
|---|---|---|
| Decision maker (sponsor, CPO, executive) | Arbitrates, decides, unlocks budget | Kickoff, prioritization, final sign-off |
| Business (sales, operations, experts) | Real cases, exceptions, vocabulary | Journeys, wireframes |
| Tech (lead dev, architect) | Feasibility, hidden costs, available data | Every workshop, no exception |
| Support and customer service | Pain points, recurring questions | Kickoff, journeys |
| Users | Reality on the ground | Testing, and ideally the kickoff |

The rule I never negotiate: tech is in the room from the first workshop. A mockup developers discover at the end has very little chance of shipping as designed.

## The script of a 90-minute workshop

A workshop without a script becomes a discussion. Here is the structure I use, whatever the topic.

1. **Before (D-3)**: a one-sentence goal, the agenda, materials to review ahead. If the goal does not fit in one sentence, the workshop is not ready.
2. **Open (10 min)**: restate the problem, what is already decided and what must be decided today. No round of introductions beyond five people.
3. **Diverge (25 min)**: everyone writes alone, in silence, their ideas or objections on sticky notes. Silence keeps the most senior person from steering the whole group.
4. **Converge (25 min)**: group, name the clusters, remove duplicates. The designer rephrases out loud to check everyone means the same thing.
5. **Decide (15 min)**: dot voting, then the decision maker decides. Write down the decision, its why and what we give up.
6. **Commit (15 min)**: who does what, by when. Every action has a name and a date.

The summary goes out within 24 hours: decisions, trade-offs, actions, open questions. One page, never more.

## Six workshops, from kickoff to delivery

### 1. Kickoff and framing

Align the team on the problem, the users, measurable goals and constraints. Deliverable: a one-page vision and the list of what we will not do. It follows directly from [UX framing](https://vladispala.fr/en/blog/ux-strategy-framing-before-designing/).

### 2. Journeys and information architecture

Map current and target journeys with business and support, screen by screen, noting every pain point. Deliverable: prioritized target journeys and the site map.

### 3. Wireframe review

Show black and white screens, no colour, no images, so the discussion is about structure and content, not taste. A business person walks through a real scenario, out loud.

### 4. UI and design system review

Approve the visual direction on three or four key screens, then the components. The question is not "do you like it" but "does it serve the goals set at kickoff".

### 5. Prioritization after testing

Play back user tests as short videos: nothing convinces faster than a user getting stuck. Then sort fixes into three piles: before delivery, right after, later.

### 6. Handoff and acceptance

Walk the tech team through final mockups, states (empty, error, loading), responsive rules and components. Agree on acceptance criteria together. A handoff is not sending a file, it is a workshop.

## Between workshops

Workshops set the pace; the work happens between them. So that nothing gets lost:

- **A shared decision log**: date, decision, why, who. It is the document you reread when someone reopens a closed topic.
- **Comments in Figma**, not by email: every remark is attached to the screen it concerns.
- **A short weekly demo** (15 minutes) to show progress without waiting for the next workshop.
- **One single channel** for questions, with a commitment to answer within 24 hours.

## Pitfalls

1. **Too many people**: beyond eight, nobody dares to disagree.
2. **No decision maker**: a workshop without an arbiter produces options, not decisions.
3. **Showing colour too early**: the discussion drifts to taste and the structure is never validated.
4. **The designer defending their mockup**: in a workshop, they facilitate. They defend users, not pixels.
5. **Minutes arriving a week later**: everyone's memory has already rewritten the story.

## Going further

The kickoff builds on the [UX strategy](https://vladispala.fr/en/expertise/ux-strategy/) method; the final review and handoff on the [UX/UI audit](https://vladispala.fr/en/expertise/ux-ui-audit/). The [case studies](https://vladispala.fr/en/work/) show what this work produces once shipped. And to choose the right person to run them: [How to choose a freelance UX designer](https://vladispala.fr/en/blog/how-to-choose-a-freelance-ux-designer/).

## Frequently asked questions

### How many workshops does a UX/UI project need?

Six on average for a mid-sized product or flow: kickoff, journeys, wireframe review, UI review, prioritization after testing, handoff. A small website needs three; a multi-role platform may need ten or so, often one set per user role.

### Do workshops need to be in person?

The kickoff benefits from being in person, because that is where the team forms. The other workshops work very well remotely with a shared board (FigJam, Miro) and a stricter script: cameras on, timed speaking turns, silent voting.

### What if a decision maker cannot attend?

Postpone the decision workshop rather than decide without them. Or ask them to explicitly delegate the decision to someone in the room. A decision made in their absence will be reopened, and will cost twice as much.


---

Contact: https://calendar.app.google/1nHYAgzZcMcMqCbV7 · contact@vladispala.fr · https://www.linkedin.com/in/vladispala/
