Design Isn't the Step After Strategy. It's How You Get There

A few years ago, a client hired me to redesign their homepage. Before I started, I suggested we do a strategy session first. The word "strategy" seemed to land wrong. He pushed back, said it felt like unnecessary work, and asked me to just take a shot at the designs.

I told him we could do that, but warned the project might take longer without it. We agreed to work hourly and move forward.

First round of designs: the two founders and their in-house person all had different reactions. Different opinions, different directions, different ideas about what the page should do. I let them talk, then asked one question: what does your ideal user actually need here?

Silence.

They didn't know. And they hadn't realized, until that moment, that they each wanted something different from each other too. A two-hour workshop and some lightweight research on my end would have surfaced all of that before a single pixel got moved. Instead, we got there eventually, and the homepage turned out well, but everyone spent more time than they needed to.

That's what it looks like when design gets used as a starting point instead of strategy.

When the Design Problem Isn't Really a Design Problem

When a brand or product isn't performing the way a founder hoped, design is usually the first thing that gets flagged. The site looks outdated. The app feels clunky. The packaging doesn't match the product. These are real observations, and they're worth fixing. But they're often symptoms of something that sits further upstream.

The real ask tends to sound like one of these:

• We're not converting and we think the site is the problem
• We raised a round and now the brand needs to look the part
• Our users aren't coming back and we're not sure why
• We need to look more credible before our next pitch

None of these are design briefs. They're business problems with a design-shaped layer on top. That layer is real and it matters. But peeling it back without looking at what's underneath it is where projects go sideways, where founders end up in a room disagreeing about button colors when the actual problem is they haven't decided who they're designing for yet.

Design can't answer that question on its own. But a good discovery process, the kind that includes the right conversations before anything gets built, will make sure it gets asked and answered before a single screen gets designed.

Why Design Becomes the Default Fix

There's a reason founders reach for design when something isn't working. Design feels actionable. You can brief it, budget for it, launch it, point to it in a deck. It looks like progress because in many ways it is progress.

Strategy is harder to hold. It requires sitting with questions that don't have clean answers yet. Who exactly is this for? Why would they choose us over doing nothing? What does this product need to communicate in the first ten seconds? These aren't uncomfortable questions because founders are avoiding them. They're uncomfortable because they're genuinely hard, and the pressure to ship, grow, and show traction doesn't leave much room for sitting with uncertainty.

So design becomes the thing you do instead. A new homepage instead of a positioning conversation. A rebrand instead of an audience audit. A UI refresh instead of figuring out why users are dropping off after day three.

The work still gets done. The site goes live. The app gets updated. But six months later the numbers haven't moved, and nobody's quite sure why, because the thing that actually needed attention never got it.

Strategy Isn't a Prerequisite for Design. It's Part of It

Here's the part that usually gets left out of this conversation: strategy isn't something that happens before design and then gets handed off. In a well-run engagement, it's built into the process itself.

A discovery session surfaces assumptions that haven't been tested yet. Asking the right questions before opening Figma will often reveal that two co-founders have different ideas about who the product is for. A brand audit makes it visible when the problem isn't aesthetic at all, it's that the messaging on the site doesn't match what the product actually does. Mapping the full customer journey shows where trust is breaking down, and whether that's happening in the UI, in the copy, in the post-purchase experience, or somewhere else entirely.

This is what good design work does. It doesn't decorate a strategy that already exists. It makes the gaps in that strategy impossible to ignore, and it creates the conditions for founders to make better decisions about what to fix and in what order.

A femtech brand on Shopify with flat conversion might come in thinking they need new product photography. What the audit surfaces is that the copy is speaking to the wrong person, the checkout flow is creating unnecessary friction, and the brand across their site, their emails, and their packaging all feel like they were made by three different companies. The photography was fine. The strategy needed attention.

Design didn't replace that work. It revealed it.

How to Get the Most Out of Working With a Designer

Before you bring in a designer, there are a few questions worth sitting with. Not because you need to have everything figured out first, but because your answers will shape how useful the engagement actually is.

Do you know who you're designing for, specifically? Not "women 25 to 45" but the person who has the problem your product solves, and why they haven't solved it yet.

Do you have a hypothesis about what isn't working? It doesn't need to be right. But having one means you're coming in as a thinking partner, not just a client waiting for a deliverable.

Are you prepared to act on what the process surfaces, even if it points somewhere uncomfortable? A good discovery process will sometimes confirm what you suspected. Sometimes it will tell you something you didn't want to hear. The value is in being willing to do something with it either way.

You don't need all the answers before the work starts. That's partly what the process is for. But the founders who get the most out of a design engagement are the ones who show up curious, not convinced they already know the answer.

Design Isn't the Step After Strategy. It's How You Get There.

Good design work was never just about how something looks. At its best, it's a process that forces clarity, surfaces assumptions, and gives founders a much sharper picture of what they're actually working with.

The band-aid instinct makes sense. When something isn't working, you want to do something. Design feels like doing something. But the designers worth working with won't let you skip the thinking. They'll build it into the process, ask the questions that need asking, and make sure the work that gets done is solving the right problem.

If you're a femtech founder and something isn't converting, isn't retaining, or just doesn't feel cohesive, the answer isn't to hold off on design until you have everything figured out. It's to find a designer who helps you figure it out as part of the work.

‍