Case Study: Engineering Adoption — ERP and CRM Implementation Across a Multi-Campus Senior Living Organization
40%Â reduction in user resistance
700+Â employees trained
25% / 30%Â productivity increase/improvement in satisfaction
The Situation
Â
A multi-campus senior living organization undertook a full-lifecycle implementation of Yardi ERP and Aline CRM — replacing the systems that managed its finances, operations, and resident relationships across all campuses simultaneously.
Â
The technical risk was manageable. The human risk was not. The workforce spanned accounting professionals, campus operators, sales teams, and frontline staff — many with years of habit invested in the old systems, and most with no reason to welcome new ones. Industry experience is blunt on this point: enterprise implementations rarely fail at configuration. They fail at adoption, after go-live, when the project team has moved on, and the workforce quietly reverts to workarounds.
Â
The Approach
Â
What made this implementation unusual was that the person who designed the change strategy was the same person administering the system: an organizational psychologist. Dr. Rawe directed both the technical implementation and the human side of the change — meaning adoption was engineered into the rollout rather than appended to it.
​
Change readiness before go-live. Resistance was treated as data, not disobedience. Likely friction points were identified by role and campus and addressed in the rollout sequence rather than discovered in the aftermath.
​
Role-based training, not system tours. Each employee group was trained on its own workflows in the new system — the twenty things they would actually do — rather than marched through generic feature demonstrations. Training effectiveness was measured at multiple levels using Kirkpatrick-aligned evaluation, so the organization knew what was learned, not just what was attended.
​
Managers as the front line of change. Supervisors and campus leaders were equipped to model the new systems, answer the first wave of questions, and reinforce adoption daily — because employees take their cues about whether change is real from their direct leaders, not from project announcements.
Â
The Results
Â
User resistance fell by 40% relative to the organization’s baseline expectations — and adoption held steady after go-live. The enterprise training program ultimately reached more than 700 employees and contributed to a 25% increase in productivity, a 15% reduction in turnover, and a 30% improvement in employee satisfaction. The systems became how the organization works, not a mandate it tolerates.
Â
The Takeaway
Â
Your implementation partner will configure the software correctly. Whether your people adopt it is a separate discipline — one grounded in psychology, training design, and leadership alignment. Organizations that engineer the human side of implementation get the system they paid for. Organizations that don’t get a very expensive license.
Â
Implementing Yardi, Aline, or another enterprise platform?