Process4 min read
Strategy before aesthetics
Design has to be right about something. Until the strategy is settled, there is nothing for it to be right about.
The most expensive design decision on any project is the one made without a reason. It costs nothing at the moment it is made. It costs a great deal later, when the site is live and nobody can explain why the homepage leads with a slideshow, why the services are ordered the way they are, or why the enquiry form asks eleven questions. Those decisions were aesthetic in the sense that they were made by looking. Strategy is the discipline of deciding by thinking first.
What strategy means for a website
The word gets used to mean a slide deck. For a website, strategy is four concrete answers, written down and agreed before design begins.
- Positioning. What this business is, for whom, and what makes choosing it the obvious decision rather than one option among several.
- Audience. Who is actually visiting, what they arrived wanting, and what they are worried about.
- Journey. The path from arrival to the action that matters, page by page, with the question each page has to answer.
- Success. What the site is for, in a form that can be measured after launch.
Every design decision that follows should be traceable to one of these. A layout exists because of the journey. A headline exists because of the positioning. A form is short because of what we know about the audience. When a decision cannot be traced back, it is decoration, and decoration is the first thing to cut when something has to give.
Discovery: the questions before the design
Discovery is where strategy comes from, and it is a conversation before it is a document. We ask about the business before we ask about the website: what a good month looks like, which customers are worth more than others, what the competition does that annoys you, what customers say when they call. We ask what the website has to do, and then we ask why, until the answer is a business outcome rather than a feature.
A brief that says "we need a modern site with a blog and a gallery" is a list of features. A brief that says "we lose the customers who would pay the most because our site makes us look like the cheapest option in the area" is a strategy waiting to be designed. Getting from the first to the second is the job of discovery, and skipping it is how projects arrive at launch with a site that does everything asked and nothing needed.
Structure follows strategy
With the four answers in hand, the shape of the site becomes an argument rather than a guess. The sitemap is the journey made concrete. The content structure decides what each page says and in what order. Wireframes settle hierarchy and flow without the distraction of colour and type. By the time anything is designed, the question of what goes where has been answered, and design can spend its attention on how it should feel.
This is the order of our own process: discover, define, design, develop. Design is third on purpose.
Then design has something to be right about
Design without strategy is a matter of taste, and taste is impossible to argue with productively. A client who dislikes a colour and a designer who defends it are both right, and the conversation goes nowhere. Design with strategy is a matter of fit. Does this treatment make the positioning clearer? Does this layout serve the journey? Those questions have answers, and the answers make design reviews shorter, calmer, and better.
Saying no to a feature
Strategy is also what lets a studio decline work honestly. If a requested feature does not serve the journey or the success measure, the right response is to say so and redirect the budget to something that does. A blog nobody will write for, a chatbot that answers nothing, an animation that delays the content: each is a real cost with no traceable reason. Declining revenue you do not deserve is uncomfortable and it is the strongest signal of a studio worth hiring. It is a commitment we make in writing.
The reasoning requirement
We ask ourselves to complete a set of sentences for every decision on a project, and we think any business commissioning a website should ask its studio to complete them too.
- This layout exists because…
- This call to action exists because…
- This animation exists because… and it respects the visitor's reduced-motion preference.
- This typeface exists because…
- This spacing exists because…
- This navigation exists because…
"Because it looks good" is not a completion. "Because the eye needs somewhere to rest before the price appears, and rushing that decision costs conversions" is. The difference between those two answers is the difference between aesthetics and strategy, and it is decided long before anyone opens a design tool.
Questions people ask
- How long does the strategy phase take?
- For most business websites, a focused discovery workshop and a week or two of definition. It is a small share of the project and the part with the most leverage over everything that follows.
- I already know what I want. Can we skip discovery?
- Knowing what you want is valuable input to discovery, not a substitute for it. The point is to connect what you want to why, so that every decision downstream can be tested against the reason. That connection is usually quicker to make than clients expect.
- Does strategy make the design more conservative?
- The opposite. Strategy gives a bold design something to be bold about. Without it, boldness is a risk nobody can evaluate; with it, an ambitious treatment can be defended because it serves a stated purpose.
Put it to work