A short article by our CIO on why Environment Mapping (or call it “good” Configuration Management if you wish) is so essential to controlling an organization’s IT delivery capability and cost optimization.
Why Map your IT Environments
Mapmaking, or cartography, has been an integral part of human history for tens of thousands of years.
From paintings in caves to ancient maps of Babylon, Greece, Rome and Asia, through the Age of Exploration by the Stars, town planning to avoid contention and onto today with the likes of Google Maps & Geo-Location-ing.
People, government & businesses have created and used maps as a tool to help them define, explain, and navigate their way through towns, cities, counties and the world itself. And imagine the risk of doing trade without them?
- Scope: Destination unknown
- Cost: Journey is expensive due to a sub-optimal route
- Risk: You might never get there (Here there be Dragons)
- Time: Late delivery (assuming you get there)
- Quality: Risk of spoilt goods
Goals that all sound somewhat familiar, and it begs the question:
- “Where does “Mapping” sit in the realms of IT & Digital Delivery?”
Well, my quick answer would be this: There was good reason ITIL evolved around a centralized CMDB (Configuration Management Database) philosophy, despite many organizations focusing too much on the ITIL peripheral like ticketing.
IT Environment Mapping is the foundation of “Enterprise IT Intelligence”. Or to put it another way: “If you don’t know what your IT Landscape looks like, you are going to struggle to navigate, manage, and coordinate it effectively”.
And if that’s the case, then you probably stop talking about grandiose goals like DevOps @ Scale or SAFe (Scaled Agile Framework), as the reality is your teams are very much unprepared.
Like tribes sitting on their isolated islands playing with sandcastles, blissfully unaware, and unprepared for the broader mega-structures around them.
The Value of IT Environments Mapping
So why is Environment Mapping so important? Well, here are 5 reasons:
1. Knowledge via a single pane of glass
Establish a holistic view of your IT landscape that allows you to bring it all together and bridges IT and Business appreciation, team upskilling, and cross-team collaboration.
Understand your Environments Lanes and their sub-structure. Structure consists of System Instances consisting of Applications, Data & Infrastructure and, of course, relationships with other Systems, Projects and the Business itself.
2. Consolidate and/or Grow Decisioning
Easily identify whether you have “footprints” that are over- or undersized. Recognise over-proliferation & quickly identify opportunities to save costs through proactive housekeeping and decommissioning.
Or recognise under-proliferation, which causes contention, disruption & project bottlenecks, and address it to streamline your delivery chain.
3 Simplified Service Management
Streamline troubleshooting and impact analysis after System or Component incidents & issues. Instantly recognise what is up and down and identify what that means, i.e., how it is impacting your business, processes, other systems and the delivery process itself.
4 Project Readiness & Streamlining
Ensure Project Environment needs (and any gaps to goal) are immediately understood and accommodated, i.e., Shift Left your Design, Architecture and Build practices, and ensure your Environments are “Fit for Purpose” and provided in a timely fashion.
5 Delivery Chain Optimization
Environments Mapping is the foundation for Behaviour Mapping, i.e., it is not just about the boxes (as was often the focus in the early CMDB days).
By attaching key metadata, for example, system versions or data compliance, you can start to identify gaps and opportunities for ongoing improvement, for example, the need to introduce tooling and/or automate key tasks.
Tips on successful IT Environment Mapping
So, with the above benefits in mind, how does one go about successfully mapping their IT Environments? Well, to be honest, that’s probably beyond any brief post; however, I’d offer the following pointers:
1. Map Top Down
IT is the backbone of business, so start from a business perspective. This will allow you to develop “meaningful” associations across Business Units, Finance, Programs & Technology itself.
2. Ensure it’s living
Visio Diagrams & Excel diagrams are static and get out of date very quickly. Implement methods & automation to ensure maps are continually regenerating. Technical debt is the reason 95% of CMDBs fail.
3. Don’t think Box
Mapping need not and should not be focused on the physical. Think more broadly about how these maps will allow you to get to your corporate destination.
For example, help projects deliver more quickly or cost-effectively by interlacing key metadata that allows effective insight and decision-making.
4. Don’t leave it to your Infrastructure Team
Or more fairly, don’t let the tail wag the dog. Sure, Infrastructure is important, but mapping bottom-up should be a complement to top-down, not a “practical” alternative.
Summation
Whether you prefer to call it Enterprise “Configuration Management” or “Environment Mapping”, it is clear that delivery agility comes from transparency, collaboration, less disruption, and good operational decision-making, and understanding your systems & relationships is key to that success.
Anyhow, let me know what you think.
Niall Crawford
Niall is the Co-Founder and CIO of Enov8. He has 25 years of experience working across the IT industry in Software Engineering, Architecture, IT & Test Environment Management, and Executive Leadership. Niall has worked with and advised many global organisations covering verticals like Banking, Defence, Telecom, and Information Technology Services.