Analysis

What an information systems audit reveals, and nobody asked for

You commission a technical survey. You receive a map of the company’s dependencies — on tools, on providers, and sometimes on a single person.

Four people looking together at a computer screen in an office
What the tools cannot see, the interview says

“Information system” is an expression that keeps people at a distance. It suggests servers, when it means everything that moves information around a company: the software, the files, the habits, and the people who know where things are.

An information systems audit looks at that system. Which is why its conclusions surprise: they are rarely about the hardware.

What an information system covers

Four layers, of which usually only the first is examined.

  • the applications: what the teams actually use, including whatever was never approved by anyone
  • the data: where it is, who holds it, in what format, and what it would take to take it back
  • the flows: how information passes from one tool to another — often through a manual export somebody runs on a Friday
  • the roles: who decides on a change, who applies it, who is told about it

The third layer reveals the most. A flow held together by hand is a flow that stops when the person is away, and nobody has ever written it down.

Three findings that recur

They were not asked for, and they weigh more than the list of obsolete versions.

  • Tools in use without management knowing. A shared spreadsheet, an online service subscribed to by one team, a personal account used for work. This is not indiscipline: it is a need that found no official answer.
  • A dependency on a provider that was never assessed. Not in the contractual sense but the practical one: he alone knows the configuration, holds the credentials, and knows why things are as they are.
  • A single point of failure. A machine, a file, an account whose unavailability halts an entire activity, and that nobody had identified as critical.
The question is not whether the system is modern. It is what stops, and for how long.

Technical debt, explained without jargon

Every time a decision is deferred — not migrating, not documenting, working around rather than fixing — the company borrows time. The deferral is often rational at the time.

What is not rational is not knowing how much has been borrowed. The debt then shows up as symptoms blamed on something else: a simple project taking six months, a provider refusing to commit to a deadline, software that cannot be updated because something else depends on it.

An audit does not clear it. It puts a figure on it, and says which part to repay first.

The questions to have asked in interview

An audit conducted from documents alone misses the essential. Four questions, put to the people doing the work, say more than any inventory:

  • What loses you the most time each week?
  • What do you do by hand because the tool does not do it?
  • What would stop if you were away for three days?
  • What have you stopped reporting because nothing changed?

The last is the most revealing. The faults nobody reports any more are the ones accepted as normal, and they appear in no monitoring tool.

What the report must make it possible to decide

An information systems audit that concludes “we should modernise” has produced nothing. The useful deliverable answers three questions the director can arbitrate:

  • What threatens business continuity within twelve months?
  • What is currently preventing a project already decided on?
  • What is expensive without preventing anything, and can therefore be left as it is?

What comes out of it is not an inventory, and the confusion is expensive: mapping is not taking stock.

The third question is what makes the report credible. A document that gives nothing up asks the company to handle everything, which it will not do — and it loses, in the same movement, the authority of its first two answers.

Common questions

How do you audit an information system?

By looking at its four layers — applications, data, flows between tools, roles — not just the hardware. Interviews matter as much as documents: what is done by hand, what would stop during an absence, what people have stopped reporting.

Why audit a business’s information system?

To know what stops, and for how long. An information system audit most often reveals tools used without management’s knowledge, a never-assessed dependence on a supplier, and a single point of failure nobody had identified.

What is technical debt?

The accumulated cost of deferred decisions: not migrating, not documenting, working around rather than fixing. It is paid in delays, dependencies and the inability to change. An audit does not erase it; it prices it and shows which part to repay first.


Next article

Repositioning: the signals you would rather not see

Read

A transformation to support?