Define day-30 capability
Name the work the person should perform with agreed support by the end of the first month.
← All toolkits
Manager routines
30-Day Onboarding Plan
Sequence context, relationships, practice and early ownership so onboarding is more than an information dump.
Use this when
Start with a live team problem.
- New starters receive access but not operating context.
- Managers cannot tell whether onboarding is working.
- Time to independent contribution varies widely.
How to use it
Move from context to one usable agreement.
Sequence learning through work
Combine context, observation, practice and feedback around real responsibilities.
Make support visible
Assign a manager, working buddy, access owner and clear checkpoints.
Worked example
Operations Coordinator
Use the example to understand the level of specificity. Replace the content with evidence from your own team.
DAY-30 OUTCOME Coordinate the weekly fulfilment workflow, surface exceptions and publish the operating update with manager review. WEEK 1: UNDERSTAND - Customer promise and fulfilment outcome - Systems, terminology and key relationships - Observe one full workflow cycle WEEK 2: PRACTISE - Run the workflow with a buddy - Record exceptions and questions - Draft the weekly update WEEK 3: OWN WITH REVIEW - Coordinate one cycle - Escalate exceptions using the agreed rules - Receive structured feedback WEEK 4: DEMONSTRATE - Own the cycle with exception-only support - Review measures and suggest one improvement SUPPORT Manager: weekly progress and priorities Buddy: daily workflow questions for two weeks
Blank template
30-Day Onboarding Plan
Copy this into Docs, Notion or your existing workspace, or print it for a team conversation.
30-DAY ONBOARDING PLAN Role: New team member: Manager: Start date: DAY-30 OUTCOME WEEK 1: UNDERSTAND - Context: - People: - Systems: - Work to observe: WEEK 2: PRACTISE - WEEK 3: OWN WITH REVIEW - WEEK 4: DEMONSTRATE - SUPPORT - Manager: - Buddy: - Access owner: CHECKPOINTS - End of week 1: - End of week 2: - End of day 30: EVIDENCE OF READINESS -
The System Folks · Free founder resource · thesystemfolks.com/resources/30-day-onboarding-plan
Common mistakes
Keep the tool connected to real work.
- 01
Measuring onboarding by completed reading instead of demonstrated work.
- 02
Front-loading information before the person has context to use it.
- 03
Leaving support relationships and checkpoints informal.
Why this works
Evidence behind the resource
Capability, opportunity and motivation interact to make a target behaviour possible.
Read COM-B behaviour frameworkNeed help implementing it?
A template can reveal a bigger operating problem.
If onboarding exposes unclear roles, undocumented work or inconsistent quality, we can help fix the operating system new starters are entering.
Contact us when one costly workflow or team bottleneck needs diagnosis, build support and adoption.
Get implementation support Use another toolkit