There are projects where almost anything is technically possible.
The only question is: should we do it?
I do not decide situations like these on the basis of features.
I decide on the basis of risk.
When the timeline is unrealistic.
When the budget and expectations do not align.
When the customer says, “You decide.” That is when I become cautious.
To me, innovation does not mean making everything possible.
Innovation means taking responsibility.
Sometimes that means consciously saying no.
Not because something cannot be done.
But because there is a high probability that it will go wrong.
Saying yes to the wrong project feels good in the moment.
The rude awakening comes later.
For the customer.
And for your own team.
That is why I would rather say no early than later have to explain why a project was “a good idea in theory”.
👉 Where would saying no be more honest today, even if it is uncomfortable?