How to think about your product before you design it
Before Figma, before brand, before copy: the thinking that prevents six months of expensive drift.
There’s a version of this post that is twenty frameworks long. This isn’t it. In our experience, most clients who are about to spend real money on design don’t need a framework — they need a handful of honest answers before they start. Here are the questions we ask, in the order we ask them.
1. Who is this for, specifically?
Not ‘SMBs in North America.’ A person. A role at a specific scale of company at a specific moment. The more specific, the more design decisions resolve themselves. Vague audiences produce vague products.
A useful trick: describe the last three times this person felt the problem you solve. If you can’t, you don’t know them yet.
2. What is the moment you are interrupting?
Products don’t get used in a vacuum. They get used between other things — in a 3-minute window between meetings, at the end of a long day, on a phone in a taxi. The moment shapes everything: the copy length, the density of the UI, whether the thing needs to be understood in 10 seconds or 10 minutes.
Design made for no moment feels generic. Design made for a specific moment feels considered — even when it’s simple.
“The question isn’t ‘what should the product do?’ It’s ‘what is happening the minute before someone opens it?’”
3. What is the thing it refuses to be?
This is the one founders hate. Every product is defined as much by what it refuses as by what it does. A product that won’t say no to anyone becomes muddy. A product with a clear no is sharp.
‘We won’t serve enterprise.’ ‘We won’t add a chat feature.’ ‘We won’t write for beginners.’ Each no is a point of focus.
4. What does it replace?
Every new product replaces something — even if that something is ‘doing nothing.’ Name it. If your product replaces a spreadsheet, it competes with the comfort of a spreadsheet. If it replaces a consultant, it competes with the intimacy of a human answer. Those are wildly different design problems.
You can’t design against a rival you haven’t named.
5. What does ‘working’ look like?
Before a single screen exists, describe the week the product is working perfectly. Who is using it? How often? For what? What do they say after? This is not a mission statement. It’s a picture of success concrete enough to measure.
Without it, ‘better design’ becomes an infinite problem. With it, every design choice can be tested: does this get us closer to that week?
What changes when you have the answers
The product gets smaller. Features get cut. Copy gets sharper. The team stops arguing about personal taste because the answers pre-decide most of it. Design becomes execution instead of invention.
The founders we work with who do this pre-work ship faster, spend less, and end up with products that feel inevitable. Not because we were better, but because the thinking underneath was already clean.
Design is expensive. Thinking is cheap. Pay for the thinking first.