You finally bought an ATS. Three weeks later, half the hiring managers still export to a spreadsheet. Nobody logs notes where they belong. You are not failing at change management alone. You are bumping into two stubborn forces: habit and missing know-how. On paper the old way looks broken. In practice it feels fast, familiar, and low risk.
Habit Is a Feature, Not a Bug
Email threads and shared sheets are terrible systems of record. They are excellent systems for avoiding embarrassment. People already know where to click. Mistakes look like normal noise.
A centralized ATS asks everyone to name stages, tag feedback, and admit when a decision slipped. That is a small social cost on a team that already feels underwater. So the tool becomes “extra work” even when it would save hours later.
This is why debates about ATS quality often miss the point. The software can be fine and still lose to muscle memory.
What “Lack of Knowledge” Really Means Here
It is rarely “we do not know how to log in.” It is usually a gap in process literacy:
- Nobody agreed who moves a candidate between phone screen and onsite, so stages stay generic or empty.
- Managers were never shown how notes help legal hygiene, calibration, or handoffs, so they treat the ATS as admin theater.
- HR is the only person who touched onboarding in the vendor demo, so the rest of the org never built a shared picture of the workflow.
You need a little training, a little governance, and a single source of truth everyone touches on day one. Without that, the ATS feels optional. Optional tools die.
What the Field Data Adds (With Context)
Industry blogs recycle big headline numbers. A smaller survey can still sharpen the conversation if you read the fine print.
In February 2025, Recruit CRM surveyed 58 recruiting professionals and reported recurring friction with ATS products: 65% listed lack of user-friendliness as a common challenge, and 55% reported broad dissatisfaction with their current recruitment tool. The same write-up claims 60% of businesses with 1 to 50 employees now use an ATS.
Tiny sample, so treat it as a pulse check, not a census. The pattern still matches what SMB teams say out loud: the tool is “there,” but comfort and clarity are not.
Why 20 to 100 Person Companies Feel This More
You have enough hiring to hurt when the process leaks. You are still small enough that one stubborn hiring manager can pull everyone back to DMs.
You also get pulled into “just this once” exceptions: a founder referral, a rush fill, a role nobody wants to document. Each exception teaches the team that the ATS is optional.
Adoption is less about enthusiasm and more about defaults. If the standing rule is “candidates live in the ATS, full stop,” the habit flips. If the rule is “ATS when we remember,” the old stack wins.
The Uncomfortable Argument
SMB ATS projects often fail softly. The subscription renews. The work keeps happening elsewhere.
If you are the HR lead stuck in the middle, the fix is not another feature demo. It is naming the real job: shrink the comfort gap, train for real workflows, and make the old path slightly annoying on purpose.
Turn off parallel trackers when you can. Close the duplicate sheet. Route status questions back through one place.
That is political work. It is also the real work.
Canvider keeps SMB hiring in one place so you spend less energy fighting duplicate workflows and more on actual decisions.