You Don’t Have a Technology Problem

You Don’t Have a Technology Problem.

You Have a Sequence Problem.


It should take thirty seconds. A customer calls with a question about their last order. The answer is somewhere in the system.

The sales rep opens the CRM. The record is there, but the last update was six weeks ago. They check the shared drive for the delivery confirmation — three folders deep, two versions of the same file, neither clearly labeled. They open their inbox and search for the thread from February. Find it. The information they need is in a PDF attachment that someone manually exported from a system the company stopped using last year but never fully migrated away from.

Fourteen minutes later, the customer has their answer. They’re polite about it. They shouldn’t have to be.

Around the building, variations of this scene play out all day. The warehouse checks stock in one system and orders in another. Sales promises a delivery date based on what they think is current. Finance reconciles invoices against a spreadsheet that someone updates on Fridays — when they remember. The owner fields three calls before lunch that only exist because information didn’t arrive where it was supposed to.

Everyone has tools. Nobody has a workflow.

You’re not behind on technology. You’re buried under it.


How It Happens

It always starts with a real problem. A genuine bottleneck. Too much manual work, lost information, a task that takes an hour when it should take five minutes. The kind of friction that makes a business owner think: there has to be a tool for this.

So they find one. The demo looks right. The features make sense. The pricing seems fair. It gets purchased, rolled out, maybe even celebrated for a week.

But the process underneath — the way information actually moves through the business — was never mapped. Never questioned. Never cleaned up. The tool gets layered on top of a broken flow.

Now you have the same broken flow, plus a login.

This happens once. Then again with a different tool for a different problem. Then a third time. Each decision made sense in isolation. Together, they create a landscape nobody fully understands. Five tools. Three of them overlap. Two of them hold different versions of the same data. One of them nobody’s opened since March.

The owner becomes the only person who knows which tool holds which truth. The team uses what they trust — usually the spreadsheet they built themselves. Or their own memory.

The tool didn’t fail. It was asked to fix something it was never designed to fix — a process that nobody had stopped long enough to look at.


What It Does to People

The technical cost is easy to name: duplication, errors, wasted licenses, data that doesn’t connect. But the real cost is quieter. It shows up in how people feel about their work.

First: they stop trusting the system. It only takes getting burned by bad data twice. After that, people build their own shadow processes — notebooks, personal files, mental tracking. The official tool exists. Nobody believes it. So now the company runs on two systems: the one it pays for, and the one that actually works, which lives in someone’s head.

Then: double work becomes the default. People enter the same information in two places “just to be safe.” They verify outputs manually because they’ve learned the system doesn’t catch what it should. The tools that were bought to save time are now generating work. The team doesn’t complain about it. They’ve normalized it. That’s the dangerous part.

Then: decisions stall. Three systems show three different numbers. Not because anyone entered anything wrong — because the data took three different paths and arrived in three different states. Meetings that should produce action produce more questions instead. “Which version are we looking at?” becomes the most common sentence in the room.

Then: the quiet opt-out. People stop engaging with the tools altogether. They call instead of logging. They walk over instead of updating the system. They solve things in person because it’s faster than fighting the software. The digitalisation that was supposed to move communication forward has pushed it backward — to hallways, phone calls, and sticky notes on monitors.

This isn’t just friction. Research shows that employees spend an average of nearly an hour per day — 51 minutes — simply searching for information across scattered tools and platforms. Over a year, that adds up to more than 44 lost hours per employee. In a team of ten, that’s a full working month spent not on the actual work, but on finding the information needed to start it. And 56% of workers report that this constant toggling negatively affects their performance every single week.

The irony of bad digitalisation is that it makes people work more like machines — repetitive, manual, mindless — so the actual machines can sit idle.


The Sequence That Works

The fix isn’t removing technology. It isn’t adding better technology. It’s changing the order.

First: understand how the work actually moves. Not how it’s drawn on a diagram. Not how it was designed three years ago. How it moves today — including the workarounds, the shortcuts, the “just ask Sandra” steps that never appear in any documented structure. Most businesses have never done this. Not because it’s complicated, but because there’s never been time. Everyone is too busy managing the consequences of the current process to stop and look at the process itself.

Second: simplify. Remove what’s unnecessary. Clarify what stays. Some steps exist because they were needed once. Some exist because nobody questioned them. Some exist because a tool created them — a required field, a mandatory approval, a notification chain that triggers four emails where one would do. Knowing the difference is where the value is.

Third — and only third: decide what should be supported by a tool. Sometimes the answer is automation. Sometimes it’s a simpler version of what you already have. Sometimes it’s removing a tool entirely and replacing it with a clear agreement between two people. The point is that the tool serves the process. Not the other way around.

Simple beats complex. But simple isn’t where you start. It’s where you end up — after you’ve done the work of understanding what’s actually going on.


What Changes When the Sequence Is Right

The first thing that changes isn’t speed. It’s trust.

People open a system and the number they see is the number that’s real. They stop double-checking. They stop maintaining their personal backup. They start relying on the tool — not because someone told them to, but because the tool now reflects how they actually work.

The warehouse checks one screen. Sales quotes from the same source. Finance reconciles on Monday morning in twenty minutes instead of Friday afternoon in three hours.

The owner asks a question and gets an answer. Not three answers from three systems. One answer. The right one.

And then — the space opens up. Fewer errors means fewer fires. Fewer fires means more time. More time means someone finally builds that reporting view they’ve been thinking about for months. Someone else notices a pattern in the sales data that suggests a new opportunity. Not because they were told to innovate. Because they finally had the room to see.

People finish their day and feel like they finished something. The tools disappear into the background — which is exactly where good tools belong. Nobody talks about “the system” anymore. They talk about the work.

That’s not digital transformation. That’s what happens when the tools finally work for the people — instead of the other way around.


You know which system your team doesn’t trust.

You know which report takes three hours when it should take ten minutes.

You know which tool you’re still paying for that nobody opens anymore.

The answer probably isn’t more technology. It might be less. But it definitely starts with looking at what’s underneath.

When you’re ready to look — this is where we start.


Written by Sonja Huirne, founder of Resilience4Bizz. 30+ years of operational experience across industries, borders, and company sizes — from multinationals to the owner-led businesses that form the backbone of Europe’s economy. [Read more →](link → About page)


Sources

¹ Harvard Business Review (2022) — Knowledge workers toggle between applications 1,200 times per day, spending approximately 4 hours per week reorienting after switches.

² Lokalise / Workplace Productivity Survey (2025) — Workers lose an average of 51 minutes per week to tool fatigue; 56% report it negatively impacts their performance weekly. 79% say their company has taken no steps to consolidate platforms.

³ Qatalog & Cornell University — It takes an average of 9.5 minutes to regain productive workflow after switching to a different application.

⁴ American Psychological Association / Atlassian — Context switching can consume up to 40% of a person’s productive time.