Test capacity and routines, then measure the decisions
An HR initiative can have executive support and still be difficult for managers to carry out within the working week. The rollout may add meetings, documentation, and follow-up without reducing other demands. Before interpreting limited adoption as disagreement, examine where the required activity is supposed to fit and whether managers have the time and support to do it well.
“Before interpreting limited adoption as disagreement, examine where the required activity is supposed to fit and whether managers have the time and support to do it well.”
Span of control is one part of that assessment. A manager responsible for 14, 18, or 25 people faces different demands depending on the work, team experience, and available support. Gallup's research on team size finds that the effect of a larger span depends on manager characteristics and working conditions; it does not establish a universal maximum. Estimate the time required for conversations, development planning, and follow-up alongside the manager's other responsibilities.
Tool and process friction can increase the time required. Ask managers to complete representative tasks and observe repeated data entry, unclear approvals, and time spent finding information. Multiply the effort by the relevant team size and frequency. The result gives the rollout team a more credible capacity estimate than a claim that each step takes only a few minutes.
Existing business reviews, shift-start huddles, one-to-ones, and performance discussions may provide a useful place for a new activity. Check whether the purpose, participants, timing, and confidentiality fit. Adding an item to an already full meeting can still create extra work or reduce the attention given to another responsibility. Make that trade-off explicit.
A new meeting may be warranted when the decision needs different participants or protected time. If so, identify what will be removed, shortened, deferred, or supported with additional capacity. The design question is whether the required behavior has a workable place in the manager's responsibilities, not whether every initiative can use an existing calendar slot.
Translate the policy into specific actions. For example, a development initiative might change the preparation for a one-to-one, the discussion itself, and the follow-up on an agreed opportunity. Specify each step and the information it needs. Managers can then test a defined routine, and the rollout team can see which part creates unnecessary effort or remains unclear.
Map the proposed activity against representative managers' calendars and responsibilities before launch. Include roles with different spans of control, shifts, and administrative support. Test whether an existing meeting can accommodate the work without displacing a more urgent purpose. Where it cannot, adjust the scope, remove competing work, add support, or revise the timing. Extending the schedule helps only if it reduces the workload during the relevant period.
In matrixed organizations, map overlapping demands from different leaders. Regulatory and union requirements may constrain which activities can change, but they do not make every existing meeting necessary. Identify the obligations that must be preserved, coordinate competing requests, and simplify discretionary reporting where possible. Choose a manageable set of required behaviors and give managers a clear route to report conflicts.
When an initiative stalls, examine the actual time and sequence required to carry it out. Identify the task that is being missed, the competing demand, and the change that would make completion feasible. Capacity is one possible cause alongside incentives, skills, clarity, and process design. Establish which explanation fits before selecting the remedy.
An adoption dashboard can show completed training and regular system use without establishing that managers make decisions differently. The distinction matters when an HR transformation depends on a change in judgment or practice. Completion measures answer useful questions about exposure and participation. To assess the intended behavior, define the decision that should change and look for evidence in how managers handle it.
“An adoption dashboard can show completed training and regular system use without establishing that managers make decisions differently.”
Consider a rollout in which managers receive training and begin using a new process. Routine transactions progress, but unusual requisitions, accommodation requests, or performance cases take longer. Managers seek help from HR business partners or use a workaround. Several months later, system use is high while the expected outcome remains unchanged. That sequence is a scenario to investigate, not a fixed timetable or proof that the transformation failed.
A proposal to relaunch should prompt a review of what the existing measures establish. Outcomes may lag, the intervention may be insufficient, or another change may offset its effect. It is also possible that use increased without the intended behavior changing. Distinguish those explanations before deciding whether the response should be further training, process repair, different measurement, or a revised objective.
Completing training, entering a required field, and logging into a system are different activities. None of these activities necessarily shows that a manager applied a new decision rule well. For example, a completed performance form may contain clear evidence and useful feedback, or it may repeat last year's judgments. Identify what a meaningful application looks like and choose evidence that can distinguish it. Retain completion data for the questions it can answer rather than ask it to demonstrate an outcome it does not measure.
After a workflow change, ask managers how long a relevant task took, what was difficult or unclear, and what they did when the intended route did not work. Include the option to report that the process worked as intended. These questions can reveal issues a completion rate misses, but the answers remain self-reported and may reflect selective recall or concern about blame. Use a clear purpose and appropriate confidentiality to encourage useful feedback.
Follow the feedback into representative cases. If a manager bypassed a new route to resolve a payroll problem, examine the time pressure, information available, and outcome. The workaround may reveal a design defect, an unclear rule, or avoidance of a workable process. Compare the account with permitted workflow records and other users' experience. Collect only the detail needed to evaluate the process, particularly for sensitive employee matters.
If system use improves while the intended outcome does not, review the expected sequence of effects. Was the behavior supposed to change first? How long should the outcome take to respond? Were comparable populations measured, and did other conditions change? A flat outcome is a reason to test the connection between the intervention and the result, not sufficient evidence that the metric was never relevant.
Use the findings to refine the response. If managers apply the new rule but cases still stall, investigate the next handoff or the rule itself. If they use the system without applying the rule, establish whether the cause is unclear expectations, inadequate support, conflicting demands, or another issue. Repair the measure where it cannot distinguish those conditions, and evaluate the operating change where it can.
A useful adoption review connects three kinds of evidence: participation, application, and the intended result. Each serves a different purpose. Read them together, investigate disagreement between them, and make the next decision from what the evidence shows rather than from the dashboard's overall status.
Connex convenes HR and people-operations executives in Trusted Peer Groups to compare where a new routine fit in the manager's week and what evidence showed it was being used. Ask peers how they checked the relationship between reported use, management behavior, and outcomes, including cases where the measures gave different answers.