Discovery done right

Daniele De Blasio, Director, Digital Strategy at Bladonmore, explains why the first four weeks of your project decide how successful the whole process is.

‘We know exactly what we need. Can we just skip to the design phase?’

This refrain will be familiar to anyone who has spent more than a week in digital strategy. The pressure to move fast and hit an aggressive Q3 launch date often makes the discovery phase feel like an unnecessary delay – a hurdle of sticky notes and workshops standing between the client and their shiny new website. The issue is that jumping straight into design and development without a foundational discovery phase is like buying expensive tiles for a house before you’ve poured the concrete. You might end up with something beautiful, but the moment you put any weight on it, the cracks will show.

Discovery is where we align the business goals with the user’s reality. Here is what ‘discovery done right’ looks like, and why it is the ultimate insurance policy for your digital budget.

Three lenses of insight

For a discovery phase to be successful, you must go beyond just listening and really interrogate the brief. That way, you ensure that you’re asking the right questions to deliver insightful answers. We look at the project through three distinct lenses before a single line of code is written.

1. Find the why behind the what

Clients usually arrive with a list of features. We hear, ‘We need a portal, a chatbot, and a new blog’. During stakeholder interviews, our job is to reverse-engineer those feature requests into business goals. By talking to different departments – sales, customer service, marketing, and leadership – we often uncover competing priorities. Discovery is the arena where we resolve these internal misalignments and tension points.

We shift the conversation from, ‘What do we want to build?’ to ‘What commercial capability are we trying to unlock?’

2. Confront reality

The most dangerous bias in digital project delivery is assuming your users think exactly like your internal team. User analysis – whether through data deep-dives, surveys, or direct interviews – removes the guesswork. Through the first lens, we looked at internal tensions, now we’re looking at external ones – we’re looking for where our assumptions differ from the user’s reality.

Why are users dropping off at the products page? Why are the sales team fielding questions that should be answered on the website? When we understand the sticking points that are blocking the progress against our business goals, we can design the website to resolve them.

3. Find the white space

The final lens is your competitor audit. To build something that stands out in your marketplace, you need to understand what everyone else is doing, where they’re going wrong, and how you can better serve your users. That insight will help you build a customer-centric tool that really stands out in the crowd and delivers a differentiating user experience.

Translating insight into action

Once we understand the business, the user, and the market, we have to translate those abstract insights into tangible blueprints for the design and development teams. We have to set the foundations of a solid website before we start painting.

Before we design how a site looks, we design how it thinks. The sitemap is the structural floor plan of the website. I’ve written previously about how information architecture is the unsung hero of ROI. The sitemap ensures that the user journey from landing on the site to booking a consultation is as frictionless and intuitive as possible. If a page doesn’t serve a specific user need or business goal, it doesn’t make it onto the sitemap.

Once we have a sitemap, we can move into wireframes. These are often misunderstood as incomplete designs. In reality, they’re never meant to be the design, we’re laying out the logic of the website, understanding what content needs to go on each page, the hierarchy of messaging, and the core functionality without the distraction of brand colors, typography, or imagery. No amount of beautiful user interface and design will make up for a lack of logic if the page hasn’t been properly planned.

Why discovery is an investment

When we get to the end of a robust discovery phase, we hand over a defined, tested, and commercially aligned roadmap to the delivery teams.

Taking the time to define the exact capabilities required means the development team knows precisely what to build. Mapping the Information Architecture means the design team knows exactly what content to prioritize. And most importantly, we have agreed on the core business goals on day one – the client is protected from expensive scope creep halfway through the build.

A properly planned and executed discovery phase ensures that when you finally do launch, you’ve built an engine for growth that fits your needs precisely and delivers a meaningful experience to your users, rather than an expensive digital monument to a missed opportunity.

If you want to get the foundations right, get in touch.