Why senior designers should build products, not just decks
There is an uncomfortable truth in our industry that many people avoid saying out loud but one that’s getting louder because of AI.
A lot of senior designers spend more time talking about products than actually building them.
They produce strategy decks, vision presentations, maturity frameworks, operating models and service maps.
The slides are polished. The thinking sounds convincing. The language feels strategic.
But somewhere along the way, something important gets lost.
Distance from the product itself.
The further you move from the product, the easier everything looks
When you sit close to the product, reality is messy.
Features take longer than expected.
Users behave differently from what you predicted.
Technical constraints appear everywhere.
Business trade-offs constantly shift priorities.
Nothing is ever as clean as the diagram in the deck.
But when you move further away from the product, something interesting happens. The work begins to look simpler. It becomes easier to design perfect operating models and elegant frameworks because you are no longer dealing with the friction of actually shipping something.
Strategy becomes theoretical.
Slides are safe. Products are not.
Creating a strategy presentation is low risk.
If the outcome fails, there are many explanations.
The organisation was not ready, leadership did not support the vision or engineering could not execute.
But when you build a product yourself, the feedback loop becomes brutally honest.
People either use it or they do not.
They either pay for it or they do not.
No deck can hide that reality.
Shipping a real product removes abstraction. It forces you to confront the difference between good ideas and working products.
Building products changes how you design
The moment you start owning something real, your perspective shifts.
You start caring about things that rarely appear in design strategy discussions.
- Pricing models
- Retention
- Customer acquisition
- Support requests
- Performance
- Conversion
You realise that a beautiful experience is only one small part of a product’s success.
A product also needs to be discoverable, sustainable, accessible and commercially viable.
That is why many of the best product thinkers are people who have built something themselves. They have felt the pressure of making something work in the real world.
Designers who ship products develop sharper judgement
Building products forces decisions.
You cannot endlessly explore options. At some point you must pick one direction and release it.
This creates a kind of judgement that is hard to develop through presentations alone.
You start to recognise:
- Which ideas are worth pursuing.
- Which problems are actually painful for users.
- Which features are unnecessary complexity.
- Which trade-offs matter.
You also learn something important about users.
People rarely behave the way we expect, and they rarely ever do what you would do in your own product.
That lesson alone is worth more than most design strategy workshops.
It also changes how you lead teams
When leaders build things themselves, they gain empathy for the people doing the work.
- They understand the weight of deadlines.
- The complexity of implementation.
- The frustration of edge cases.
- The compromises that happen between design, engineering and product.
That experience makes conversations more grounded.
Instead of abstract instructions about “raising the quality bar”, the discussion becomes practical. The quality bar is baked in so the focus shifts to solving real constraints rather than describing ideal outcomes.
Teams notice the difference immediately.
This is not about designers becoming developers
Building products does not mean every designer needs to become a full-time engineer.
It means understanding how products actually come into existence and not just doing ‘your part’.
Today, the barrier to building something is lower than it has ever been. Tools, platforms and AI systems allow designers to prototype, launch and test ideas faster than ever before.
You do not need to build the next global platform.
You just need to ship something real.
Because products teach lessons slides never will
The most valuable product lessons rarely come from frameworks.
They come from moments like these.
Launching something and hearing silence from the market.
Watching a feature you loved get ignored by users.
Seeing a small change dramatically improve adoption.
Realising the problem you thought was important does not matter to customers at all.
Those lessons reshape how you think about design.
And once you have experienced them, you start approaching product strategy very differently.
The best design leaders stay close to the work
Great design leadership is not about moving further away from the product.
It is about staying connected to the reality of how products are built, used and sustained.
The leaders who remain curious enough to build things themselves often develop sharper instincts, stronger credibility and more practical thinking.
Not because they have the best slides.
But because they understand what it actually takes to make something real.
And that understanding changes everything.