Most tech founders think their organisation has a product vision. What they actually have is a feature list.

When your product organisation talks about vision, they are usually talking about the "what": which feature to ship, which backlog item to prioritise, or which request from the last customer call to build.

That isn't a product vision. A product vision is founded on the "why". It requires your organisation to think at both a micro and a macro level. It requires you to develop belief in order to stick to who you are: your brands reason to exist, your niche, your audience (key persona), and their killer pain points.

Without that, you cannot say no to anything. So you just keep adding: adding features, adding frameworks, and adding PMs to manage those features. Suddenly, at 30 employees, you become as complex as a big corporation.

Trying to solve everyone's problems solves no ones problem. Building a vision (the why) and working around it is essential. It needs to become your backbone. This is a required condition, but it is still not sufficient.

Why? Because at this stage, you have only solved the feature selection. Now you have just a fraction of your product vision correct.

There is a structural misconception that desirability comes down to capabilities alone, and that these capabilities must translate into features.

Let's consider a Windows laptop versus a Mac. Both have similar feature sets. Why does a Mac command a premium?

• Technical Execution: system stability, built-in security, and zero-latency performance.

• Experience Flow: seamless ecosystem integration, intuitive micro-interactions, and visual consistency that feels premium.

You dont buy a Mac for more features; you buy it for superior experience and execution.

If your roadmap is just adding new capabilities, meaning new features, you’ve built a product organisation that acts like Windows instead of Apple. A complete product vision rests on three equal pillars: Experience, Capability, Quality.

The reason you are trapped in features is structural. You centralise customer insights, product vision, and orchestration inside a single person, usually a Product Manager. Giving one role absolute power kills open debate. It creates cross-functional friction or turns other functions into passive execution units. As a consequence, your product vision becomes a mere reflection of that single persons profile or its team.

And this is the exact organisational model that Microsoft followed.

Apple (under Jobs and Ive) didnt work this way. Neither did McLaren (2016–19) or Lotus (2019–22) during their scale-up stages. They built organisations where desirability was carried equally by three distinct profiles: Experience, Capability, Quality, forcing each function to reach excellence.

Which of these three pillars is currently neglected in your roadmap?