Tool Avoidance vs. Tool Outgrowth 🛠️
Tool avoidance is mostly a behavior problem. People can complete important work inside the system, but choose not to.
The reasons are familiar: habit, low perceived value, weak training, poor incentives, or a belief that the platform exists mainly for management reporting rather than daily work.
Tool outgrowth, however, is a system-fit problem. The platform may have been reasonable when the company was smaller or less complex.
Over time, workflows, reporting demands, governance needs, and cross-functional coordination can outgrow what the tool was designed to handle.
A useful way to frame it is behavior gap versus capability gap:
- A behavior gap means the tool can support the job, but people aren’t using it consistently.
- A capability gap means even willing users struggle because the platform no longer supports the level of complexity the business now requires.
If the issue is avoidance, the company needs better adoption mechanics.
If the issue is outgrowth, it needs to rethink process design, system configuration, integrations, or the platform itself. Those are very different moves, with very different costs.
Check out the full article HERE
2
1
1August 19, 2026 88
