I’m a solo maker and I built this after repeatedly running into the same problem in planning sessions. No matter what framework we used: RICE, ICE, voting, scoring, nothing actually got removed. Everything had a solid justification. The roadmap just kept growing.
It wasn’t a prioritization problem. It was a subtraction problem. So I tried reversing the rule. Instead of asking people to vote on what to keep, I made everyone cut three items. You couldn’t move forward until something was actually removed.
The tone of the conversation changed immediately. It forced real trade-offs instead of polite agreement. I turned that exercise into a small web tool called Less Is More. It’s intentionally simple, no accounts, no scoring system, no analytics. Just structured subtraction. I’m curious how others here handle “priority inflation.” Do you enforce caps? Time box initiatives? Something else?
I’m a solo maker and I built this after repeatedly running into the same problem in planning sessions. No matter what framework we used: RICE, ICE, voting, scoring, nothing actually got removed. Everything had a solid justification. The roadmap just kept growing.
It wasn’t a prioritization problem. It was a subtraction problem. So I tried reversing the rule. Instead of asking people to vote on what to keep, I made everyone cut three items. You couldn’t move forward until something was actually removed.
The tone of the conversation changed immediately. It forced real trade-offs instead of polite agreement. I turned that exercise into a small web tool called Less Is More. It’s intentionally simple, no accounts, no scoring system, no analytics. Just structured subtraction. I’m curious how others here handle “priority inflation.” Do you enforce caps? Time box initiatives? Something else?
Would appreciate honest feedback: https://www.cognu.app/less-is-more