VOL 003CHROOnboarding - Time-to-productivity - Probation

Bad onboarding looks like a people issue. It usually becomes an execution issue

Week 3 people systems should reduce time-to-productivity. Use a Day 1-7 onboarding checklist, assign a buddy, define first-week wins, and make probation visible with Day 7 and Day 30 checkpoints. New hires should not spend their first week collecting confusion as if that were training.

Many MSMEs spend energy selecting people and then waste the gain by onboarding badly. The new person arrives, access is incomplete, expectations are vague, SOPs live in someone's head, and everyone assumes they will 'pick it up.' What they actually pick up is confusion. Then three weeks later the business says the person is not proactive enough. Often the system never gave them a fair start.

Week 3 should make onboarding operational, not ceremonial. Day 1 must cover access, role clarity, reporting line, customer communication rules, attendance basics, and the first useful task. Day 2 to Day 7 should include product or process familiarisation, one small observable win, and a buddy or go-to person for questions. This dramatically reduces founder interruption and stops the new hire from learning the wrong shortcuts.

Probation should also become visible early. A Day 7 check asks: are they showing up correctly, learning the work, and closing simple loops? A Day 30 check asks: can they now own recurring tasks with acceptable quality and pace? Those two checkpoints turn onboarding from vibes into signal. Good people respond well to clarity. Weak systems produce delayed disappointment for everyone.

The Week 3 metric to watch is not just retention. It is time-to-productivity: how quickly a new person becomes useful without constant rescue. That is the people number that actually protects growth.

  • Day 1 to Day 7 onboarding should cover access, role clarity, communication rules, and one early win.
  • Add a buddy and visible Day 7 and Day 30 probation checkpoints.
  • Track time-to-productivity, not just retention, if you want onboarding to protect execution.

Turn the first week into a planned operating handoff, not an improvisation.