A Story of DevOps >> Episode 10. The Suit (Digital Transformation)
‘Digital Transformation’ – what is this? I am not sure I have found a particularly satisfying definition of this (similar to DevOps, in a way) but these two words are hitting the streets of the CIO in a big way bringing with it confusion and chaos.
Dare I take this subject. Not on my own. However, with the help of my esteemed colleague Harvey Neve, we would like to have a go.
Iron Man is the name of the suit of armor developed by Tony Stark created with the help of Ho Yinsen as a means of escaping captivity in Afghanistan. Once he got back home, he perfected the armor using the vast resources of his former weapons factory Stark Industries.
Tony took the name “Iron Man” after the suit of armor he built and wore.
There have been 42 iterations of the suit. Mark 1 was crude and made with what was available with equipment such as a manual rocket launcher, flamethrower and jet boots. This is a vast contrast to Mark 42 which attaches to the nervous system and boasts a plasma-penetrating Unibeam, tactical weaponry, remote control, self-repair, advanced repulsion, armour separation upgrades and water resistance amongst many other features.
However, the suit is not fully exploitable without Digital capabilities. Some of these capabilities include:
- Data storage and analysis from both the sensors in the suit and from external sources
- Mobile integration to send and receive voice, video and multi-media calls and messages
- Information access via computing, tablet, phone and HUD capabilities with seamless integration of information between all devices
- Bluetooth, Wi-Fi and Satellite secure connectivity
- Self-Diagnostics, self-heal capabilities with debugging and logging capabilities
- Artificial Intelligence through J.A.R.V.I.S. Amazon Alexa has nothing on J.A.R.V.I.S. yet. J.A.R.V.I.S brings all the information and real-time situational analysis together with Tony’s intelligence and controls all devices and security
The key here is that without the right data and technology (which incidentally needs to built to extremely high standards, with continuous evolution based on the nature of threat, suit capability and user feedback) Stark cannot use the capabilities of the suit to full effect.
Organisations are facing the same challenge – your nature of threat is changing all the time, your market is being infiltrated with new products constantly, customer experience is king, you have petabytes of data which demands some order to make effective decisions and competition is rampant and global. Your competitors are underpinned by high quality technology which seamlessly integrates data from all sources, with new features being deployed every week or every day and they are building solutions for all scenarios on all platforms – and they are going crazy by integrating all this with advanced artificial intelligence which becomes the ‘best friend’ of the customer and the organisation.
Business forecasts, market prediction, stock replenishment, process automation, self-heal and strategic pivoting are done in hours and minutes instead of months and weeks.
Where do you start? What chance to you have? Who is trying to sell you a technology that will solve all this for you. What solution can possibly interface with your organisation’s Nervous System as J.A.R.V.I.S does with Stark?
This brings me back to DevOps – is it important that we have a culture within our organisation where high performance IT teams can build, deploy and support high quality software with continuous release of evolving features that are needed to respond to forever changing world and to do this at breath taking velocity that leaves the competition standing?
Stark realised this and from the Mk 1 Minimum Viable Product, he build 42 iterations, each evolving with continuous learning, experimentation and in response to the evolving threat with no view of finishing. He didn’t work alone and had support from J.A.R.V.I.S and the team. If you have seen the films, Stark has no issue in experimenting and failing (like in the video above) with an appetite for risk (albeit perhaps slightly too much appetite). He has a balanced working team with Pepper, Rhodey and J.A.R.V.I.S. Working together towards the common mission, a team of people with different strengths and the right behaviours who have masters of their environment, iterate the development of the Iron Man suit and with the sacrificial and determined leadership of Tony Stark, despite the odds, to save the world on many occasions.
Like Iron Man is to Stark, we all need to put our Digital Transformation to our Users. Put the user first, consider the user persona and journey and build the technology around them.
More in this series #AStoryof DevOps:
- A Story of DevOps
- Episode 1 >> Origins (Traversing the Change Curve)
- Episode 2 >> One Ring (Alignment and Empowerment)
- Episode 3 >> Freedom (Leadership)
- Episode 4 >> Assemble (Productive and Teams)
- Episode 5 >> Shield (Tools of the Trade)
- Episode 6 >> Kryptonian (Value, Flow, Quality in a Complex World)
- Episode 7 >> Jedi (Mastery)
- Episode 8 >> Balrog (Confront the Brutal Facts)
- Episode 9 >> Kryptonite (Anti-Patterns of DevOps)
- Episode 10 >> The Suit (Digital Transformation)
- Episode 11 >> Flux Capacitor (Automation and Orchestration)
- Episode 12 >> Resurrection
#AStoryofDevOps #DevOps #IronMan