> Because not talking to users and then implementing a drastic change they don’t like sounds like a rookie move? That sounds like every single sad tale where a

> Because not talking to users and then implementing a drastic change they don’t like sounds like a rookie move? That sounds like every single sad tale where a change of management/executives forces some new process or tool on their underlings without any input. (Perhaps those are junior developer CTOs?) So the thesis of the OP was straightforward and clear because of all the facts in the history. Replacing that with some generic tale about mismanagement and the accursed junior-run-amok is comparatively less interesting.