“Saying No!!”- The declutter every PM needs.
Every product manager dreams of saying yes to every idea.But the best PMs build their careers on the art of saying “no.” Because every “yes” costs time, focus, and sometimes the product’s soul. When I first started exploring product management, I thought PMs were idea machines — always brainstorming, adding more, building more.
Great product management is less about building and more about filtering. It’s not about how many features you can push; it’s about how many you can confidently reject. The Hidden Skill: Saying “No” Gracefully.
Every day, PMs face a flood of ideas — from users, engineers, marketing, even their own late-night “what if” thoughts.
The challenge isn’t collecting ideas. It’s deciding which ones truly deserve your team’s time and focus.
Saying “no” doesn’t make you rigid — it makes you responsible.
Because every feature you build
- Adds complexity
- Demands maintenance
- Risks confusing users if it doesn’t align with the core vision.
A great PM knows that every “yes” must earn its place. Frameworks Help, But Judgment Wins
Frameworks like RICE (Reach, Impact, Confidence, Effort) or MoSCoW (Must, Should, Could, Won’t) bring order to chaos.
They help quantify what feels subjective. But even the best framework can’t replace judgment — your instinct for what truly matters to users. Sometimes, data says one thing while empathy says another.
The magic of product management lies in balancing both. For example, Data might say users click more on short videos.But empathy might reveal they need long-form trust-building content before buying. Good PMs look beyond numbers; they look at narratives.
Think about Instagram. If you were in the product team, you could easily pitch a hundred ideas —
Polls, Groups, Filters for Reels, Advanced Search, Custom Themes... Yet Instagram keeps its interface clean.
That simplicity is intentional — a product of countless things they chose not to build. Because clutter kills usability. And great PMs know that every “add” must justify the attention tax it demands from users. When evaluating a feature, ask:
Get Aseem Singh’s stories in your inbox
Join Medium for free to get updates from this writer.
“Will this make the product better for most users — or just make it busier?” Sometimes the best feature is no feature. The best decision is restraint. My takeaway as an aspiring PM coming from a development background, I’ve always been in a “builder” mindset — solve, code, deploy.
But PM thinking flips that mindset. It’s not about how fast you build.
It’s about what’s worth building.
The biggest shift for me has been realizing that focus is a product feature too. A product that does one thing beautifully will always beat one that does five things averagely. In product management,success isn’t defined by what you build. It’s defined by what you decide not to build — and why. Because every product is a story. And like any good story, it’s not about how many characters you add, but how clearly you tell the main one.
The main role of product manager is not being an ‘ idea man’. It’s collecting ideas and prioritising what to build or more importantly what not to build.
