And how did you actually do it? Any good advice/books on this.
I know my management has clear ideas what they want so even if I am told - it’s my job to figure it out they say what needs to happen (not accepting a No).
I know my management has clear ideas what they want so even if I am told - it’s my job to figure it out they say what needs to happen (not accepting a No).
This is an indirect no. We can do that, it will cost X and take Y time and have Z impact on the code base and our long term velocity. Is this what you would like to do?
Quite often, they will say no themselves. If you have no trust with management and they ignore your warning, the org is already at high levels of toxicity and there isn't much you can do anyway. Realize that and navigate the position accordingly.
Couple weeks in CEO asked when new feature would be ready.
It took that level of complete absurdity for me to finally say no. I eventually rebuilt the entire infrastructure, scaled traffic 3x, hired and trained new team. It was about a year before I would even listen to a request for a new feature. Took me a long time to recover from that job.