A focused workshop can expose the organizational questions a new interface cannot solve on its own.
Website redesigns often begin with broad agreement: the current site no longer works as well as it should. But agreement about the symptom is not the same as a shared understanding of the problem. Leadership may see a brand that no longer reflects the organization’s direction. Marketing may see accumulated content and language that has become difficult to manage. Customer-facing teams may see recurring confusion. Technical teams may see platform constraints. Users simply see a path that does or does not make sense.
“Alignment is different from agreement.”
—Goran Paun, Principal and Creative Director, ArtVersion
Goran Paun, Principal and Creative Director of ArtVersion, examines that gap in Fast Company’s “Inside the Website Redesign Workshop.” The article explains how a few focused sessions can reveal the organizational, messaging, usability, and governance questions that need to be understood before design begins.
The website concentrates problems the organization has not named
A website is often the most visible place where organizational drift appears. The business expands, audiences change, new services are introduced, and internal ownership becomes distributed. The website continues carrying earlier assumptions until its language, navigation, and structure no longer match how the organization operates or what visitors need to understand.
That is why a redesign workshop should begin with diagnosis rather than visual preference. A request to make the site feel more current may point to a positioning problem, an information architecture problem, a content-governance problem, or several of those at once. Naming the real pressure behind the redesign determines what the project must solve.
Different stakeholders hold different kinds of evidence
Useful participation does not mean placing everyone into one large conversation and treating every perspective as interchangeable. Each group is positioned to reveal something different. Leadership understands direction and reputation. Marketing knows which pages and messages are difficult to maintain. Customer-facing teams hear the questions people repeatedly ask. Technical and subject-matter teams understand operational limits and nuance. Users reveal what the experience communicates without the benefit of internal context.
The workshop creates value by separating those forms of evidence, then reading them together. A user’s hesitation can settle a navigation debate that internal discussion has left unresolved. A content-maintenance problem may reveal unclear ownership rather than a writing problem. A technical constraint may change which redesign ambitions are realistic. When those signals are collected deliberately, the project begins with evidence instead of assumptions.
Alignment does not require unanimity
A successful workshop does not end with everyone agreeing on every decision. In many cases, disagreement is the most useful finding. It shows where teams have been carrying different assumptions about audiences, priorities, terminology, ownership, or the role the website should play.
Alignment means those tensions are visible and the group understands what the website redesign must make clear, which trade-offs are likely, and why certain decisions matter. That shared direction is more durable than superficial consensus because it gives the design team a basis for making choices when new questions appear later.
The workshop creates evidence. Synthesis creates direction.
The working session may last only a few hours. Its real value emerges afterward, when notes, observations, transcripts, and conflicting comments are interpreted. The team must distinguish between issues of messaging, navigation, content ownership, platform capability, governance, and user behavior. Without that synthesis, the workshop produces participation but not direction.
This is where website strategy turns research into a design brief. The resulting synthesis should identify the decisions the redesign must make, the evidence behind them, and the priorities that will guide information architecture, content, interaction, and development. It becomes a working reference for the project rather than a record of the meeting.
Design should begin after the problem becomes legible
At ArtVersion, discovery is part of the design work because interfaces cannot resolve an organization’s unanswered questions by themselves. Workshops, stakeholder conversations, content and brand audits, user observation, and technical review help establish what the website needs to do before the team determines how it should look.
That preparation does not slow a redesign down. It prevents design and UI/UX decisions from becoming expensive proxies for debates that should have happened earlier. When the problem is understood, the design process has a clearer standard: every decision can be evaluated against what users need, what the organization must communicate, and what the platform must support.
Fast Company’s feature offers a practical reminder that a website workshop is not successful because everyone attended or because the room felt collaborative. It is successful when the right tensions surface, the evidence is synthesized, and the redesign begins with a shared understanding of what must become clearer.
Read the full Fast Company article: Inside the Website Redesign Workshop