The launch went well. The system is live. The recruiters know how to use it.
Six weeks in, your req-to-hire cycle has slowed by 14 days and the project team can't explain why.
Look at the data. Hiring managers stopped reviewing candidates as quickly as they used to.
Approvals take longer. Some hiring managers have effectively gone dark.
The new system is working as built. The hiring managers just stopped using it the same way they used to, and the project team didn't catch it until the velocity numbers showed up in a finance review.
This is the most common silent failure mode in SuccessFactors-to-SmartRecruiters projects. The recruiter-side rollout is loud and well-resourced. The hiring manager side is an afterthought, and the afterthought costs you a quarter of req velocity.
Why hiring manager transition is the silent killer
Hiring managers are the highest-impact user group in your ATS and the worst-served by most implementation plans.
Impact: every action they don't take costs you a delay somewhere in the funnel. A hiring manager who delays a candidate review by 48 hours pushes your time-to-hire by 2 days. A hiring manager who stops reviewing candidates entirely pushes the whole req sideways while the recruiter chases them down.
Service: most implementation training plans budget 1 to 2 hours per recruiter and roughly 20 minutes per hiring manager. The hour-per-recruiter budget assumes deep learning on a tool that will be used in-depth, every day. The 20-minute budget for hiring managers aims to address a user that they may interact with the tool/process infrequently.
This can work well with experienced Hiring Managers if the tool/process is close enough to the old one. In a SuccessFactors-to-SmartRecruiters move, the UI is different, the workflow is different, the notifications are different, and the muscle-memory clicks lead nowhere.
Quick aside. Udder runs hiring manager change management as part of our SmartRecruiters implementations and as a standalone service for clients whose post-launch adoption has stalled. The view below is shaped by what we've watched move the numbers, not what training plans tend to assume.
What actually changes for hiring managers
The differences hiring managers will hit on day one, in priority order of operational impact:
- The "my reqs" view is structured differently. Where SuccessFactors gave hiring managers a list view of their open reqs, SmartRecruiters presents the same information with different navigation and different defaults. Five seconds of confusion per login might compound across 200 hiring managers, twice a day, for the first month or longer.
- Approval routing logic has changed. If your SuccessFactors approvals were tied to SAP HCM org-chart structures, SmartRecruiters routes differently. The same approval request that used to go to one manager may now go to two, or to a different layer, or get queued in a new place. Hiring managers who approved automatically before may now have to dig.
- Notifications are different. SuccessFactors's notification model is verbose by default and configurable per user. SmartRecruiters's is leaner by default. Hiring managers who relied on specific SuccessFactors email triggers won't get the equivalent in SmartRecruiters unless someone configures it. Mobile is better, but the bookmark is different. SmartRecruiters's mobile experience is genuinely a step up for most hiring manager use cases. The catch is the URL changed, the app is different, and a hiring manager who finally got the SuccessFactors mobile login working has to start over. Some will quietly stop trying.
- Scorecards work differently. If you ran structured interviews with scorecards in SuccessFactors, SmartRecruiters's evaluation model is different in shape. The fields, the weighting, and the workflow for filling them in will need re-introducing, especially for hiring managers who only fill scorecards three or four times a year.
- Permissions are subtly different. SmartRecruiters's permission model isn't a one-to-one copy of SuccessFactors. Some hiring managers will be able to do more than they could before, which is fine. Some will be able to do less, which is what they notice and complain about unless they understand why.
These are transition problems. Transition is what happens when someone has been doing it the old way for 3 years and the new way feels worse for the first month.
Training fills the knowledge gap. Muscle-memory is rebuilt by usage, scaffolded by reference materials and someone to call when stuck.
How to phase the rollout so hiring managers don't disengage
Six moves in priority order:
- Identify your power-user hiring managers first. Some hiring managers are heavy system users, others rarely log in. Onboard the heavy users first, in a small early cohort, and use them as your in-business advocates. They'll surface real adoption problems before the wider rollout catches them at scale.
- Send a "before-and-after" reference card to every hiring manager. Not training material. A one-pager that says: "the thing you used to click to do X is now this." Put it in their inbox the day before they get access. Five tasks max, the five tasks they actually do.
- Don't roll out new behaviour at the same time. If your project has any "let's also adopt scorecards" or "let's introduce structured interviewing" components, separate them from the migration by at least 6 months. Asking hiring managers to change the system and change the process at the same time is a multiplier on disengagement risk.
- Identify a named human per business unit. Hiring managers won't read help docs. They will ask a person. Name that person, publish their direct contact, and make sure they're real and have capacity to respond fast. A shared inbox isn't a person.
- Measure adoption from week 1, intervene by week 3. Don't wait for the first month's metrics. If a hiring manager hasn't logged in by week 3 after rollout, they're a disengagement risk. Outreach now is cheap. Outreach in month 3 is a recovery project.
- Set the post-launch expectation honestly. Tell hiring managers up front that the first month will feel slower. Surface that as a planned outcome with a known timeline, not as a defect. Hidden expectations are the source of most post-launch complaint volume.
Adoption metrics that matter, and the ones that look like they matter but don't
Two metrics worth tracking weekly for the first 3 months:
- Active hiring managers, by week. How many distinct hiring managers logged into SmartRecruiters and took at least one action (reviewed a candidate, approved, commented, created a req). Compare to your SuccessFactors baseline. If you're 20% below baseline after week 4, you have something to work on..
- Average time from candidate-ready-for-review to first hiring manager action. This is the single best leading indicator of whether hiring managers have actually adopted the system or are just logging in to keep HR off their back.
Three metrics that look meaningful but aren't, at least not for the first 90 days:
- Training completion rate. Hiring managers click through training to stop the reminder emails. Completion correlates weakly with actual adoption.
- Helpdesk ticket volume. Low ticket volume can mean the system is working. It can also mean hiring managers have stopped trying. You can't tell which one from the ticket data alone.
- NPS or satisfaction survey scores. Hiring managers answer surveys based on their last bad experience, and the first month of any migration produces some bad experiences. The score in months 1 to 3 is noisier than the underlying adoption pattern.
The post-launch checkpoint
In week 8 after go-live, run a 30-minute review with your TA leadership and HR business partners. Pull the two metrics that matter. Compare to the SuccessFactors baseline.
If the numbers are tracking back towards baseline, your transition is working, move on.
If they're significantly off (more than 15% below), you've got a recovery cohort to manage. The earlier you catch it, the cheaper the recovery.
By month 3, some hiring managers will have built workarounds that don't involve the system. Pulling them back from a workaround is harder than catching them before they built one.
Inside the first 60 days post-launch?
If your hiring manager numbers don't look like you expected, that's the conversation we're having most often this quarter. Udder is a SmartRecruiters partner. We've watched plenty of well-executed migrations slow at the hiring manager line, and we've got a working playbook for catching it before it shows up in finance reviews.