Onboarding & Probation System
Two startups inside an IT holding (AI customer support and GameDev), around 80 people, hiring steadily, remote and office mixed. I was their People Partner.
Problem
Probation was a formality. It got closed on time, and then a few months later the lead realised the person wasn't right. New hires told us the same story in different words: access arrived late and depended on one person, there was no knowledge base, teams were isolated, and it was unclear who to go to.
Solution
Talked to new hires, mapped their journey from offer to end of probation, and built a 30/60/90 toolkit in Notion for leads and HR, with an adaptation index and a probation tracker synced from PeopleForce.
- first check on fit, instead of months 4–6
- Day 30
- first check on fit, instead of months 4–6
- templates for leads and HR
- 12
- templates for leads and HR
- CustDev interviews with new hires
- 6
- CustDev interviews with new hires
How it works
Three rhythms
Lead and employee: a weekly 1:1 in month 1, then bi-weekly, plus reviews at D30, D60 and D90. HR and employee: a pulse at D5, D25, D55, D85. HR and lead: a short sync after each pulse.
Statuses
Green: on plan, keep going. Yellow: risks, a 2–4 week development plan with support. Red: no progress, escalate to HR and the lead and prepare a decision.
Ground rules
The conversation is 50/50: half the employee's self-assessment, half the lead's assessment and plan. Facts, not impressions. A red flag is raised right away, not at the next review.
D30 review template
Goal: understand whether the person has settled in. Must-ask: "What was the hardest part of the first 4 weeks?", "Where did you lack information or support?" Output: goals for month 2 and a G/Y/R status. After each pulse HR sends the lead 3 lines: what's OK, risks, next steps.
Adaptation Index
0–10, the average of 12 questions in 5 blocks: pre-arrival, day 1 and access, week 1, goals, belonging. Risk signal: "day 1 and access" below 7, or more than 20% of answers at 0–6.
Probation tracker
Every hour the script reads PeopleForce and updates two sheets: "On probation" (name, role, start date, probation end, days left; 7 days or less highlighted) and "Closed probations".
Outcome
- A mismatch now shows up at the D30 or D60 review, not months after probation closes, which is when people used to leave.
- One probation standard for leads and HR across both startups, used by the People Partner team.
- 12 ready templates instead of a blank page before every review.
- HR sees upcoming probation ends without opening PeopleForce.
- Every new hire got a personal onboarding dashboard on tools the company already had, and leaving got its own offboarding process.
- The CustDev findings fed the to-be onboarding: an owner for day 1, an access SLA, a contact map, a buddy as the entry point, and a check-in plan at weeks 1, 4 and 8.
What I did
- Ran 6 CustDev interviews with recent hires (office and remote, first month and closer to month 3).
- Drew the journey map as-is and to-be: 6 stages from offer to end of probation, with actions, touchpoints, pain points and opportunities.
- Designed an Adaptation Index (12 questions, 5 sub-indices) and short pulses at month 1 and month 2.
- Built the Probation Toolkit in Notion: separate flows for the lead and for HR, ground rules for the conversations, 12 templates.
- Wrote an Apps Script that pulls everyone on probation from PeopleForce into a Google Sheet, so HR sees whose probation ends next.
Screens
My role
Research, design and build, by me; agreed with the leads and the People Partner team.
Stack
Notion · PeopleForce API · Google Apps Script + Google Sheets · Miro (journey map).
Next case
Internal Comms From Zero