By Scott Scoble in DX First Principles — 26 Feb 2026

The Onboarding That Actually Works

Hook: Your new hire's first week is reading documentation, attending HR sessions, and feeling lost. By month three, they're wondering if they made a mistake. Here's how to fix that.

Most engineering onboarding is terrible.

Week one: HR paperwork, IT setup, compliance training, reading docs that nobody reads.

Week two: "Shadow" someone, which means watching them work without understanding why.

Week three: Get assigned a "starter project" that doesn't matter to anyone.

Month two: Still not sure what you're doing, who to ask, or whether you belong.

Month three: Seriously wondering if you should have taken the other offer.

This is how you turn excited new hires into disengaged employees.

Why Onboarding Fails

It's information transfer, not formation. Onboarding is treated as "give them the docs, give them access, send them to the team." Information is transferred. Habits are not formed.

It lacks human connection. Reading documentation is not the same as having a relationship with someone who will answer your questions without judgment.

It's passive, not active. Watching and reading is passive. Learning happens through doing. Passive onboarding doesn't create skill.

It's front-loaded and forgotten. Week one gets attention. Months two through six are neglected. But most of the adjustment happens after week one.

It doesn't account for archetype. A Fast Grower needs different onboarding than a Deep Root. One-size-fits-all doesn't work.

Onboarding by Archetype

For Tall Stalks (Systems Thinkers)

What they need: Context about how systems connect. The big picture. Historical decisions that shaped the architecture.

First month: Pair them with another systems thinker who can explain why things are the way they are, not just what they are. Give them architecture docs—but also give them someone to interrogate.

Key milestone: Can they draw the system architecture from memory? Can they predict where a change in one system affects another?

For Nitrogen Fixers (Mentors)

What they need: Relationships with people they'll mentor. Understanding of how learning happens here.

First month: Introduce them to the junior engineers they'll work with. Let them observe how mentorship currently happens. Give them permission to start teaching early.

Key milestone: Have they established relationships with mentees? Do they understand the team's current skill gaps?

For Ground Cover (Reliable Executors)

What they need: Clear expectations. Defined scope. Visible queue of work.

First month: Give them real work immediately—not a fake starter project. Start with smaller tasks that build to larger ones. Make expectations crystal clear.

Key milestone: Are they delivering consistently? Do they understand what "done" means here?

For Pollinators (Connectors)

What they need: Introductions across the organization. Context about who does what and where the boundaries are.

First month: Schedule introductions with people across multiple teams. Explain the organizational structure and where collaboration happens (and where it should happen but doesn't).

Key milestone: Can they navigate the organization? Have they made connections that didn't exist before?

For Deep Roots (Knowledge Holders)

What they need: Access to people with institutional knowledge. Permission to go deep.

First month: Pair them with current Deep Roots who can transfer context. Give them time to explore systems in depth, not just surface level.

Key milestone: Are they starting to accumulate knowledge that they can retain long-term? Are they building relationships with people who hold historical context?

For Fast Growers (High-Potential Juniors)

What they need: Mentorship. Challenge calibration. Fast feedback loops.

First month: Assign them to a mentor explicitly. Give them stretch opportunities that are just beyond their current capability. Check in frequently—Fast Growers need more feedback, not less.

Key milestone: Can you see measurable growth from week one to week four? Are they asking good questions?

The 30-60-90 Structure

Good onboarding is a journey, not an event.

Day 1-30: Learn Focus on context, relationships, and basic orientation. New hire should be observing and absorbing, with increasing small contributions.

Day 31-60: Contribute Focus on real work with support. New hire should be delivering real value with guardrails. Mistakes are learning opportunities, not failures.

Day 61-90: Own Focus on independent contribution. New hire should be operating with decreasing supervision, taking ownership of meaningful work.

At day 90, you should know: Is this person thriving? What support do they need? Did we hire right?

The Secret Ingredient: A Human

The single most effective onboarding intervention is assigning a specific human who is responsible for the new hire's success.

Not HR. Not the manager (though managers matter too). A peer—someone who will:

Answer the "stupid" questions
Provide context that isn't in docs
Notice when they're struggling
Help them navigate the social landscape
Advocate for them when needed

This is a real assignment with real time allocation—not a volunteer favor.

The Red Flags

Signs your onboarding is failing:

New hires still seem lost after 30 days
They ask the same questions repeatedly (bad docs or bad relationship)
They hesitate to ask questions at all (bad safety)
They deliver work that misses expectations (bad clarity)
They leave within 6 months

Track these. When patterns emerge, fix the onboarding.

The Investment Math

"We don't have time for better onboarding."

Let's do the math:

New hire salary: $150k/year
Time to productivity with bad onboarding: 6 months
Time to productivity with good onboarding: 2 months
Value of 4 months of additional productivity: ~$50k
Cost of good onboarding: A few days of existing employees' time

Good onboarding isn't a cost. It's the highest-ROI investment you can make in a new hire.

And that's before counting reduced turnover.

The Formation Frame

Here's the reframe:

Onboarding isn't about information transfer. It's about habit formation.

You're not trying to fill their head with facts. You're trying to shape their daily practice. You want them to develop the habits that make engineers successful at your company.

That happens through doing, not reading. Through relationships, not documentation. Through practice, not orientation.

Form them. Don't just inform them.

Next in series: "Retention Is Onboarding That Never Ends"