Here There Be Dragons! Mapping IT Environments
Why Map your IT Environments
Mapmaking, or cartography, has been an integral part of the 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 expensive due to 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
- “Where does “Mapping” sit in the realms of IT & Digital Delivery?”
The Value of IT Environments Mapping
So why is Environment Mapping so important, well here are 5 reasons: 1 Knowledge via a single pain of glass Establish a holistic view of your IT landscape that allows you to bring it all together and abridges IT and Business appreciation, team upskilling and cross team collaboration. Understand your Environments Lanes and their sub-structure. Structure consisting 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 under sized. Recognise over proliferation & quickly identify opportunities to save costs through proactive housekeeping and decommissioning. Or recognise under Proliferation, that causes contention, disruption & project bottlenecks, and address 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 is it 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. Shit 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:- 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.
- Ensure its 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.
- 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 meta data that allows effective insight and decision making.
- 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 compliment to Top Down opposed to a “practical” alternative.
Summation
Whether you prefer to call it Enterprise “Configuration Management” or “Environment Mapping”, it is clear, 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.Relevant Articles
What is Canary Deployment? A Complete Explanation
Software development and deployment come at you fast. So organizations strive to deliver new features and updates to their users while minimizing risks and disruptions. One of the most effective techniques to achieve this delicate balance is through the use of...
A Comprehensive Guide to Product Lifecycle Management (PLM)
Product lifecycle management (PLM) plays a critical role in ensuring the longevity and competitiveness of software products. A successful software solution is not an accident, but rather a result of ongoing supply chain management, maintenance and a clear long-term...
Data Mesh vs Data Lake: Choosing an Architecture
As organizations scale and mature their digital ecosystems, data becomes both a key asset and a major architectural challenge. Live by the data, die by the data. With vast quantities of structured and unstructured data pouring in from dozens (or hundreds) of...
RAG Status: What It Is and Using It for Project Management
Effective Leadership requires effective tooling to drive successful outcomes. One tool they can use to monitor and measure progress is RAG status. RAG stands for Red, Amber, Green, and is a simple traffic light system used to communicate the current status of a...
Enterprise Architecture Tools: 11 to Be Aware Of in 2025
Enterprise architecture (EA) is an essential discipline for organizations aiming to align their IT strategy with business goals. As companies become more complex and technology-driven, having the right set of EA tools is crucial to streamline operations, improve...
What is a Staging Server? An Essential Guide
Release issues happen. Maybe it’s a new regression you didn’t catch in QA. Sometimes it’s a failed deploy. Or, it might even be an unexpected hardware conflict. How do you catch them in advance? One popular strategy is a staging server....