01
Automate dev environment setup
Dev containers, Nix, or a Makefile bootstrap. Saves 1-3 days per hire and removes the 'works on my machine' tax. Tools: Dev Containers, Gitpod, GitHub Codespaces, DevZero.
High impactMed effort
02
Pre-board starting day -7
Ship laptop early, create accounts, send architecture map. Eliminates day-one friction. The single highest-ROI change most teams can make.
High impactLow effort
03
Assign a buddy, not a mentor
Buddies are peers responsible for unblocking; mentors are senior engineers. Buddies cut senior interruption by 40%. Rotate every 4-6 weeks for fresh perspective.
High impactLow effort
04
First PR by end of week one
Top-performing teams get a new hire to their first commit in 1-2 days. The discipline of finding small, safe early tickets pays compound interest in psychological safety and confidence.
High impactLow effort
05
Recorded architecture walkthroughs
Record once, reuse for 12-24 months. Saves 4-6 hours of senior engineer time per hire. Tools: Loom, Tella, internal video portal.
Med impactLow effort
06
Living documentation and ADRs
Architecture Decision Records reduce 'why' questions by ~50%. Highest long-term ROI but expensive to backfill. Start with new decisions, then walk back.
High impactHigh effort
07
Standardise tooling
One IDE config, one linter, one test runner, one deploy command. Eliminates choice paralysis. Saves 1-2 days of setup per hire.
Med impactMed effort
08
Structured 30-60-90 day plan
Reduces ramp by 20-30%. Costs four hours of manager time per hire, returns $5k-$15k in faster ramp. The single best documented practice.
High impactLow effort
09
Internal developer portal (IDP)
Backstage, Cortex, Port, OpsLevel. Golden paths and self-service infrastructure compress onboarding by removing 'who do I ask' friction.
High impactHigh effort
10
Codebase orientation sessions
Two-hour walking tour of the architecture, quirks, and 'here be dragons' areas. Best run by someone who joined six months ago, not the original architect.
Med impactMed effort
11
Production-incident shadowing
New hire shadows on-call rotations from week six. Builds production intuition and trust. Leads to confident on-call eligibility by Day 60-90.
Med impactLow effort
12
Measure time-to-first-commit
What gets measured improves. Track it from day one and you will compress it. Tools: Jellyfish, LinearB, Swarmia, or a simple dashboard from Git history.
High impactLow effort
Priority matrix
Do first / plan second / consider third.
Do first
High impact, low effort. Start this quarter.
02 Pre-board starting03 Assign a04 First PR08 Structured 30-60-9012 Measure time-to-first-commit
Plan second
High impact, higher effort. Roadmap this quarter, ship next.
01 Automate dev06 Living documentation09 Internal developer
Consider third
Medium impact. Add when foundations are in place.
07 Standardise tooling10 Codebase orientation11 Production-incident shadowing05 Recorded architecture
matrix order