What a Tool Changes
Most workplace software is bought to solve a problem that is not a software problem. The distinction is learnable in advance and expensive to learn afterwards. For a related reference, see the guide.
Four things a tool genuinely fixes
Recall. Where things are, who said what, what state something is in. Software is far better at this than people and always will be.
Repetition. Anything done identically many times.
Coordination across distance or time. People who cannot ask each other because they are not in the same place or the same hours.
And arithmetic. Aggregation, rollups, comparisons.
All four are mechanical, and a tool that addresses one of them tends to pay off quickly and quietly.
Four things it only makes visible
Unclear ownership. A task system does not decide who is responsible; it displays that nobody is.
Undefined process. A tool imposes one where none exists — sometimes an improvement, always somebody else's.
A disagreement about priority. Now visible in a backlog rather than in a meeting, and no more resolved.
And a manager who is not managing. A dashboard shows activity; it does not supply the conversation that was missing.
Visibility is genuinely useful. The failure is treating it as resolution.
The question before buying
What decision will be made differently once this exists?
If there is a specific answer — we will stop doing X, we will catch Y earlier — the tool has a job.
If the answer is "we will have better visibility", ask the question again about the visibility. Visibility that changes no decision is a subscription.
Where the cost actually sits
Not the licence.
Administration. Somebody adds users, removes leavers, adjusts permissions, answers questions. Across six tools this is a part-time role and it is in nobody's plan.
Adoption. The whole problem, and it has its own page.
And the process change, which is the real work and is always underestimated because the tool demonstration made it look like configuration.
What to check before signing
What exports, and whether history leaves with you.
What the next tier costs and what triggers it, since administrative controls commonly sit one level above where a team starts.
What is on by default, particularly any capture that turns an administrative tool into a monitoring one.
And who else sees the data — the subprocessor question, which for anything holding employee data matters more than for most. Ten questions cover the rest.
The short version
- Tools genuinely fix recall, repetition, coordination across distance, and arithmetic — all mechanical, all pay off quietly
- They only make visible unclear ownership, undefined process, priority disagreements, and a manager who is not managing
- Visibility is useful; treating it as resolution is the failure
- Ask what decision will be made differently once the tool exists, and if the answer is "better visibility", ask again about that
- The cost is administration, adoption and process change rather than the licence
- Before signing: what exports, what the next tier costs, what is on by default, and who else sees the data
For additional context on this topic, see PlayStation.