Technology changes nothing.
Recently Damon Edwards said
Beware: “Tools change culture” may sound like wisdom, but it’s not. It’s a fallacy often repeated by people who want cover to embark on a tools project without addressing what is really wrong with their organization.
— Damon Edwards (@damonedwards) February 3, 2018
and a few tech-worshippers got upset, e.g.
Really disappointing to see some prominent "DevOps" people reject the need for tooling repeatedly.
The biggest change has been brought about by waves upon waves of tooling, starting from configuration management to containers to now schedulers ... https://t.co/6CXpI4IspM— Cindy Sridharan (@copyconstruct) February 4, 2018
There is far more to IT than information or technology. The information and technology are useless dead lumps without the people and process and business and partner and service and value and governance aspects of IT to bring them to life.
I first said it back in 2006: technology does not fix process.
- If the process is broken technology is not going to fix it. Bang your head hard against the desk while repeating five times "technology is not going to fix it". If your people do not have a service management culture; if your service management processes are not well designed, bedded in to the organisation, and measured and monitored; if you do not have this situation then all the cool tools in the world are not going to fix it dammit! ... if you have a process problem there is not a technology solution.
A few years later I talked about over-hyping Cloud.
Cloud doesn't address:
- cultural change: trust, teaming, sharing...
- changing skillsets and capabiltiies
- build methodology
- automation of build and operations tools (the devops "tool chain")
- changed SDLC
- changed operations and support
- un-virtualisable legacy
This is yet another example of that old IT pestilence: one "thing" as the answer to a complex question. Tech alone solves nothing.
And the tool is not the objective
- Identified need, problem or risk
-> business requirement
-> objective(s)
-> desired IT outcomes (COBIT maps all this)
-> identified improvements
-> designed solution
-> appropriate bits of best-practice processes create a composite solution
-> efficiency and/or effectiveness constraints
-> software requirements
We are talking in the context of organisations not society as a whole. Don't confuse your personal digital experience. A few exceptional technologies impact culture in step-changes. That's not something you can generalise to every software tool, though the vendors sure try.
Organisations do not wish to change in the organic uncontrolled manner that society does. Org change is directed. By changing people not tools. Good people can work with crap practices. They soon fix them. Good practices can work with crap tools. They show what needs fixing.
It doesn't work the other way. Good tools don't fix crap practices and they sure as hell don't make good people and culture.
Technology change is only a small part of organisational change. To say technology is transformational you have to have the narrow world view stereotypical of technical people. When technology changes it has a diminishingly significant impact as you go up higher levels of an organisation:
Or looked at conversely: tech change is only a small part of the overall change. Tech makes change more efficient and effective. Occasionally it is essential to the change.
But changing tech ON ITS OWN changes nothing: that is the key point here. Roy said it:
And that’s just it: The “solution” doesn’t solve the problem. The people *using* the “solution” do. @gtsanker #ITSM https://t.co/ksbRLfLBy5
— Roy Atkinson (@RoyAtkinson) February 2, 2018
Coming soon: "Tech is the easy bit".
