Are We Investing in Technology Before Properly Understanding the Problem?

The question is uncomfortable because, in many organisations, the answer is yes.

A budget is approved. A vendor is shortlisted. A project plan appears with dates and a steering committee. Meanwhile the work itself — how a request moves, who decides, where things stall — remains a matter of opinion. Ask three people to describe the same process and you will receive three processes. The exceptions are not exceptions. They are the work.

Technology cannot fix a problem it cannot see. If nobody can point to a shared picture of how things actually run, the organisation is not choosing a solution. It is choosing a hopeful object and asking it to stand in for understanding.

This is not an argument against software. It is an argument against sequence. Understanding is treated as a delay — something to squeeze in after the licence is signed, or to skip because “we already know”. That confidence is usually the first thing that unravels in delivery. Requirements shift because they were never requirements. Scope expands because the problem was never bounded. The system is blamed for a process that was never examined.

Better questions come first. What is really happening? Who owns each decision? Where does work wait? What knowledge lives in one person’s head? What would break if they left tomorrow? Until those questions have answers that more than one person would recognise, a platform is a guess with an invoice.

Understanding is not a delay. It is the work that makes every later decision cheaper. Map the process. Name the problem. Then decide whether technology is even the answer — and if it is, what it must be asked to do.