The Discovery Phase Is Not Optional

We used to think discovery was a luxury. A thing you did on big projects. A line item you could trim when the budget got tight. The client would push back on the two weeks of workshops and interviews and we’d shrug and say okay, we’ll figure it out as we go.

Then we’d figure it out as we went. And it would go badly.

Every time we’ve skipped discovery, we’ve paid for it. Every time we’ve insisted on it, the client thanked us later. It took us years to understand why.

What discovery actually is

Discovery is not a kickoff meeting. It is not a brand questionnaire. It is not sitting the client down and asking what their favorite colors are and what their competitors look like.

Discovery is the work of figuring out, together, what the project is actually trying to accomplish. Underneath the brief. Underneath the RFP language. Underneath the “we need a new website” that got the project started in the first place.

Sometimes the answer is close to what the client asked for. Sometimes it’s not. Either way, you can’t know until you dig.

The questions sound simple. Who is this for. What are they trying to do when they get here. What does success look like six months after launch. What is the thing we’re building actually competing with for someone’s attention. What happens if we do nothing.

The answers are almost never simple.

What happens when you skip it

Here’s the pattern we’ve seen over and over again. Project kicks off with a confident brief. Design happens. Build happens. Launch happens. Three months later, the client is unhappy and nobody can quite articulate why.

Usually it’s one of two things.

One: the site is doing a different job than the client needed it to do. The brief said “modernize our brand.” The actual problem was that the sales team couldn’t find anything to send to prospects. We built a beautiful brand expression. We did not build a sales tool. Both parties are frustrated.

Two: the site is doing the right job, but the client’s organization isn’t set up to feed it. We built a great news section. Nobody is writing the news. We built a case studies template. Nobody is approving case studies for publication. We built a resource library. There are no resources. The site becomes a monument to its own launch, slowly going stale, because the discovery conversation never surfaced the fact that there was nobody internally who was going to own the content pipeline.

Both of these are discoverable in week one. Both of them are nearly impossible to fix in month six.

What the client gets out of it

The hardest part of selling discovery is that from the client’s side, it can look like paying us to ask them questions. They know their business. We don’t. Why are we charging them for a chance to teach us about it.

The honest answer is that we’re not charging them to teach us about their business. We’re charging them to figure out what the project should be. Those are different things.

A good discovery process produces:

• A clear articulation of who the site is for and what they came to do
• A map of the content that will need to exist for the site to work
• A list of the people inside the organization who will own each piece after launch
• An agreed-upon definition of what success looks like, measurable where possible
• A written-down version of the trade-offs we’re making and why

Most clients have some of this in their heads already. Very few have it written down. Even fewer have it written down in a way that the whole team agrees on.

When discovery is done right, the client walks away with something they can use whether we build the site or not. They know what they’re trying to do, they know what it will take to do it, and they know who’s responsible for what. That document outlives any particular project.

What we get out of it

For us, the honest answer is that discovery is where we figure out if the project is going to work.

Not whether we can build it. We can almost always build it. What’s important is whether it’s going to work.

The signals we’re watching for during discovery are small. Does the client have a champion internally. Are there two or three stakeholders who agree about what the site is for, or does every meeting end with a different person vetoing the thing the last person approved. Can anyone tell us who the site is actually for, by name or by job title, or are we getting hand-waves about “everyone.” Does anyone own the content that will need to exist to make this site work. Is there a theory of change.

If the signals are good, we build with confidence. If the signals are bad, we have a real conversation with the client before anybody signs anything else.

That conversation has saved us from six-figure disasters more than once. It has also, occasionally, cost us the project. We’re okay with both outcomes.

Where we are now

These days, discovery is non-negotiable. Not because we’re precious about process, but because we’ve been burned enough times to know what skipping it looks like.

If a client doesn’t want discovery, they don’t want us. That’s okay. There are plenty of shops that will build what you asked for without asking why. We’re not one of them.

The ones who hire us because of this are the ones whose sites are still working years later. The arithmetic there is pretty clear.