A working brief: what we ask before pitching

The quality of a project is often determined long before the first design file is opened.

It's tempting to think good products begin with inspiration. In practice, they usually begin with better questions.

Over the years, we've noticed that the strongest client relationships share one characteristic: everyone leaves the first meeting with greater clarity than they arrived with. Not because every answer has been found, but because the right problems have finally been identified.

A brief isn't paperwork.

It's a design tool.

When conversations begin with questions like, "How many pages do you need?" or "Which colours do you prefer?", we're already discussing solutions before understanding the problem. Those details matter eventually, but rarely at the start.

Instead, we begin somewhere else.

What changed inside the business that made this project necessary now?

That single question often reveals more than an hour of feature discussions.

Sometimes the answer is growth. A company has outgrown the website that served it well for years. Sometimes it's repositioning after entering a new market. Sometimes it's an internal process that has become painfully manual. Occasionally, nothing is technically broken—the business has simply evolved while the digital experience remained frozen in time.

Understanding that context changes every decision that follows.

Another question we return to repeatedly is surprisingly straightforward.

What does success look like one year after launch?

Not next month.

Not immediately after deployment.

A year.

The answers tend to shift the conversation away from aesthetics and towards outcomes.

"We want fewer support requests."

"We need to hire more efficiently."

"Our sales team spends too much time explaining the same things."

"We want distributors to find information without calling us."

Those aren't design preferences. They're business objectives.

Once those objectives are clear, features become much easier to evaluate.

Does this interaction move us closer to the goal?

If not, why is it there?

It's remarkable how many ideas disappear when they're measured against a clearly defined outcome.

We also spend time discussing constraints, even though they're rarely exciting.

Budget.

Timeline.

Internal approvals.

Content availability.

Technical limitations.

Constraints aren't obstacles to creativity. They're the framework that gives creativity direction. A project with unlimited possibilities often struggles more than one with clearly defined boundaries.

One area that's frequently overlooked is ownership after launch.

Who updates the website?

Who approves new content?

Who maintains integrations?

Who responds when something changes inside the business?

These questions don't usually appear in visual mockups, yet they influence the longevity of every digital product. A beautifully designed system that's impossible for the client's team to manage eventually becomes another problem waiting to be solved.

The same thinking applies to content.

Many projects assume that words will somehow appear once the interface is finished. Reality tends to work differently. Good content shapes navigation, hierarchy and interaction patterns from the beginning. Waiting until the final week often leads to compromises that could have been avoided.

Technology enters the conversation later than most people expect.

Frameworks change.

Hosting platforms evolve.

Libraries come and go.

The underlying business rarely changes because React released another version.

That's why we prefer discussing technology after we've understood people, processes and objectives. Engineering decisions become significantly easier when the product itself is already well defined.

Perhaps the most valuable part of a discovery session isn't the answers we receive. It's the assumptions that quietly disappear.

Clients often arrive believing they need one solution and leave recognising a completely different opportunity. Occasionally the best recommendation is to build less than originally planned. Sometimes it's to postpone development entirely until a larger operational issue has been addressed.

Those conversations don't always lead to the biggest projects.

They usually lead to the right ones.

A good brief doesn't limit creativity. It protects it from being wasted on solving the wrong problem.

That's why we treat discovery as part of the design process rather than an administrative step before it begins.

By the time sketches appear on a screen, many of the most important design decisions have already been made through careful conversation.

The interface is simply where those decisions become visible.