Knowing something isn't right is different from knowing what to do about it.
It’s easy enough to know something isn't working or needs to change, and there is no end to technology "solutions" to implement, but which technology to choose and more importantly--how do you integrate it effectively within your current ecosystem/culture? Not so easy.
What I call "Trickle-down Techenomics" is when non-technically oriented leadership attempt to forge a new technology path using the same mindsets and maps as before. They implement technology, but they don't know how to integrate it.
"Trickle-down Techenomics" results in "Kabuki Integration"
Under "Trickle-down Techenomics", "Kabuki Integration” gives the appearance of functionality but is underemployed, controversial, burdensome, and doesn't promote confidence among users let alone show demonstrable return on investment.
As "Kabuki Integration" is often invisible to non-technical leadership, it's difficult to root out because it's giving off the appearance of working. All the roles are there, all the events take place, but the real benefits never reach the user and the technology/coordination overhead is often wasted.