As the website redesign workshop session starts, a few screens are open on the conference room display. Printed website maps are spread across the table. Around the room, a group of people agrees on one thing. The current website no longer does what it needs to do.
That is how a typical redesign workshop begins. Leadership may believe the site no longer reflects where the organization is headed. Marketing sees a message that has become too broad or difficult to manage. Customer-facing teams may know where users get confused. When brought into the process, users often reveal something else entirely.
Everyone is talking about the website, not always talking about the same problem. That is why the workshop matters.This roundtable is where the organization begins to see what the current site has been carrying: evolving priorities, inherited assumptions, distributed ownership, outdated language, and sometimes a version of the organization that no longer matches where it is headed.
The website is the most visible surface for those issues. The workshop helps separate what the site says today from what the organization now needs to make clear.
WHAT THE TEAMS KNOW ABOUT THE SITE
Organizations often mistake inclusion for putting everyone into the same conversation at the same time. This is about respecting the difference between types of input. Leadership can speak to direction and reputation, but the goal is to understand what each group is uniquely positioned to reveal about the site’s load.
LEADERSHIP
When leadership enters the room, the conversation should begin with high-level discussions about what has changed. Many redesigns begin because the website “looks old,” or because it has drifted into looking like everyone else’s. Often, the deeper issue is that the organization has changed, and the website has not kept pace.
- Has the business expanded or audience shifted?
- Has the organization introduced new services?
- Has the organization outgrown the language it once used to describe its work?
MARKETING
Marketing teams know the website’s daily reality. They know which pages are difficult to maintain, which messages no longer work, where content has accumulated, and where analytics suggest friction.
With marketing and communications teams, the questions become more practical:
- Which pages are hardest to maintain?
- Where does the message become inconsistent?
- What content receives attention internally but little engagement from users?
Which paths matter most, and where do people drop off?
CUSTOMER-FACING TEAMS
With subject-matter and customer-facing teams, the questions shift again. Customer-facing teams reveal practical friction. They hear the questions directly. They know what people missed, what needs to be repeated, and where the website creates avoidable work.
- What do clients or customers misunderstand most often?
- Which terms need explanation?
- Where does the website oversimplify something important?
- What questions are people repeatedly asking because the site does not answer them clearly enough?
TECHNICAL AND SUBJECT-MATTER TEAMS
Technical and subject-matter teams know the nuance. They understand what customers misunderstand and where language becomes too broad, too technical, or too simplified.
This part of the workshop requires careful facilitation because internal importance and user priority are not always the same.
WHAT USERS REVEAL
Users reveal something different again, and their value lies in showing how the site’s experience is understood from the outside.
With users, the questions should be more about behavior and usability:
- What would you do next?
- Where would you look for this information?
- What does this label mean to you?
- What made you hesitate?
Users evaluate a website based on what they can understand without the backstory, internal terminology, or organizational chart. Instead, they arrive at the site with a task, a question, or a need.
In sessions where the users test the website, the most useful moments often arise from hesitation. A user pauses before choosing a path, misinterprets a label, or skims past a message the organization thought was important. Those moments reveal the gap between intent and understanding.
In one recent session, a user was asked to find pricing on a services company’s site. She opened the main navigation menu, read the top-level labels, and stopped navigating. The “obvious” menu labels displayed were built around how the company organized its offerings internally. The labels told her nothing about where to find pricing.
She guessed, clicked into the wrong section, and backed out. Nobody had questioned that label before, because it matched the org chart. One person hesitating in front of it settled a navigation debate that internal discussion had left open for weeks.
ALIGNMENT IS NOT AGREEMENT
A successful workshop doesn’t mean everyone leaves agreeing on every decision. Some of the most valuable workshops reveal disagreement. That is the work. The workshop is successful when the right tensions become visible before they become design problems.
Alignment is different from agreement. People can nod in a meeting and still carry different assumptions into the project. Alignment means the team understands what the website needs to make clear, what trade-offs may be necessary, and why certain decisions matter.
FROM NOTES TO DIRECTION
The workshop itself is short. It’s a single working session, usually a few hours, with the right participants. What produces the value takes longer, and it happens afterward, in how that material gets read. The workshop’s real value lies in synthesizing raw notes, transcripts, and a list of comments to help craft strategy, direction and design.
Which concerns pointed to messaging, navigation, governance, content ownership, or operational strain? Where did the website reveal a deeper decision that had not yet been made?
This is where workshop input becomes redesign direction. A redesign reflects what was understood from the room and what needs to happen before redesign work begins. Everyone helps reveal what the website needs to make clear.
At the end, the team receives a synthesis document. It names the decisions the redesign will have to make, the trade-offs behind them, and the priorities the group aligned on, and it carries the workshop forward into the design work.
Goran Paun is the principal and creative director of ArtVersion.