Why I Don’t Start Website Projects With Design
Most website projects start the same way. Colors, fonts, a Pinterest folder of sites you like, a rough sense of the vibe you’re going for. It feels like the obvious place to begin, you’re building a website, so you start with what it should look like.
I don’t start there, and it’s not because design doesn’t matter to me. It’s because a beautiful website that doesn’t say the right thing to the right person is still a website that doesn’t work. It just fails more quietly, and takes longer to notice.
Where I Start Instead
Before I open a design file, I want to understand the business. What you do, who you’re doing it for, what makes someone choose you over the other option they were considering, and what usually gets in the way of them saying yes.
Then I want to understand the visitor’s side of it. What they already know when they land on your site, what they still need to be told, what they’re unsure about, and what would make them comfortable enough to reach out. That’s not the same conversation as “what colors do you like,” and it usually surfaces things a mood board never would.
Only once that’s clear do I start thinking about structure, what pages exist, what each one needs to accomplish, what a visitor sees first and what they see next. Design comes after that, built to support decisions that have already been made, instead of decisions that get made up as we go. That order is the actual shape of how a project runs, not a step I skip when a timeline gets tight.
Design Still Has to Be Excellent
None of this means design is an afterthought, or that strategy is the real work and design is just decoration on top of it. The finished site still has to look genuinely good. Strategy tells you what a page needs to accomplish. Design is what makes someone actually want to read it, trust it, and stay on it long enough to take that next step. They’re not competing priorities. A strategy without strong design doesn’t get read. A design without strategy doesn’t say anything worth reading.
Why the Order Matters
Skip straight to design, and you end up making structural decisions by accident, buried inside visual ones. A homepage gets built beautifully, and only afterward does anyone ask who it’s written for, or what a visitor is supposed to do once they finish reading it. By then, those aren’t easy fixes. They’re baked into a layout that already looks finished, which makes them feel a lot more painful to change than they would have been on a whiteboard in week one.
It’s an easy trap to fall into: a homepage that looks completely professional, with a headline that could belong to five other businesses, because “what do we want it to look like” got answered before “who is this for” did. The site isn’t broken. It’s just answering a question nobody asked, dressed up well enough that it takes a while to notice, which is exactly how a website can look completely fine and still not be bringing in the right inquiries.
This Isn’t Extra Steps
This might sound like more process, another round of conversations before anything visible happens. It isn’t extra work stacked on top of a normal project, it’s the same total effort in a different order. The alternative isn’t a faster project, it’s the same thinking happening later, usually as a revision instead of a starting point, after a design already exists and now has to be undone to fix something that could have been settled on a whiteboard. Doing it first just means it happens once instead of twice. It’s the same reason a Website Assessment starts with figuring out what’s actually going on instead of jumping straight to a redesign, diagnosis first isn’t extra process, it’s what keeps you from fixing the wrong thing.
What This Looks Like in Practice
In a real project, this means the first real work isn’t a mood board, it’s a conversation, and sometimes a few of them. What’s working right now, what isn’t, who you want more of, what you’re tired of explaining over and over to people who land on your site confused. From there, the site gets mapped out before it gets designed: what each page is for, what order things need to happen in, what a visitor needs to know before they’re ready to take the next step, and which page is actually doing the heaviest lifting toward getting them to reach out.
That structure becomes the brief design has to work inside of, not a constraint on creativity, but the difference between a homepage that looks good and one that also does its job. By the time design starts, it’s not guessing at what might look nice. It’s building the version of “nice” that was already decided by what the business and the visitor both need.
Final Thoughts
A website that looks good and a website that works aren’t automatically the same thing, and starting with design is how you end up hoping they line up instead of making sure they do. If you’re starting a project and want it built in that order, structure and strategy first, design built to carry it, let’s talk about what that looks like for your business, or take a look at how that process has played out on past projects.
