Command and control was the edict but it was like herding cats. IT was managed as one big machine (Back in the 70s when I was playing school ground tiggy<\/a> it probably was one machine) that could be managed down to the smallest element. Very particular and focused.<\/p>\n The claw of the beast (John Christian Fjellestad via Flickr)<\/p><\/div>\n Of course IT supported only simpler applications back then like ledger accounting (urgh). Now IT underpins every part of a business. Business and IT have become one big melange.<\/p>\n With firewall boundaries being torn down to support XaaS, mobile and 3rd party integration the world and organisations are becoming one mega-melange. In this excellent blog Venkatesh Rao at Ribbonfarm details 8 metaphors for the modern organisation<\/a>. The organisational metaphor of a machine<\/em> is where we were, and the metaphor of the organisation as brain<\/em> or organism<\/em> is where we are heading.<\/p>\n You cannot control all details of an operation. A better approach is to:<\/p>\n Risk management entails making decisions moving forward but looking backward. Assessing the likelihood of something bad happening, say an AWS zone failing, or a VC-backed vendor going bankrupt, can be problematic. Assessing the MTTF of a hard drive is a little more scientific. We can apply standards, certifications etc. to technology and providers etc., but hey…. Sarbanes Oxley didn’t stop the GFC<\/a>.<\/p>\n Another method could be to look at managing the risk through Insurance and possibly even state governments. (Socialist, eh? I saw that “comrade” earlier)<\/p>\n I like the idea of insurance companies and governments (ICAG) providing incentives for better IT management. ICAGs will only cover risk if there is a level of transparency, disclosure and accountability from IT users, vendors and providers. Mandatory disclosure laws are a good example – looking at you Australia<\/a>. Another example could be whether an organisation’s risks should be covered if they don’t perform regular platform lifecycles<\/a>.<\/p>\n Technology will only improve standards (security, service levels, manageability etc.) with transparency and audited action that drives improvements. Open source development is a good example of heading in the right direction. We also need to report this stuff in annual reports, marketing briefs and government audits.<\/p>\n In the same way that airlines and airplane-makers disclose details of accidents and implement improvements to avoid recurrences, thereby improving air travel safety every year, IT must organise itself so that it is biased to improving without the need for “top-down” intervention. Some things will slip through the cracks but the “rules” will adjust to stop the same event occurring again.<\/p>\n Technology users and providers that can’t adapt will die off. Those that can will thrive.<\/p>\n What are some open and transparent practices IT should have in place to bias it to improving over time?<\/p>\n![\"The](\"http:\/\/www.coffeescroll.com\/wp-content\/uploads\/2015\/02\/6166513822_8f5e007dc1_o.jpg\")
<\/a>
\nOrganisations that see IT as something they can command and control are setting themselves up for disappointment, or consigning themselves to the past.<\/p>\n\n