There’s a moment that sticks in my head.
A founder I was working with years ago had spent three months refining their product idea. Wireframes, mockups, even the copy — all done. But something wasn’t quite clicking.
The flow was clunky. The offer felt vague. The team was frustrated.
And eventually, I realised what was going on:
They had approached the entire thing like a tech spec.
Linear. Locked in. Rigid.
No room for iteration. No time to question assumptions.
They were building a solution before understanding the shape of the problem.
When I suggested we pause and map the actual user journey, they looked at me like I was suggesting we scrap everything.
But here’s the thing. Thinking like a designer isn’t about throwing ideas away.
It’s about creating space for better ones to emerge — ideas that are grounded in clarity, context, and use.
And if you’re a founder, or anyone making decisions about what gets built, learning to think like a designer might be the single most useful shift you can make.
What does it mean to think like a designer?
It doesn’t mean learning Figma.
It doesn’t mean spending hours picking fonts.
And it definitely doesn’t mean obsessing over how things look.
Thinking like a designer means thinking in terms of people, flow, and consequence.
It means starting with the question, not the answer.
It means solving for real-world behaviour, not internal preferences.
It’s about:
- Clarifying the actual problem
- Making ideas visible so they can be tested
- Expecting iteration, not perfection
- Making decisions based on flow, not features
- Communicating so that others can act
Designers, when they’re doing it well, are trained to reduce friction.
To make things easier to understand. Easier to use. Easier to trust.
And that mindset?
It doesn’t just belong in the design team. It belongs in product strategy, growth planning, investor decks, and operations too.
Where founders often get stuck
Founders are problem solvers by nature.
You see a gap, a broken process, a need — and you act. That’s a good instinct.
But in the rush to act, it’s easy to bypass the pause.
The “hang on — is this the right shape of solution?” moment.
The step where you map the journey, not just the idea.
I’ve seen startups burn six months building the wrong thing — not because the idea was bad, but because they never validated the logic between steps. They assumed the user would behave a certain way. That they’d see the value, click the button, convert.
But real life isn’t a pitch deck.
Design thinking forces you to simulate reality.
To ask:
- What happens before this screen?
- What is the user trying to do?
- What do they already know?
- What will stop them?
And the moment you think that way, everything starts to shift.
Design is a mindset, not a deliverable
This is something I wish more founders understood.
Design isn’t what you get at the end.
It’s how you shape what happens from the beginning.
It’s a decision-making tool. A communication layer. A method for removing confusion before it costs you.
It’s not about making things look pretty.
It’s about making things clear.
Because clarity leads to trust.
Trust leads to momentum.
Momentum leads to results.
The best founders I’ve worked with all share one trait
They don’t think of design as decoration.
They think of it as navigation.
They ask better questions.
They’re comfortable showing work-in-progress.
They’re quick to test and faster to learn.
They don’t fall in love with their ideas — they fall in love with solving the right problem.
And funnily enough, those founders usually need less design work in the long run.
Because they don’t waste time backtracking.
They make better decisions up front.
You don’t need to become a designer
But you do need to adopt the mindset.
Here’s how to start:
- Stop asking “What should this look like?”
Start asking “What should this do for the person using it?” - Instead of explaining everything, try showing it.
Whiteboard it. Sketch it. Let others see your thinking. - Build small loops.
Can you test one part of your flow before building the whole thing? - Get comfortable with iteration.
Done is better than perfect, but tested is better than both. - Design for behaviour, not just belief.
What do you want people to do next? Is that obvious to them?
Final thought
Thinking like a designer won’t magically make your product succeed.
But it will dramatically reduce the number of wrong turns you take getting there.
Because when you shift from planning in documents to mapping in flows,
When you stop treating design like the final polish and start using it as your early lens,
You gain something far more useful than a great layout.
You gain clarity.
And clarity, in any business, is an edge most people never develop.
