The opportunity passes by, now your company is playing catch-up and managers above you are asking how they missed it. If you say "I told you so," you get a reprimand instead of acknowledgement.
The opportunity passes by, now your company is playing catch-up and managers above you are asking how they missed it. If you say "I told you so," you get a reprimand instead of acknowledgement.
A lot of times, devs want to move in a new direction of whatever the hip tech stack is this year. This would help their career by adding the tech to their resume but the business benefit is almost always net negative.
Rather than arguing with a developer, they might just give a response that is outside of the developers' domain. The real reason is that it was a bad idea for the business.
Mix in the usual human bias ("We got to have 1 Leader, with 1 plan, else we have civil war and unrest") and you get viewed as a failure as manager- even though you prepared the underlyig plattform technology for future successes, because one product didnt take off.
I was really spitfull on management for this. but they are limited in quite a lot of ways.
What helps is creating the ilusion that others already have done a innovation..
We don't want to avoid doing x because we will end up like [the time we missed the boat].
Their request today? "You were absolutely right two years ago. Nothing has changed in the mean time and things have become even more complex now. But could you develop X for us, knowing that you can't touch or change any of the architecture?"
We did dissect the pros and cons, pointed to winners, showed the opportunities ahead etc etc. We were discussing everything at C-level too. But sometimes it just doesnt work.