Hey PMs! Quick question for you:
How do you decide when a feature is "too advanced" for MVP, even when it's objectively valuable?
I just wrote about this exact dilemma with our Hotspot Analysis & Decarbonization Module. Super cool feature, genuine user need, but adding it to MVP would have:
Delayed our entire launch
Created dependencies we couldn't manage
The hard truth: Not everything belongs in MVP, even when stakeholders really, really want it.
Wrote up the full story: 4 unexpected challenges, 4 hard-earned learnings, and why documentation saved our sanity: https://ektaghadle.substack.com/p/building-the-decarbonization-puzzle
Curious how others handle scope decisions for complex, multi-industry products? 🤔
