The Systems Map: Why Your Company Runs on Acronyms

You’ve sat in a meeting where someone said “that has to go through SAP” or “just check Salesforce” and nodded, because everyone else nodded. Nobody paused to explain, because everyone assumes you know — and half of them are nodding too. This course is the missing explanation: the eight or so systems every big company runs, what each one actually is, and why they behave the way they do. No IT background needed; the point is to stop nodding and start understanding.

Here’s the first surprise: a typical mid-size company runs 50 to 200 software systems. Not because IT loves complexity, but because each department bought the tool that speaks its language. Sales bought a CRM to track customers. Finance bought an ERP to track money and stock. HR bought an HRIS to track people. IT bought an ITSM tool to track its own work. Each one is the right answer to a real problem — and together they form a map nobody ever hands you on day one.

System of record vs system of engagement

The single most useful distinction in enterprise software: a system of record is the one official version of the truth for a given kind of data. The CRM is the system of record for customers. The ERP is the system of record for money, orders, and inventory. The HRIS is the system of record for people — your title, salary, manager, vacation days. The ITSM tool is the system of record for IT’s work. When two sources disagree, the system of record is right by definition — that’s the whole point of having one.

A system of engagement is where you actually spend your day: email, Microsoft Teams, dashboards, chat, mobile apps. You rarely open the ERP directly; you see its data in a report someone pasted into a deck. This split explains a daily frustration — the place where work happens is almost never the place where work counts. The number in the Teams chat is a rumor; the number in the ERP is the truth. If you use Teams all day, our Microsoft Teams course covers the engagement side; this course covers the record side.

And here’s the honest rule veterans know: whoever owns the system of record wins arguments. If Finance’s ERP says the budget is spent, your spreadsheet saying otherwise doesn’t matter. If the HRIS says the role isn’t approved, the role isn’t approved. Arguing with a system of record isn’t a data debate — it’s a jurisdiction debate, and you lose.

Why there’s always one more system

Systems multiply for a predictable reason: every department’s pain eventually gets its own tool, and no single vendor does everything well. Then acquisitions add duplicates (two CRMs, three HR tools), and every new VP arrives loving a system from their last job. IT departments spend years on “rationalization” projects trying to shrink the list, and the list still grows.

Below the official map lives shadow IT: the spreadsheet, Access database, or free web app that a team quietly built because the official system was too slow or too rigid. Every company has one spreadsheet that secretly runs something important. Shadow IT isn’t stupidity — it’s usually a sign the official system fails at some real task. But it’s also invisible to backups, security, and audits, which is why IT reacts badly when they find it. Our Security Essentials course explains exactly why that free file-sharing app makes the security team twitch.

This week, try the one-question habit: for any number that matters in your job — a customer’s status, a budget line, your own vacation balance — ask “which system is the system of record for this?” The answer tells you where to check before a meeting, and whose data wins if there’s a fight.

Spot it: which system owns this?

Why it matters

People who carry this map navigate a company faster: they know where the truth about any topic lives, whom to ask, and why the official system beats the beautiful slide. Over the next seven modules we’ll walk the map one region at a time — CRM (module 2), ERP (module 3), HRIS (module 4), ITSM and the ticket ritual (module 5) — then the connective tissue: how one password opens everything (SSO), how systems exchange data (APIs), and the finale every employee has personally suffered: why these systems still don’t talk to each other. By the end, “it has to go through SAP” will be a sentence you understand, not one you survive.