75% of new managers skip Step 4 (approval workflow configuration) during onboarding. Without it, schedule changes made by supervisors go live immediately with no manager visibility — causing payroll errors and compliance violations.
The product team's proposed fix is to make the step mandatory by removing the skip option and blocking progression until it is completed.
Before designing a fix, we need to understand the skip. There are three likely causes:
At the moment a manager reaches Step 4, they have just created a location profile and imported employees. They have not yet thought about who their supervisors are, what their approval hierarchy looks like, or how much autonomy to give each person. Asking them to configure an approval workflow at this point is like asking someone to set parental controls before they have children. The context does not exist yet.
"Define approval workflow" is product language, not manager language. A manager thinks in terms of: "Do I want to know when someone changes a shift?" or "Can my supervisors edit the schedule on their own?" The current label creates cognitive friction — the user does not immediately understand what they are being asked to decide.
The onboarding flow gives no signal about what happens if this step is skipped. There is no warning, no example of what a schedule change looks like without oversight, and no indication that payroll or compliance risk is involved. From the manager's perspective, skipping feels safe.
Making Step 4 mandatory removes the skip option and blocks progress until completion. This addresses the symptom (skipping) without addressing any of the three root causes. The risks are:
The goal is to ensure every location has a working approval configuration without forcing managers to make decisions they are not ready to make. The solution has two parts:
Instead of presenting a blank configuration screen, Step 4 arrives pre-filled with a sensible default: "All schedule changes require your approval." This is the safest default for the business — it ensures nothing goes live unreviewed.
The manager's choice becomes: confirm the default (one click) or customize it. Most managers will confirm and move on. The step still gets completed, the workflow is configured, and no one is blocked.
The language is also rewritten in plain terms: "Who can make schedule changes without your review?" rather than "Define approval workflow."
For the minority who skip (or select "do this later"), the dashboard shows a persistent but non-blocking warning banner: "Schedule changes are going live without your review. Set up approvals to stay in control." The banner links directly back to the configuration step.
This nudge also fires as a contextual alert the first time a supervisor makes a schedule change with no workflow set — catching managers at the exact moment the consequence becomes real and visible.
Even with the nudge, some managers will not return to configure approvals. The design must account for this gracefully:
If time allowed, these are the questions worth testing before building:
Suggested research methods:
Every decision below was made to solve the root causes, not just the symptom of skipping.
| Decision | Why | Tradeoff Considered |
|---|---|---|
| Smart default pre-fills Step 4 | Removes friction for the majority; ensures a safe config exists from day one | Could train users to accept defaults without reading — mitigated by plain-language rewrite |
| Skip option stays (not mandatory) | Mandatory gates cause abandonment when users lack info; misconfiguration is worse than no configuration | Business risk of some locations going unconfigured — mitigated by safe fallback default |
| Dashboard warning banner | Makes the consequence visible at the moment managers return to work, not just during setup | Banner fatigue — mitigated by allowing dismissal once the step is completed |
| Contextual alert on first supervisor change | Catches managers at the exact moment the risk becomes real and personal | Could feel intrusive — framed as informational, not an error state |
| Safe fallback (all changes need approval) | Worst-case scenario is over-caution, not a compliance violation | May frustrate supervisors wanting more autonomy — surfaced in dashboard Settings |