Onboarding Shared Service Redesign
A shared-services center onboards 2,400 new hires a year across six countries. The target is five days from signed offer to ready-to-work, but the current average is 11 days. HR operations, IT service desk, and facilities each maintain separate trackers; 30% of new hires arrive without system access on day one and 18% have missing payroll documents. Four legacy systems-HR, payroll, IT provisioning, and badge-must remain because there is no budget for replacement. Compliance checks vary by country, and GDPR restricts sharing some personal data across borders. Nine months remain before peak hiring, and only two FTEs are available for automation work. The COO wants a to-be design that improves readiness without waiting for a new platform, and wants country variation handled explicitly rather than hidden in local spreadsheets.
1. Propose the to-be onboarding design at a level suitable for stakeholder sign-off. What should be eliminated, simplified, automated, and retained, and how should country variation be handled?
Read the worked answer
Design around a single trigger-signed offer-and a case record owned by HR operations. Eliminate duplicate trackers and repeated data entry; simplify offer and payroll forms to one structured intake; automate standard IT and badge provisioning through integration or RPA where APIs are unavailable; retain country-specific compliance checks and GDPR controls. Do not automate bad forms. Create a core process: pre-boarding data capture, compliance triage, payroll setup, IT/badge provisioning, and day-one readiness check. Handle country variation through a rules layer: a standard core plus a country compliance matrix that defines required documents, retention, and cross-border data restrictions. Use a role-based provisioning matrix by job family so standard roles auto-provision and exceptions route to a human. Set service levels: compliance decision within one day, provisioning two days before start. Eliminating duplicate entry and moving provisioning earlier could remove several days; a 5-day target is plausible only if pre-boarding starts before day one.
2. The IT service desk insists on keeping a manual ticket review before creating accounts. How do you decide whether to retain it?
Read the worked answer
Treat it as a control decision, not a turf decision. Quantify what the review catches: volume, error types, security incidents, and time cost. If it mainly catches missing or inconsistent data upstream, fix the intake and use validation rules; manual review is compensating for a design defect. For standard job families with approved role profiles, auto-provision with a post-check and audit sampling; for privileged, contractor, or exception roles, retain manual approval. Run a parallel test: auto-provision a sample, compare error and security outcomes, and calculate cycle-time savings. Require a rollback and logging. This preserves control where risk is real and removes it where it is ceremonial. The 30% day-one access failure suggests the manual review is not delivering readiness, so the burden of proof should be on retaining it.
3. Define three KPIs and two design guardrails for the new onboarding process.
Read the worked answer
KPIs: (1) Day-one readiness-percent of new hires with payroll, system access, badge, and required compliance complete on start date; target ≥98%. (2) First-pass compliance-percent of onboarding cases with complete documents at first submission; target ≥95%, because 18% missing payroll documents is a design symptom. (3) Cycle time from signed offer to all access ready, median and 90th percentile; target median ≤5 days and 90th percentile ≤8 days. Guardrails: privacy-no cross-border transfer of personal data unless the country matrix permits it, and role-based access limited to need-to-know; control-no auto-provisioning for privileged or contractor roles without human approval. Also monitor rework and manual touches to ensure automation does not hide errors. These measures keep the focus on readiness and compliance, not on how busy the shared-service team looks.