Five reasons your new software is already a shelf
You bought it, trained on it, and three weeks later the team is back on the whiteboard and the group text. Low adoption is almost never a people problem. It is five design choices the vendor made, and every one of them is predictable.
You bought it. You sat through the training. Three weeks later the team is back on the whiteboard and the group text, and your expensive new system is a very well-funded shelf.
Low adoption feels like a people problem. It almost never is. It is a predictable set of design choices the vendor made. Here are the five that do the most damage.
1. It was built for the buyer, not the daily user
Most clinical-operations software is designed to win the demo, the feature checklist an owner evaluates, not to serve the admissions coordinator using it at 8 a.m. When the tool is built to be bought rather than used, staff route around it.
2. It requires an academy
If a new hire needs a certification course before they are productive, that complexity is your problem now. In a field with 30 to 40% annual turnover (Relias / NAATP, 2024), you pay that training tax on repeat.
3. It makes people re-enter everything
When the clinical record, the CRM, the spreadsheet, and the billing tool do not talk, someone re-keys the same patient again and again, and 47% of clinicians report sifting through duplicated data (KLAS, 2024). People do not avoid software. They avoid typing the same name for the fourth time.
4. It is a blank canvas with no sensible default
Endless configurability means the tool does nothing until someone spends months setting it up, and the choice-overload research says that is exactly how adoption dies (Iyengar & Lepper, 2000). A product that works on day one beats a product that could work after a quarter of configuration.
5. Support is slow when they are stuck
The fastest way to lose a user is to strand them mid-task. Slow or hard-to-reach support, a common complaint about the heaviest incumbents and a live risk whenever a vendor is mid-merger, teaches staff not to bother.
The through-line
Notice that all five are the vendor's design choices, not your team's failings. The inverse is a system built for the daily user: productive on day one with sensible defaults, fed by connected data so nobody re-keys, with help in the room when someone is stuck. Adoption is not a training initiative. It is a property of the product.
Keep reading
'Infinitely customizable' is a bill, not a feature
Endless configurability sounds like power. It is a transfer of work, from the vendor's product team to your staff, and the research on choice is brutal. When a study offered shoppers 24 options instead of 6, purchases collapsed. Software that ships as a blank canvas ships an adoption problem with it.
What Are CEUs, and Why They Matter for Behavioral Health Licensure
Continuing education units are the currency of staying licensed, but few people explain what they actually are or how to earn them well. Here is the plain version.
PHP vs. IOP: Which Level of Outpatient Care Is Right for You?
Outpatient treatment is not one thing. A partial hospitalization program and an intensive outpatient program differ in hours, intensity, and who they fit. Here is how to tell them apart.
If onboarding your software needs a 40-hour academy, the software is the problem
When a new admissions coordinator needs a certification course before they can do the job, that is not thoroughness. It is the vendor outsourcing its design debt to your staff's calendar. And in a field with 30 to 40% annual turnover, you pay that training tax several times a year.
Behavioral Health Updates is an independent industry publication published by vProGo.