What we underestimate about emotion in product
Ego, fear, identity and the emotions we pretend aren’t there
We tend to present product decisions as rational.
We talk about data. Opportunity cost. User research. Prioritization frameworks.
But behind many decisions, something else is quietly contributing:
Emotion.
You’re human. So are your stakeholders. As long as humans are involved, product work is social.
We defend a feature because someone championed it publicly, and now we’re attached.
We prioritize a roadmap item because it has high visibility, even if it’s not high impact.
We choose a metric to measure success because it reassures what we hope is true, even when it’s not the best signal.
We underestimate how much emotion shapes outcomes.
Ego. I proposed this, so it must succeed.
Insecurity. If their idea succeeds, where does that leave mine?
Fear. If we don’t launch something impressive, we look small.
Identity. We’re an AI company, so everything we build has to “touch” AI.
Status. This project is “cool”. It has executive attention.
It’s human.
When the emotions behind decisions are acknowledged, they become manageable. Like it or not, this is part of product management.
Instead of asking:
“Is this backed by data?”
Sometimes the better question is:
“What feeling is driving this decision?”
You can’t eliminate emotion from product work. But once you understand what’s underneath it, you can manage it deliberately.
We like to think we operate analytically. In reality, product is as psychological as it is strategic.
If this resonated, I’d love to know: where have you seen emotion quietly steer a product decision?


Admitting no logical decision is logical is the only logical thing