Digital Transformation & Change
Change Management for Staffing Technology Projects
Lauren B. Jones
CEO & Founder, Leap Advisory Partners
Lauren B. Jones
I can tell you within the first week of a technology rollout whether it will succeed or fail. Not by looking at the technology. By looking at the people.
When recruiters lean in during training, ask questions, and immediately start figuring out how to adapt their workflow, the project will succeed. When they sit with crossed arms, answer questions with "but that is not how we do it," and go back to their desks to use the old system, it does not matter how good the technology is. It will not be adopted.
Seventy percent of technology projects fail. Not because the technology does not work. Because the people do not change. That statistic has been consistent for over a decade, across industries, across company sizes, across technology categories. And in staffing, where the workforce is competitive, independent, and often resistant to anything that disrupts their personal productivity formula, the failure rate can be even higher.
The fix is not better technology. It is better change management.
The adoption problem is the single largest determinant of whether a technology investment produces a return, yet it almost never gets a budget line item. I review technology project budgets regularly, and the pattern is consistent. There is a line item for the software license. A line item for implementation services. Sometimes a line item for data migration. Occasionally a line item for training.
There is almost never a line item for change management.
And yet, change management is the single largest determinant of whether the technology investment produces a return. A $100,000 ATS with 90% adoption produces more value than a $300,000 ATS with 40% adoption. The math is simple. The execution is not.
The adoption problem compounds over time. Day one, 80% of users log into the new system. By week two, 60% are using it consistently. By month three, 40% have reverted to their old workflows, using spreadsheets, personal tools, or the old system that was supposed to be decommissioned. By month six, the agency has two systems running in parallel, data in both, and neither is a reliable source of truth.
I have watched this happen at agencies that spent over $500,000 on technology implementations. The technology worked perfectly. The adoption failed. And nobody had budgeted for the work of making adoption succeed.
Resistance to technology change in staffing is rational self-protection, not stubbornness, and understanding the root cause is the first step to overcoming it.
Productivity dip fear. Recruiters live and die by their numbers. Activity metrics, submission counts, placements. Every recruiter knows that switching to a new system means being slower for weeks. Being slower means lower numbers. Lower numbers mean uncomfortable conversations with managers, lower commissions, and anxiety about job security. The fear is not irrational. The productivity dip is real. A recruiter who is 30% less efficient during a system transition is 30% less effective at their job.
Relationship disruption anxiety. Staffing is a relationship business. Recruiters worry that a system change will disrupt their candidate relationships: that notes will be lost, that history will disappear, that the personal touches they have built into their workflow will be erased. These concerns are often valid. Data migrations are imperfect. Formatting changes. Context gets lost. The recruiter's fear of losing years of relationship data is a legitimate concern that needs to be addressed directly.
"My way works fine" mindset. Your top biller has been using the current system for eight years. She has shortcuts, workarounds, and a personal efficiency system that produces results. Telling her to start over feels like telling her that her eight years of built expertise do not matter. From her perspective, the new system has to prove it is better than what she already has. And that proof has to come before she invests the time to learn it.
The ADKAR framework adapted for staffing addresses the human side of change in five structured, measurable stages.
Awareness. People need to understand why the change is happening. Not "the new system is better." Why. What business problem does it solve? What competitive threat does it address? What happens if we do not change? Awareness is about context, and in staffing, the context needs to be personal. "This change will help you make more placements with less admin time" resonates more than "this change will improve operational efficiency."
Desire. People need to want the change. Desire is emotional, not logical. You build desire by showing people what is in it for them specifically. For recruiters, that might be fewer hours on data entry. For managers, that might be better reporting. For leadership, that might be scalability. Tailor the message to the audience.
Knowledge. People need to know how to operate in the new system. This is where training lives. But training in staffing needs to be practical, role-specific, and repeatable. A single four-hour training session does not create knowledge. Repeated, contextual training, where people learn by doing real work in the new system, creates knowledge.
Ability. People need the capability to perform their jobs in the new system. Ability comes from practice, support, and time. The gap between knowledge ("I know how this works") and ability ("I can do my job efficiently in this system") is where most change initiatives fall short. Bridge that gap with hands-on coaching, accessible support resources, and patience.
Reinforcement. People need to see that the change sticks. Reinforcement means celebrating wins, addressing regression, and demonstrating that leadership is committed for the long haul. If leadership stops talking about the new system after 30 days, the team interprets that as permission to stop caring about it.
Champion networks. Identify 1-2 people per office or team who are tech-curious, respected by peers, and willing to learn the system early. Train them two weeks before the general rollout. Give them a title: "System Champion" or "Power User." Make it visible. These champions become the first line of support for their peers, and peer support is more effective than formal support because the social dynamics are different. Nobody wants to look incompetent in front of the IT helpdesk. Everyone is willing to ask a colleague for help.
Staged rollouts. Do not launch the new system to 200 people on the same day. Start with one office or one team. Learn from their experience. Fix the problems they find. Then roll out to the next group. Each wave teaches you something, and each wave goes more smoothly than the last.
Visible wins. When someone makes their first placement using the new system, make it visible. Share it in a company meeting, a Slack channel, an email. When a team discovers a time-saving feature, broadcast it. The narrative around the new system should be one of wins and progress, not problems and complaints.
Feedback loops. Create a simple, fast mechanism for users to report problems and request help. A dedicated Slack channel, a daily 15-minute office hours session, a weekly "what is not working?" survey. The act of listening reduces resistance because people feel heard. And the feedback gives you specific, actionable intelligence about what needs to be fixed.
System login counts tell you who is opening the system. They do not tell you who is using it effectively. Measure these three dimensions instead.
Adoption curves. Track the percentage of users completing core workflows in the new system over time. Core workflows are the 3-5 actions that represent real work: creating candidate records, submitting candidates to jobs, logging activities, running reports. Plot adoption weekly. A healthy adoption curve rises steeply in weeks 1-3, plateaus slightly in weeks 4-6, and reaches 85%+ by week 8. If the curve flattens below 70%, intervention is needed.
Productivity recovery timelines. Measure how long it takes for key metrics (submissions per recruiter, time-to-fill, activity volume) to return to pre-change levels. Expect a dip. Plan for it. But track the recovery. If productivity has not returned to baseline within 60 days, investigate why. Is it a training gap, a configuration issue, or a change management failure?
Sentiment tracking. Run a simple 3-question survey at 30 and 60 days post-launch: How confident are you using the new system (1-5)? What is the biggest challenge you face with the new system? What feature or change would improve your experience most? The quantitative score tracks sentiment over time. The qualitative responses tell you where to focus.
Not every complaint is a signal to change course. But not every complaint is resistance to be pushed through.
Course-correct when: The same problem is reported by multiple people across different teams. The system has a genuine limitation that forces inefficient workarounds. A core workflow takes significantly more time in the new system than it did in the old one. These are legitimate issues that need to be fixed.
Push through when: The complaint is about the learning curve, not the system. When someone says "I could do this faster in the old system," the answer is: "Yes, and you will be faster in the new system too, once you have the same practice time." The discomfort of learning is temporary. Reverting to the old system because learning is uncomfortable guarantees that the investment fails.
The judgment between course-correcting and pushing through requires knowing your team and trusting your data. If adoption metrics are trending upward and productivity is recovering, push through the discomfort. If adoption is flat and productivity is declining after 60 days, something needs to change, and it might not be the people.
Technology projects fail because of adoption, not functionality. The platforms work. What fails is the process of getting people to use them. In staffing specifically, recruiters are competitive, independent, and protective of personal workflows that produce results. Without structured change management, including communication, training, support, and reinforcement, adoption declines from 80% on day one to 40% by month three.
ADKAR is a five-stage change framework adapted for staffing: Awareness (explain why the change is happening in personal terms), Desire (show individuals what is in it for them), Knowledge (practical, role-specific, repeatable training), Ability (bridge the gap between knowing how and performing efficiently through coaching and time), and Reinforcement (celebrate wins, address regression, demonstrate sustained leadership commitment).
Measure three dimensions beyond login counts: adoption curves (percentage of users completing core workflows weekly, targeting 85%+ by week 8), productivity recovery timelines (how long until submissions per recruiter and time-to-fill return to pre-change levels), and sentiment tracking (3-question surveys at 30 and 60 days measuring confidence, biggest challenges, and desired improvements).
Recruiter resistance comes from three rational fears: productivity dip fear (being slower means lower numbers, lower commissions, and uncomfortable conversations), relationship disruption anxiety (losing years of candidate notes and personal workflow touches during migration), and the "my way works fine" mindset (top performers have built efficient systems in the current tool and see no reason to start over). Address these fears directly with data, empathy, and adjusted KPI expectations during transition.
Launching a technology project? Download the Change Management Playbook Template. It includes a stakeholder analysis tool, communication plan framework, champion network guide, and adoption measurement dashboard.
Download the Change Management Playbook Template
Lauren B. Jones is the CEO and founder of Leap Advisory Partners, with 28 years of experience in staffing technology. She helps staffing agencies, PE firms, and software companies build technology that actually works.
