Blog 14 · experience strategy

Your roadmap is a list of bets nobody has admitted are bets

Pranjal Chawan
Pranjal ChawanUX leader · LinkedIn

Look at the next item on your roadmap. Now answer three questions.

What do you believe it will change? For whom? And what would convince you that you were wrong?

If those answers are hard to find, you do not have a strategy. You have a delivery schedule.

That is not a criticism. Most organisations are busy, and delivery schedules feel like progress. I have seen a trucking app built exactly to specification, with every requested feature shipped, and still used by only 30% of its audience. Nobody had failed at delivery. The plan had simply never asked why a driver would care.

Strategy is what you choose not to do

Product strategy asks where the business should compete. Experience strategy asks what it should feel like to be a customer, and why they should choose you. The two need each other.

A good experience strategy fits on one page and answers these questions:

QuestionExample of a useful answer
Who is this for first?A specific, evidence-based audience
What progress do they want?The real goal, in their words
What gets in the way?Effort, doubt, lack of motivation
Where will we be different?One or two clear choices
What will we stop doing?Named items, not vague intent
How will we measure it?User and business measures together

The stop-doing line is the one that reveals whether leadership is serious.

Two projects, one lesson

My two public case studies look different on the surface. One was a bank's Fixed Deposit journey. The other was a driver app in the UK. In both cases, the breakthrough was a strategic correction rather than a new screen.

For the bank, the strategy changed from a logical audience to the real one. Daily bookings rose about 60%.

For the driver app, the strategy changed from adding functions to creating motivation. Usage rose from 30% to 90%.

In each case, the most useful thing we did was change the question.

How I build an experience strategy

  1. Understand the business. Talk to leaders about goals, constraints and fears.
  2. Gather the evidence. Bring together analytics, user research and competitive benchmarking.
  3. Name the tension. Find the gap between what the company believes and what customers do.
  4. Make a few clear bets. State each as a hypothesis with a measure of success.
  5. Test before scaling. Use small pilots to learn cheaply.
  6. Turn it into a roadmap. Now the roadmap has a reason to exist.

Strategy belongs at the top table

McKinsey's research on design value found that the best financial performers treated design as a top-management issue. Design conversations that stay in middle management rarely shape what a company chooses to do.

I like to help designers join that conversation by speaking the language of choices and risk, while keeping the customer's voice in the room.

Questions people ask

What is experience strategy? It is a plan for the experience a company wants customers to have, based on evidence, business goals and clear choices.

How is experience strategy different from a product roadmap? Strategy explains who you serve and why. A roadmap sets out what you will do and when.

What would you stop doing?

If your roadmap is full and your direction feels fuzzy, let's have a chat. I am at pranjal.productmind@gmail.com, and these are my favourite conversations.

© 2026 Pranjal Chawan. All rights reserved.