Process debt, data debt, and tool debt
Process debt is a workaround everyone knows is wrong, but the team keeps doing it because the day does not allow a proper fix. Data debt is where the truth of record lives in the wrong place — a spreadsheet with twelve versions, or a field in the system nobody trusts. Tool or integration debt is when a glue script, manual export, or a seat on another app is holding the real workflow together — until renewal season, a key person leaves, or you try to migrate the mess.
None of that goes away when you buy a different platform unless you have named the debt first. A new name on the login screen is still the same re-key, the same handoff, the same who is allowed to change the master record.
Book a free systems review if the next project already feels more like a rescue than a launch. If you are in that shape, we also have rescue and rebuild in our offers, plus build and ongoing system care once the ground is calmer.
What compounds between renewals
The expensive pattern in SMEs is temporary that became load-bearing — the one Excel someone "just uses for a bit" that is now the board pack; the do not delete folder; the only Dave knows export that runs the payroll.
When the bill finally comes — migration, re-platforming, a compliance review — you pay for (a) the move itself and (b) untangling a decade of habit. The second part is the part leadership underestimates, because the software invoice has a number on it and the habit line item does not.
Signals you are in compound territory:
- The same work is typed twice between systems with no one owning the sync.
- Can we have a report? is answered with another spreadsheet, not a change in the system of record.
- Fear of touching a part of the stack, because the last time someone did, it broke a downstream step nobody had documented.
- Someone says we will fix that in the next tool and the list has outlived two next tools already.
A one-page debt register for leadership
You are not after a 40-row IT inventory on day one — you want a list a non-technical owner can use in quarterly planning.
| What we call it (plain English) | Why it burns | Rough cost of delay (high / med / low) | Who owns a decision, not just a log-in |
|---|---|---|---|
| e.g. Quote in CRM, still raised in a doc | Rework, wrong pricing in front of customers | High | Head of sales + ops lead |
| e.g. Stock truth in a sheet | Fulfilment errors, year-end pain | Med | Whoever signs stock counts |
Keep the cost of delay as a band, not a fake decimal — the point is to compare and to stop everything from being the same urgent later.
Next step in the room: pick one item the next quarter and answer: do we need a process fix, a data clean-up and ownership fix, a build or integration, or a process audit to see which applies? That single decision cuts more debt than a slide deck with ten strategic blurbs.
Local and remote: we work with Teesside and the North East and with teams further afield when the fit is right. Book a systems review to walk the register with a second pair of eyes — and see all offers for audit, build, rescue, and care when you are ready to pay the debt down on purpose, not in a fire drill.