Milestone map
Milestone map
3 milestones
Write the onboarding program before hiring
2–3 weeks
Design a written onboarding program before the first engineer starts. Define what 'contributing to production' means and set checkpoints. Without a written definition, 90 days can't be measured.
Proof required
Submit the onboarding program: week-by-week plan, buddy assignments, first-task list, and the definition of production contribution with how it's measured.
What gets checked
- Clear, measurable definition of production contribution
- Week-by-week plan with named owners
- First real tasks prepared in advance
Common mistakes
- Starting hires before the plan exists
- A vague success definition
- No named buddy or owner
Powstik Guide
A written 90-day onboarding program.
Steps
- Define production contribution, like first shipped change.
- Set checkpoints at days 7, 30, 60 and 90.
- Assign a buddy and a manager owner per hire.
- Prepare a queue of small real first tasks.
- Write access and setup steps as a checklist.
Template
Onboarding plan Production contribution means: Day 1–7: Day 8–30: Day 31–60: Day 61–90: Buddy / owner: First tasks:
What gets sent back
- A plan written after hiring starts.
- An unmeasurable success definition.
- No named owners.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Check the success definition is measurable
- Check owners are named
- Check first tasks are real
You'll sign in first, then come straight back here.
Hire and onboard five engineers
8–13 weeks
Hire five engineers and run each through the program. Track every checkpoint for every hire. Fix the program as you learn from the early hires.
Proof required
Submit a tracker for all five hires showing start dates, checkpoint results and first production change dates, plus a list of program changes made.
What gets checked
- Five real hires tracked
- Checkpoint data for each
- Program updated based on early hires
Common mistakes
- Tracking only the good hires
- Checkpoints skipped when busy
- No changes despite problems
Powstik Guide
A checkpoint tracker for five real hires.
Steps
- Log each hire's start date.
- Hold every checkpoint, even when busy.
- Record first production change date.
- Ask each hire what slowed them down.
- Change the program and note why.
Template
| Hire | Start | Day 7 | Day 30 | First prod change | Day 90 status | |------|-------|-------|--------|-------------------|---------------| Program changes (date, change, reason):
What gets sent back
- Fewer than five hires.
- Missing checkpoints.
- No program changes noted.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Check all five are tracked
- Check dates are consistent
- Read the change list
You'll sign in first, then come straight back here.
Report results and defend them
1–2 weeks
Report how many hires reached production contribution within 90 days, and why. Defend the results to an experienced engineering leader. The honest numbers matter more than a perfect score.
Proof required
Submit a results report with time-to-contribution per hire and review notes (250+ words) with the reviewer's background and challenges.
What gets checked
- Time-to-contribution reported per hire
- Misses explained honestly
- Reviewer has led engineering teams
Common mistakes
- Hiding hires who missed
- Averages that hide spread
- A reviewer who only approves
Powstik Guide
An honest 90-day results report, reviewed.
Steps
- List each hire's days to first production change.
- Explain any hire who missed 90 days.
- Note what you'd change for the next cohort.
- Review it with an experienced engineering leader.
Template
| Hire | Days to contribution | Met 90 days? | Notes | |------|----------------------|--------------|-------| Review session log Date: Duration: Reviewer name: Reviewer role and experience: Challenge 1 (the results or the program): What they asked: My answer: Challenge 2: What they asked: My answer: Change I made after the session:
What gets sent back
- Hidden misses.
- Only an average reported.
- A reviewer without leadership experience.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Check each hire's figure
- Check misses are explained
- Confirm reviewer background
You'll sign in first, then come straight back here.