What a Clear IT Infrastructure Map Looks Like in Practice at a 100-Employee Company

In many companies with 70–150 employees, the IT infrastructure has grown gradually. New systems appeared as the business developed: ERP, CRM, production applications, cloud platforms, file storage, backup services.

Each of these systems solves a real problem. The trouble starts a few years later, though, when nobody can clearly see anymore how they all connect to each other.

At that point, simple questions start to surface that are surprisingly hard to answer:

• which systems are critical for the company
• what depends on each of them
• who manages them
• what happens if one of them goes down
• who can help us with cloud migration

These questions don’t come up only in technical contexts. They come up in discussions about risk, business continuity, and investment plans.

---

What an “infrastructure map” actually means

An IT infrastructure map does not have to be a complex technical document.

In most cases, it’s enough to have a clear picture of a few essential things.

1. Critical systems

The first step is identifying the systems your company’s operations depend on.

These usually include:

• ERP
• email
• file storage
• operational applications (production, warehouse, projects)
• the cloud platforms your teams use

In many companies this list exists only informally — “we know which ones they are.” The problem is that when an incident hits, this information suddenly becomes very important.

2. Dependencies between systems

A system rarely operates in complete isolation.

For example:

• Your ERP may depend on internal servers, a database, or a VPN connection.
• File storage may depend on a cloud service.
• SaaS platforms may depend on identity managed in Microsoft 365 or Google Workspace.

Without a clear picture of these dependencies, it is difficult to estimate the impact of an incident.

3. Responsibilities

In mid-size companies, the infrastructure is usually managed by a combination of:

• internal IT
• external vendors
• developers or integrators

Over time, a familiar situation develops: when a problem shows up, everyone says it’s not on their end.

That’s why it helps to be clear, for every system, about:

• who manages it
• who steps in during an incident
• who has privileged access

4. Privileged access

In many companies, administrative access has accumulated over time without periodic review.

One employee gets access for a project. Another temporarily needs elevated permissions. Sometimes external vendors keep their access after a project ends.

Without a clear picture of these access rights, it becomes difficult to assess the risk.

5. Backup and restore

Most companies have some form of backup.

The important question, though, is a different one: how long does the restore take?

If a critical system becomes unavailable, it helps to have answers to a few simple questions:

• is there a backup
• where is it stored
• how long does the restore take
• who is responsible for this process

These things are rarely documented in a way that is easy to understand.

---

Why this exercise changes how decisions get made

The moment a clear infrastructure map exists, many conversations become more concrete.

For example, it becomes easier to see:

• where duplicate systems exist
• where costs are growing without adding value
• where the company depends on a single person
• where the critical points in the infrastructure are

These things are hard to spot when the infrastructure is only ever looked at in pieces.

---

A simple exercise for executives

If you want to understand how clear the IT infrastructure in your company really is, try a simple test.

Ask your IT team or your vendors:

• which are the 5 most critical systems for operations
• what depends on each of them
• how long it would take to get back to normal if one of them stopped working

If the answers are approximate, or differ from one person to the next, it’s probably a sign that your infrastructure is not yet visible enough.