Designer resetting a cluttered product roadmap board
Building Pastel

Startup Design Hack: Resetting the Product Roadmap

A long list of requested and validated features can be stressful to work with. Here is what helps.
Aloke Pillai, product designer at Pastel
Aloke Pillai

When you have a small product design team, a long list of requested and validated features can be stressful to work with. They promise the happiness of your customers and the future growth of your company.

As the only designer at Pastel, it is a constant challenge I battle with. How do you stay on top of all the things that people want while understanding which ones to work on first?

Here is something that’s been working for us.

We reset the list every month and treat it as a product feedback

What if someone falls through the cracks? Won’t people be mad?

If it is an important feature, it will be truly hard to miss. Much like how Inbox Zero helps ease a lot of people, a true reset helps you ask what is truly important and not what are we behind on. I’ve seen customer requests go from a ‘burning need’ to a ‘nice to have’ because they found a workaround or changed their behaviour altogether.

Shiny things approaching: keeping stakeholder feedback from derailing priorities

Let’s be honest. Most of the harm done to a roadmap is self-inflicted. When we come up with great ideas, they enter the rollercoaster of joy and sorrow. Doing a roadmap reset protects us against our well-intentioned enthusiasm and gets us to focus on what is needed the most.

Big vs. small features

Prioritization is easy when the list is a few features long. It becomes an impossible game of Jenga when it goes over 100’s of features. What if all the Jenga pieces were different sizes!

That’s usually what a roadmap looks like. Big long term tasks like designing integrations to other tools are always lingering co-mingle with small UX tweaks that delight the user.

Breaking up big tasks into smaller actionable ones helps us tackle this problem. If something is unknown, it is common for our team to spend a day in exploration until the task is more defined. That exploration is seen as research time as a small task.

Tools like Pastel make it easier to capture and prioritize this kind of feedback without it getting buried in Slack threads. Try it today for free!

FAQ

What is a product roadmap reset and why would a team do one?

A roadmap reset means periodically clearing the list and re-asking what is truly important right now, rather than what the team is behind on. Much like Inbox Zero, it relieves the pressure of a growing backlog and protects the team against its own well-intentioned enthusiasm.

How do you prioritize a product backlog with hundreds of feature requests?

Prioritization is easy when the list is a few features long, but becomes an impossible game of Jenga past a hundred, especially when big long-term tasks are mixed in with small UX tweaks. The post's answer is to reset regularly and break large items into smaller, comparable pieces instead of trying to rank the whole pile.

How should a small product or design team manage a long list of customer feedback and feature requests?

Rather than trying to stay on top of everything at once, do a regular reset and let what's genuinely important resurface. A long list of requested and validated features promises customer happiness and growth, which is exactly what makes it stressful for a small team to carry indefinitely.

Won't important feature requests fall through the cracks if the roadmap resets?

If a feature is truly important, it will be genuinely hard to miss, because customers keep bringing it up. The reset filters out what only felt urgent at the time.

Do urgent customer requests always stay urgent?

No. Customer requests have gone from a "burning need" to a "nice to have" because users found a workaround or changed their behavior altogether, which is part of why resetting beats carries every old request forward.

How often should you review or reset your product roadmap?

The post describes doing it as a recurring practice, frequently enough that the list never grows into an unmanageable backlog and the team keeps re-asking what matters most right now.

Why do product roadmaps become overwhelming in the first place?

Most of the harm done to a roadmap is self-inflicted. Every great idea the team gets excited about enters the list, and without a reset habit, enthusiasm steadily turns the roadmap into an unmanageable pile.

How should large, long-term tasks be handled on a roadmap?

Break them up into smaller actionable pieces. Big items like designing integrations to other tools shouldn't sit on the list co-mingled with small UX tweaks, because pieces of wildly different sizes make prioritization nearly impossible.

What should a team do with a roadmap task that's still unclear or undefined?

Spend a day in exploration until the task is more defined, and treat that exploration as its own small research task on the roadmap rather than committing to unscoped work.

How does a roadmap reset change the questions a team asks?

It shifts the conversation from "what are we behind on?" to "what is truly important?", which is a healthier framing for deciding what a small team should build next.

Does resetting the roadmap mean ignoring customer feedback?

No. Requests stay validated and welcome; the reset just stops old requests from automatically claiming priority. Feedback that keeps coming back earns its place on the next cycle.

Page Content

  1. example

Try Pastel for free

No contracts, no credit card.
Get started now