A tool that worked three years ago can slow your team down today without you noticing. Here are the signs we spot immediately when arriving at a client's site.

Most tools don't die at once. They slow down, get uncomfortable, and your teams start building workarounds without telling you. One day someone asks "can we do this differently?" and you discover that real work has been happening alongside the official system for months. What we come to see isn't the tool: it's what your team does when the tool no longer keeps up.

Five telltale signs

Your teams keep a parallel notebook, Excel, or shared file. The clearest sign. A tool that needs to be "doubled" by an informal support has been outgrown by the real need. You add headcount to hold the same volume. A fitting tool absorbs growth up to a point without extra hires. If you hire to re-enter, correct, reconcile: that's not a labour need, it's a tool need. The same mistakes come back month after month. Wrong number in a report, forgotten order, duplicate invoice: if the same incidents recur every quarter, your tool isn't the cause, but it doesn't let you prevent them either. Your teams ask you to approve things they could do alone. A badly configured tool concentrates decisions on one or two people who become the bottleneck. You hear "with the old one, we used to…" Classic sentence after a migration or update that removed a simple function without replacement.

Why we tell you this

None of these signs come suddenly. They settle in, become the furniture, and in the end nobody notices. An outside eye catches them in one morning. We're not here to sell you a replacement: we're here to see if your tool can be adjusted, extended, or genuinely needs rethinking.

What we've seen on the ground

At a client, three different people kept the same order log: each in a different format (paper, Excel, line in a badly configured ERP). The real problem wasn't the ERP. It was that nobody had had time to reconcile the three practices since the business grew. We fixed it in two weeks without touching the ERP.

FAQ

How long does the observation take? Half a day to two days, depending on the role observed. Priced as a package.

What if you find nothing? We tell you so, and we propose nothing. We'd rather not bill a job that won't serve you.

One of these signs ring a bell? We come look before proposing. Tell us how you work today. Let's talk →