Some time ago, Dr. Mitra from the Indian Institute of Technology Gandhinagar asked me a question that appeared straightforward on the surface: “How do startups prioritize features?”
He mentioned it in the context of a teaching case on founder-led decision-making being developed by faculty from a leading management institute. While we didn’t get the chance to discuss it then, the question stayed with me. It prompted deeper reflection on how product decisions are truly made in early-stage companies, especially when the path forward is far from obvious.
What initially seemed like a product management question turned out to be fundamentally about strategic decision-making.
Over time, I realized that the single question actually contains two very different problems:
1. Prioritizing Features Already on the Roadmap
This is an execution and sequencing challenge. In our case, we maintain a structured backlog organized into feature groups. Every sprint is focused on advancing a feature and delivering incremental value to users. The goal is to ship something usable rather than waiting for perfection.
This type of prioritization is relatively manageable because the overall direction of the product is already defined. You know what the product is meant to become, you’re simply deciding the order and pace of delivery.
Teams often rely on established frameworks here, such as:
Once the vision and strategy are clear, this becomes an optimization exercise.
2. Deciding Whether to Build Something Entirely New
This is significantly more complex. Every founder eventually faces ideas or requests that fall outside the original roadmap, sometimes something you had deliberately chosen not to build, and other times an exciting opportunity that challenges your core assumptions.
In one such situation, our team found that none of us fully trusted our individual instincts. Each option had strong arguments depending on the lens applied. To navigate this, we ran a structured design thinking workshop. Using Figma boards, we mapped out all the options, openly discussed trade-offs, and assigned weights to key decision factors.
This experience reinforced an important insight: Prioritizing features within a known direction is an operational challenge. Deciding whether the product should take a fundamentally different direction is a strategic one.
These are not two versions of the same decision — they are fundamentally different:
The first determines the pace of evolution.
The second determines whether you are evolving in the right direction.
Confusing the two can lead to scattered roadmaps, diluted focus, reactive decision-making, and ultimately, building the wrong product — even if you build it efficiently.
Looking back, the distinction between these two types of decisions has been valuable. Operational decisions keep the team moving forward with momentum. Strategic decisions protect the integrity and long-term potential of the company.
For founders and product leaders, developing the ability to recognize which type of decision you’re facing, and applying the appropriate mindset and process, is one of the highest-leverage skills in building a successful product.
I continue to learn from these challenges and would be interested in hearing how other founders and teams navigate similar situations.