Product design for startups: what we learned in 15 years
Notes on product design when the team is small, time is short, and the pressure to grow is real.
Working with startups is one of the most interesting parts of our practice. The constraints are real: limited time, a small team, and an urgent need to learn from the market. These are some of the ideas we have tested repeatedly over the years.
1. Start with the problem, not the solution
The temptation to jump into Figma is strong, but every hour spent understanding the problem saves days of iteration. A good discovery session changes the rest of the project.
2. Design the small version, not the big one
The first version should be as small as possible while still being useful. Prioritize flow over the number of screens. Remove what is unnecessary and discover what is missing through use.
3. Build a system from day one
You do not need a complete design system immediately. You do need shared criteria: tokens, base components, and usage rules. This prevents visual debt from growing until it becomes unmanageable.
4. Design with the development team
The best product is the one that can be built and maintained. When design and code work closely together, decisions improve and delivery comes sooner.
5. Measure after launch
A product starts learning when people begin using it. The first version is a hypothesis. Build the second version with data rather than intuition.
Closing thoughts
Product design is, above all, a practice of reduction: fewer assumptions, fewer screens, and fewer uncertainties. The rest is execution.