Teams with unlimited resources build bloated products. Teams with constraints build focused ones. A tight deadline forces prioritization. A small team forces simplicity. A limited budget forces creativity. The best product decisions are often made not despite constraints, but because of them.
A backlog is a prioritized set of options, not a list of obligations. The moment someone says “it is in the backlog” as if that means it will get done, the backlog has stopped being a tool and started being a graveyard of half-promises. Anything older than 90 days without activity should be challenged or removed.
The act of writing a product decision down, the context, the options, the tradeoffs, the reasoning, forces a clarity that conversation alone cannot. Teams that only discuss decisions verbally lose the reasoning within days. Write it down. Not for documentation. For thinking.
Product sense is not a mystical talent. It is pattern recognition built from reps. Every user conversation, every failed launch, every feature that moved a metric, these are the training data. The PMs with the best instincts are not gifted. They have simply seen more outcomes and remembered what worked.
Most estimation rituals exist to make stakeholders feel comfortable, not to make the team more effective. The estimate is treated as a commitment. The team pads it. The stakeholder discounts it. Both know the number is fiction. The time spent estimating would have been better spent building and measuring.