Why the best converting websites start with a discovery workshop

A key audience wasn't considered. The product structure doesn't translate well to navigation. The sales team has a completely different idea of what the website is for than the marketing team does. By that point, you're backtracking on decisions and it affects all of the work already completed.

Discovery workshops exist to prevent exactly that.

At Abstrakt, we run structured, full-day discovery workshops at the start of every major website project. Not as a formality and not as a box to tick before design begins, but as the single most important thing we can do to ensure the work that follows is grounded in truth. It’s shaped by the people who know the business best, and built around the audiences who will actually use the site.

Our workshops typically run as a half or full-day session, bringing together stakeholders from across the business - usually marketing, sales, senior leadership, and sometimes operations - alongside our own team. We send an agenda and any preparatory homework in advance so everyone arrives ready to contribute, rather than spending the first hour finding their footing.

We work through a structured agenda covering the big questions a website project needs to answer before a single wireframe is created. That includes the business itself - its goals, growth targets, and competitive position through to the proposition, product and service offering, audiences, conversion journeys, content strategy, and technical requirements.

But the real value isn't in the agenda, it's in what the different voices in the room say when the questions are asked. Everything is captured and recorded.

Good workshop questions do two things at once - they surface information, and they expose assumptions. Some of the most useful moments in a workshop happen when a question prompts disagreement between stakeholders in the room because that disagreement is something the website will eventually have to navigate.

Workshop example one

In a recent workshop, we asked a seemingly simple question - who are your audiences, and what are they trying to do on your website? The brief had outlined three audience types. By the time we'd properly mapped each one, we'd identified that those groups behave entirely differently. One audience tends to be fast-moving and transactional; they often arrive on site already knowing the product name they're looking for. Two other audiences are more relationship-driven, and use the website as part of a broader evaluation process. A one-size-fits-all user journey would serve none of them particularly well.

That same session told us something else - the site search was being used heavily, not just by customers, but by the internal sales team using it as a quick product catalogue. That's not something you'd find in a brief. It changes how you think about search functionality, what you prioritise technically, and what you'd name as a primary conversion action on the homepage.

Workshop example two

In a separate discovery workshop, a question about brand architecture opened up a much bigger conversation. The business operated several sub-brands but it became clear in the session that most customers don't choose by brand. They choose by style, price point, and spec. The brand names were being used more for internal organisation than for customer navigation. That one insight reshaped the entire approach to the product section and how content would be structured for different audience types.

These aren't the kind of insights that emerge from a brief. They're insights that emerge when you ask the right questions to the right people, in the same room, with time to think.

The brief is a starting point and captures what stakeholders believe to be true before a project begins. But it's inevitably incomplete,  not because anyone is withholding information, but because it's genuinely difficult to articulate the full complexity of your business, your audiences, and your goals in a written document.

Workshops surface several categories of insight that briefs routinely miss.

Internal misalignment: On almost every project, different stakeholders hold different assumptions about what the website is for, who it's for, or what success looks like. A workshop puts those assumptions into conversation with each other. The gap between what the MD thinks the site should do and what the sales director needs from it is something that has to be addressed before it gets baked into the architecture.

The nuances of the product or service offering: In one workshop, we uncovered that two types of product "packages" existed but were only used in tender submissions with completely different pricing structures. That distinction wasn't in the brief, but it's critical to how ecommerce flows are structured and how content is written, and became an opportunity for our client to explore as an offering on their website as well.

An honest picture of what isn't working: Workshops create a space where stakeholders can speak candidly about the failures of the current site. We heard about product pages missing dimensions, leading to a high volume of avoidable support queries. We heard about a blog section that wasn't generating traffic or engagement. We heard about an enquiry process that was creating more friction than it should. None of that would have emerged unprompted and were only highlighted because we asked, and otherwise, may have remained unsolved and a friction with a new website.

Opportunities no one had articulated yet: In a recent workshop, the conversation around competitors revealed that our client’s aftercare and remedial service - one of the strongest in the sector - was almost entirely invisible online. That's a major differentiator that wasn't being leveraged at all. Identifying it in the workshop meant it could be built into the strategy from the start and not retrofitted later because we had all the background knowledge we needed to consider the journey upfront.

Everything that comes out of a workshop feeds directly into the planning phase of a project - the information architecture, the UX thinking, the content strategy, SEO, and the technical scope. The more thorough the workshop, the stronger that foundation.

When we map audience journeys, we're building on personas that came from the room; informed by people who speak to customers every day, not hypothetical archetypes created from assumptions we may have on an industry. When we define the site's content priorities, we're doing it in the context of what we know about search behaviour, what questions customers are actually asking, and where the current site is falling short.

The workshop write-up we produce after every session gives the whole project team - client-side and agency-side - a single source of truth to work from. It documents what was discussed, what was agreed, and what still needs answering. 

On a large project with multiple stakeholders, that document is invaluable for keeping everyone aligned as decisions get made down the line.

The short answer is that you start making decisions based on incomplete information, and you usually don't find out how incomplete until you're deep into the project.

The longer answer is that the risks slowly compound. 

• If you don't properly understand your audiences in advance, you design for the wrong user. 
• If you don't map the conversion journeys before wireframing, you create pathways that look logical on paper but break down in practice. 
• If you don't surface the technical and integration requirements early, you scope incorrectly and face expensive change requests later.

Without the alignment that a workshop creates, stakeholders often pull in different directions as a project progresses. Design sign-off takes longer. Content decisions get revisited. The ambiguity that the workshop would have resolved earlier has to be resolved later, when it's harder and more expensive to do so.

For smaller, more clearly defined projects, a full-day workshop may not be necessary. But for any significant website build - particularly where there are multiple audiences, a complex product or service offering, or meaningful ecommerce functionality - the workshop isn't overhead. It's how you protect the entire investment that follows.