Give every new hire a real thirty-day operating plan
Each new hire receives a role-specific plan with outcomes, context, people, systems, first deliverables, and manager checkpoints.
The problem
Onboarding is a folder of links and meetings, leaving new hires to guess what good looks like and who can unblock them.
What you get
A working system with the steps, tools, checkpoints, and expected return made explicit.
- Setup
- 60 minutes
- Back each week
- 3 hours
- Difficulty
- assisted
Expected return
The working case
A planning estimate, not a guaranteed result. Measure the first four weeks against your own baseline.
144
hours returned per year
At 3 hours/week across 48 working weeks.
1
week to earn back setup
Compare the setup estimate with the weekly time returned.
Operating contract
Input
The source material, constraints, and examples a human would need to do this work well.
Checkpoint
A person reviews judgment calls, sensitive content, unfamiliar tools, and irreversible actions.
Success signal
Track time returned, corrections required, and exceptions. Keep it only if the measured result compounds.
Before you start
- ·Approved role scorecard
- ·Named onboarding owner
The steps
- 01
Combine the role scorecard, team operating rhythm, approved documents, systems, and manager expectations.
- 02
Draft week-by-week outcomes and a deliberately small first deliverable.
- 03
Create a plan with owners and links, marking anything that needs manager choice.
Copy this prompt
Draft a 30-day plan for [role]. Include context to learn, people to meet and why, systems access, weekly outcomes, first deliverable, manager checkpoints, and signs of confusion to surface. Use only supplied company context. Inputs: [bundle]
- 04
Manager personalizes and approves; the new hire can challenge and update it in week one.
What it runs on
Where this goes wrong
- Do not expose sensitive employee or customer information broadly.
- Meetings are inputs, not onboarding outcomes.
Definition of done
Run it for four weeks. Then make it earn its place.
- □ Baseline the manual time before launch.
- □ Keep a human approval step for consequential output.
- □ Record corrections and exceptions, not just successes.
- □ Expand, revise, or retire it after the first review.
Build the system around it
Related workflows
If this one stops working, tell us. Three reports in a month and it leaves the library until a person has looked at it again.