Technology Waste Audit · System 02 · overlap, integration debt, and re-entry
When Overlap Is Actually Waste
Marketing runs its projects in Monday. Product runs its projects in Asana. Operations runs its projects in ClickUp. Spotted on a spend report, that looks like the easiest finding in the whole audit: three tools, one job, cancel two of them. Spotted on the ground, it might be three teams with genuinely different workflows, one of which is mid-migration off a tool the other two already left. The spend report can’t tell those two situations apart. Only the people using the tools can.
The idea in one line: a capability overlap is a candidate for waste, not a finding. It becomes a finding only once you’ve checked who uses each tool, for what, and what it would cost to move them — and a good chunk of what looks like software waste is actually labor cost, hiding in the re-typing between systems that were never connected.
Redundant tools aren’t waste until you check
Two products in the same category on a spend report is a question, not an answer.
A legitimate reason for the overlap shows up often enough that it’s worth checking before recommending a consolidation: different teams with genuinely different workflows, a compliance or customer-facing requirement one tool meets and the other doesn’t, or a migration already underway where cancelling the “old” tool today would strand work in progress. None of those show up in a spend export. All of them show up in a five-minute conversation with whoever owns each tool.
Build a capability map
Integration debt and duplicate entry are labor costs
These two don’t show up as an extra invoice line. They show up as time, and they’re easy to miss in a spend-only audit for exactly that reason.
Integration debt is the accumulating cost of connecting systems the cheap, expedient way — a point-to-point automation nobody documented, a manual export-then-import step someone started doing because building the real connection felt like too much for what seemed like a small need at the time. It shows up later as fragility: a tax-rule change that should touch one system instead touches three, because three different manual workarounds grew up around the gap.
Duplicate data entry — the same fact typed into more than one system because they don’t share a reliable connection — is also a named pattern in the Process Waste Audit, under duplication and re-entry. That page covers the general case. What belongs here specifically is tracing a re-entry pattern back to the missing or broken integration causing it, which a process audit alone won’t surface.
A worked example
The same 40-person agency from System 01 has three project tools on its books: Monday, Asana, and ClickUp.
What the capability map found
- Monday: client-facing account team, 9 seats. A named client contract requires shared-board access the client’s own staff can log into — a genuine, documented constraint.
- ClickUp: internal ops team, 6 seats. Genuinely different workflow, heavy on recurring checklists ClickUp handles better for this team’s use case.
What was actually redundant
- Asana: product team, 5 seats, no client-facing requirement, no meaningfully different workflow from what ClickUp already does for ops — the honest answer to “why this one” was “the last product lead had used it somewhere else.”
- Separately: the account team re-types every closed Monday project into the accounting system for invoicing, about 40 minutes a week, because the two were never connected. No missing feature caused this — nobody had ever asked whether Monday’s API could do it.
Three tools looked like one obvious finding from the spend report. The capability map found exactly one genuinely redundant seat group, and a separate, unrelated finding — a 40-minute weekly re-entry habit — that the spend report never would have surfaced at all.
Naming what’s redundant and what’s just disconnected is most of the diagnosis. What’s left is deciding what to do about each kind of finding — and one of them, shadow IT, needs a different first question than the other two. System 03 covers that decision.