Experience Is the Product—So Why Don’t Designers Lead It?
Updated: Sep 27
Rethinking product leadership in a world where experience defines value
Most product leaders today come from backgrounds in business, engineering, computer science, economics, or marketing. These disciplines bring essential strengths - strategy, execution, scale, and efficiency. Yet there is a quiet irony embedded in this structure:
None of these educations fundamentally train people to create experiences.
And in a B2C-driven world, experience is no longer a layer added to a product. Experience is the product.
Experience Is the Outcome, Not a By-Product
Products and services are often discussed in terms of features, performance, technology, or innovation. But these are inputs, not outcomes. What customers actually live with - what they remember, trust, complain about, or recommend - is the experience.
Experience is what creates emotional attachment.
It is what builds loyalty, habit, and meaning.
Technology, engineering, AI, operations, and business strategy should all exist in service of a clearly intended experience. When that intention is missing, products drift. They accumulate features, showcase capability, and optimize metrics - yet fail to connect.
Apple’s early success is a well-known example, not because of superior technology alone, but because experience was treated as the organizing principle. Innovation happened first at the experience level. Technology and engineering followed that vision, not the other way around.
When Experience Doesn’t Lead, Products Reveal Their Bias
In many organisations today, product leadership is dominated by professionals from technology, engineering, or sales backgrounds. Predictably, products begin to reflect those strengths—and their blind spots.
A common example is the touchscreen-heavy dashboard in modern cars. From a technology perspective, it signals progress and flexibility. From an experience perspective, it often introduces distraction, cognitive load, and safety risks.
A designer trained in experience would instinctively understand that driving is a tactile, eyes-free activity. Physical controls, muscle memory, and feedback matter more than visual novelty. The problem here isn’t technology - it’s leadership that optimises for capability rather than lived experience.
The same pattern appears in concealed door handles, over-automated interfaces, and feature-dense products that look innovative but feel frustrating in daily use.
These decisions are not harmless. They consume time, engineering effort, and resources - often delivering innovation that users neither need nor value.
AI: The Latest Mirror of Experience Blindness
AI is perhaps the most ironic and timely example of this problem.
Today, businesses are racing to “infuse AI” into products, driven by hype, investor narratives, and fear of being left behind. In many cases, AI has become a solution looking for a problem.
We already see:
Chatbots that block access instead of helping
Automation without trust or transparency
Intelligence that increases complexity rather than reducing it
AI is rarely the issue. Experience-less leadership is.
When AI is added without a clear experiential intent, it becomes noise - another layer users must adapt to. This is how technology bubbles form: not because the technology lacks potential, but because its adoption is disconnected from human reality.
AI can create immense value when it reduces friction, anticipates needs, and quietly supports users. But that requires leaders to ask first: What experience are we trying to create? - not Where can we add AI?
So, Who Should Lead Products?
If experience is the outcome we care about, the question of leadership becomes unavoidable.
Designers are the only professionals trained explicitly to think in experiences.
They work with:
Human behaviour and emotion
Context, constraints, and trade-offs
End-to-end journeys, not isolated features
Meaning, not just functionality
Designers don’t start with what can we build? They start with what should this feel like?
Importantly, good designers are not detached idealists. They operate deeply within development constraints. They understand feasibility, iteration, and cross-functional collaboration. They are translators between human needs and organisational capability.
This makes designers uniquely suited for product leadership - not because they know everything, but because they know what everything should serve.
The Real Gap Isn’t Capability—It’s Opportunity
The industry’s problem is not a lack of talented designers. It’s a lack of pathways for designers to lead. We need:
Programs that give designers fluency in business, technology, and strategy
Platforms where designers can practice decision-making at a product and organisational level
Companies willing to trust experience-led thinking at the top
This isn’t about turning designers into engineers or MBAs. It’s about enabling them to lead with experience while collaborating with specialists who bring depth in other domains.
Experience Is Not a Department
Experience cannot be delegated to a design team at the end of a roadmap. It cannot be “reviewed” or “polished” after core decisions are made.
Experience must be owned by leadership.
The future of meaningful products will not be shaped by who ships the most features or adopts the latest technology first. It will be shaped by who understands people best.
Perhaps it’s time we stop asking whether designers can become product leaders - and start questioning why they so rarely are.
Comments