Tell A Better Story with Theme-Based Roadmap

So you’re in a condition where you have tons of features that you want to work on; but you’re stuck mapping them “the good way” into your roadmap? Well, we all do.

As a product manager, you map those features into time-bounded releases. Say, on Q1, you will be releasing this and that feature; for Q2 you will be releasing this and that feature, and so on. Be careful if you’re mapping your roadmap with features-only and having no crystal-clear goal, or just because you want to release something ‘cool’ every month for show off; or maybe your business users think it’s best to launch that feature based on their deepest feelings.

“We need to let go of the idea that we can enumerate a list of features that represents what we’ll do in the future. This idea is absurd” — Teresa Torres

Then comes the day when someone ask you “Why this? Why first?”; you might get yourself a short deep contemplation. As a product manager, an excuse of “because A told me to do so” does not exist. If you’re desperate, you might start making your own excuses; telling them that this feature will fix a problem but that’s just it — but well, it’s there prolly just to fix short-term problem. You’re not putting the big picture in mind: the product vision itself, and you might not solve the problem to where it needs fixing the most. This type of roadmap is often called the feature-based roadmap; and is best used under 3 conditions:

1. Your product is just getting started, so your focus is basically delivering core features.
2. Change of requirements rarely happens
3. Releases are time-bounded

Now if your product isn’t under that conditions, you might want to rework your roadmap since feature-based roadmap has its typical property where changes are hard. Your product must have the capabilities to cope up with the rapidly-changing trend. Think about those products who were once the top-notch product that exceeds expectations yet now it has become underrated products (Thought of a product in mind yet? No?). They stopped innovating because complacency felt amazing and the product stays within that zone. Moreover, the products created something that customer never asked for — hoping that the product itself can actually change customer’s behavior. So before your product end up the same way, you might want to contemplate to alexandra Adornetto’s saying: “To make one person the center of your world is bound to end in disaster. There are too many factors outside your control.”

So, what, actually; is a theme-based roadmap and how will it benefit my product?

Source: https://www.productplan.com/roadmaps-themes/

A theme-based roadmap is simply, a normal roadmap, but with a theme in it. Regarding the explanations, you can have some good readings here and here

By having a theme-based roadmap, you have a better way of explaining where your product wants to go; which successive steps you should take; and how it will support your product vision. Willy Anderson of Blibli.com gave a good illustration to me when he did his presentation:

Imagine, just imagine, your boss told you to enjoy your holiday with imaginably infinite money and time (How i wish this imaginary session actually becomes real). The first thing that goes to your mind might be where you should go enjoy your holiday; so let’s say you have decided to enjoy your holiday by having a vacation in Bali because it’s the time where the tide is pretty good for surfing.

To enjoy your holiday in Bali; you have two alternatives:

1. Enjoy what Bali can offer, of which you can also elaborate into:

• Enjoy what Bali can offer FAST (take a direct flight without any transit)
• Enjoy what Bali can offer CHEAP (taking flight with several transits)

2. Enjoy the journey to Bali, of which you can also elaborate into:

• Enjoy the trip to Bali and enjoy the beautiful sceneries along the trip
• Enjoy the trip to Bali and enjoy the many culinary spots along the trip

Each alternative will create different experience and story for you to tell, but both alternatives will foster you to enjoy your holiday in Bali.

Notice the bold text highlighted in previous illustration. When your boss told you to enjoy your holiday, it is your company vision, the vision that you need to always keep in mind of. When you decided to enjoy your holiday in Bali, that is your business strategy, the mission you want to work on to achieve company vision. The two alternatives on how you want to enjoy your holiday are your Product Vision, the goal that you seek to comply your business strategy. Finally, to achieve your product vision, the elaboration of your product vision is the roadmap, with theme added onto it.

By having a theme in your roadmap, you can create a series of storylines that builds up a story. In the end, anything that you plan will look like a bedtime storybook that you can easily explain to anyone.

So how do you build your own Theme-based roadmap?

Step 1 — Collect Pain Points

Ensure that you solve the right problem by detecting the pain points your user are experiencing on your product by looking at your data, doing surveys, interviews, etc (Always listen to your customer!). Only when equipped with the right data can you get a clear understanding on the root problem; to hence create an effective release backlog.

Step 2— Grouping and Analyzing

With those list of feature/ideas/request that you have on the menu, group them into several silos and analyze the group you made to answer the question below:

• Is this the biggest pain point that we need to solve?
• What will happen if we focus on this group?
• What value will this group bring to our company? Does it comply with company’s vision?
• Can we delay? If the answer is Yes, you should delay it right now!

Step 3— Discuss, Negotiate, Repeat

Having your plan done from Step 2, discuss it with your user and get the buy in. If they don’t like your strategy, make sure you get feedback. Work again on your plan, and repeat Step 3 for a maximum of 3 cycles. If in the end agreement has not taken place yet, escalate this issue to upper management.

https://blog.zoho.com/wp-content/uploads/2017/03/24Slides-5.gif

I’m done with my roadmap. What’s next?

Show and explain your roadmap to everyone, but don’t forget to always accept feedback/requests, then explain them why those previous requests were not prioritized on your current roadmap. Having received all those feedback, groom your backlog.

Tips on your backlog grooming:

Plan your backlog release up to maximum of 2 release cycles. Anything that takes more than 2 cycle will have 80% chance to be dropped/delayed.

Make sure that the backlog that you are going to develop comply with your roadmap theme

If you have a backlog that doesn’t match the roadmap, prepare data needed for justification

Having all being set and on progress, review your roadmap once in a while. Roman Pichler shared his rule of thumbs on reviewing roadmap based on maturity of product vs stability of market.

Source: Roman Pichler: Agile Product Roadmaps

“There is nothing permanent except change” — Heraclitus

That’s it for this writing, I hope you can start putting a theme for your roadmap. Cheerio~

If you’re interested in applying for a full-time position or intern as a Product Manager, Blibli.com is currently hiring! Send your resume to recruitment@blibli.com and get the chance to work with other Product Managers with their own unique stories.