Your logo is not your brand.

Design · 4 min read

A client arrived at our first meeting with a mood board, a colour palette, three logo variations, and a set of brand guidelines. He'd spent weeks refining all of it. What he didn't have was a single screen design. No user flow. No wireframes. No idea of what the app actually did when someone opened it. He'd built the wrapper before building the thing inside it.

This happens more often than you'd think. People start with the logo because it feels productive. It's visual. It's tangible. You can show it to friends and get feedback. But a logo is the last thing you need, not the first. And confusing a logo with a brand is one of the most common mistakes I see from first-time founders.

A brand is a feeling, not a file

Marty Neumeier put it simply in The Brand Gap: a brand is a person's gut feeling about a product. Not a logo. Not a colour scheme. Not a typeface. A gut feeling. That feeling comes from experience. It comes from how the app behaves when things go right. It comes from how the app behaves when things go wrong. It comes from whether the app respected your time or wasted it.

Think about the apps you love using. Do you love them because of their logo? Or do you love them because they load fast, do what you expect, and never make you feel stupid? The brand is built in those moments. Every interaction, every screen transition, every error message, every confirmation. That's where trust gets earned or lost. The logo just sits in the corner while all of this happens.

Another client had a beautiful logo and a terrible onboarding flow. Users downloaded the app, got confused in the first thirty seconds, and deleted it. They never even noticed the logo. The brand impression they walked away with was "confusing" and "not worth my time." No amount of visual polish was going to fix that.

Design the experience first

I always push clients to focus on the user flow before anything visual. What happens when someone opens the app for the first time? What's the first thing they need to do? How many taps does it take? What happens when they make a mistake? These questions build your brand far more than choosing between two shades of blue ever will.

The speed of your app is a brand decision. The clarity of your labels is a brand decision. The tone of your error messages is a brand decision. When the app says "something went wrong" versus "we couldn't save that, but your data is safe," those are two completely different brand experiences. One feels careless. The other feels considered. Neither of them involves a logo.

I had a client who went back and forth on logo options for three weeks. In that same time, we could have mapped the entire user journey and built the first round of wireframes. When we finally moved past the logo conversation and into the actual design work, the brand emerged naturally from the product decisions we made. The colours, the typography, the visual identity all followed from the experience. Not the other way around.

When the logo actually matters

I'm not saying logos don't matter at all. They do. But they matter at the end of the process, not the beginning. Once you know what the app does, how it feels, and what experience you want users to have, the logo becomes obvious. It's a visual shorthand for something that already exists. Designing a logo before the product is like writing a movie poster tagline before you've written the script.

So if you're sitting on three logo variations and zero wireframes, I'd encourage you to flip the order. Put the logo aside. Name the app if you need to, but spend your energy on the screens people will actually use. Design the flow. Test the flow. Refine the flow. Then, once the product has a personality, give it a face. That's when the logo earns its place. Not before.

Sources
The Brand Gap (Marty Neumeier, 2003) - A brand is a person's gut feeling about a product, not a visual mark or logo.

Related blog posts:

When your app name makes a promise →

How to name your app without overthinking it →

Simplicity is harder to sell than complexity →