There comes a moment in almost every web project when the mood shifts. Somewhere between the third round of feedback and the second relaunch of the relaunch. Suddenly, what sounded so clear at the beginning isn’t clear anymore. The design is pretty, but it just doesn’t quite fit. The content is there, but it doesn’t tell a story.
What happened? In most cases: The first workshop was too rushed, too superficial, or didn’t happen at all.
The workshop as a foundation, not a kick-off
In agency practice, the kick-off workshop is often treated as a necessary ritual. You get to know each other, you show references, you jot down requirements. And then you get started.
That’s a mistake. Not because getting to know each other isn’t important—but because it prioritizes the wrong things. A good first workshop doesn’t ask: What do you want? It asks: What do you want to achieve? For whom? And why now?
The most important design decision isn’t a visual one. It’s strategic. And it’s made during the first conversation—whether consciously or unconsciously.
What happens in a good workshop
Goals are made concrete
“We want to appear more modern” is not a goal. “We want applicants to feel, after their first visit to the site, that they can grow here”—that is a goal. The difference may seem linguistic, but it is structural: the second goal can be tested, measured, and translated into design decisions.
Target audiences become real
Personas are often too abstract to be useful. What helps: concrete usage scenarios. Who opens this page, when, on which device, with what expectations—and with what skepticism? Answering these questions in a workshop changes how you build components, prioritize content, and structure navigation.
Conflicts come to light early on
In every company, there are internal tensions over what a website should achieve. Marketing wants leads. Management wants brand awareness. IT wants maintainability. HR wants recruitment. Everyone wants to avoid giving editors too much freedom. Someone wants a search bar that can do everything. If these conflicts become apparent during the workshop, they can be resolved or at least managed. If they don’t, if everyone remains stuck in a vaguely defined truce, they end up as conflicting requirements in the briefing and as an inconsistent design in the browser. And no one has even spoken to the editorial team yet.
The Cost of Poorly Run Workshops
An inadequately defined foundation reliably produces the same symptoms:
- Contradictory feedback because different stakeholders had different projects in mind
- Designs that are technically sound but strategically ineffective
- Rework during phases when changes are costly
- Projects that fail to truly excite anyone after launch, not even the client
None of this can be fixed with better design. It can only be prevented by asking better questions at the start.
How we approach it
At NXTones, the first workshop isn’t a mandatory meeting. It’s the actual project kickoff. We deliberately invest time in asking the right questions, even if they’re uncomfortable. What isn’t working today? What didn’t the last relaunch solve? What would success really mean?
Sometimes this leads us to decide together to tackle a different scope than originally planned. That’s not a problem. That’s the point.
Conclusion
The final design is evident. The impact of the first workshop is felt—in everything that follows. When a project feels right from the start, when decisions come easily, when feedback is constructive rather than destructive: that usually means someone asked the right questions at the beginning.
That’s no coincidence. It’s a method.
Do you have a project coming up and want to be on solid ground right from the start this time?
If you want to implement projects quickly, flexibly, and with a focus on results, you’ve come to the right place. Let’s talk, we’ll show you how we can take your digital strategy to the next level together.
Write to us: we look forward to hearing about your project!
