Good design starts long before the first pixel.

There is a strange habit in the design industry. A business gives an agency a brief, and the agency starts designing. A few meetings. Some competitor screenshots. A moodboard. A positioning exercise. Maybe a workshop. Then, somehow, a brand begins to appear.

It looks considered. It feels strategic. It may even be very good.

But there is a question we think should come much earlier:

Do we actually understand the business yet?

Because knowing what a company does is not the same as understanding it. You can know the product. You can know the market. You can know the customer. You can know the competition. And still completely misunderstand the business.

The interesting parts are usually less obvious. Why was the company built this way? What does it make money from? Where does it struggle? What does the customer actually value? What does the team believe that the market does not? Which parts of the business are intentional, and which are simply the result of decisions that were made five years ago and never revisited?

What does the company promise? And, perhaps more importantly, what can it actually deliver?

Those questions matter because design does not exist independently of the business. A brand promise creates expectations. A product experience reinforces them. A website explains them. A sales team repeats them. Operations ultimately has to deliver them. If those things disagree, no amount of visual polish can fix the underlying problem.

We've seen businesses ask for a more premium identity when what they really needed was a more premium experience. We've seen companies ask for a better website when the problem was that they had never decided what they wanted to be known for. We've seen products try to communicate ten benefits because nobody had made the difficult decision about which one actually mattered most.

These are not visual problems.

They simply happen to eventually show up in visual form.

That is why we don't like starting with design. We like starting with understanding. We want to know how the business works. How it makes money. How customers find it. Why they choose it. Why they leave. Where the friction is. What the team is good at. What it isn't good at. What the founder wants the business to become. And what reality currently allows it to become.

Sometimes this means asking questions that have very little to do with design. That's intentional.

Because the better we understand the business, the fewer assumptions we have to make later. And fewer assumptions usually produce better decisions.

The goal isn't to become experts in someone else's business overnight. That's impossible. The goal is to get close enough to the truth that the work starts reflecting the business rather than an agency's idea of what the business should look like. That's an important distinction.

Because there is a particular kind of design that looks impressive but could belong to almost anyone. Change the logo. Change the name. Change the colours. The work still works.

That's usually a warning sign.

Good design should feel inevitable in hindsight. It should make you think:

Of course this is what this business should look like.

Not because there was only one possible answer. Because the answer came from somewhere real. From the product. From the customers. From the ambitions. From the constraints. From the uncomfortable truths. From everything that makes this business different from the one next door.

That is where strategy becomes useful. And that is where design becomes much more than decoration.

Before we design the business, we try to understand it.

Because the first pixel is rarely where the work begins.