liveBook · Manning

Onboarding

As explained in Build High Value Software Systems

Onboarding is the process of helping a new team member become able to perform and deliver work within an organization.

Onboarding gets a new developer from joining a team to shipping useful code. Stale instructions, broken setup, and long waits create avoidable waste; measure the time from the first day to the first production deployment. section 13.5

Shorten that path by improving the work around the new hire:

  • Provide an automated setup script or container that creates a working environment in under thirty minutes. section 13.5
  • Prepare a small, real task that can ship on day one, such as a typo fix or an edge-case test. section 13.5
  • Replace stale wiki instructions with executable documentation. section 13.9

James’s first deployment

James waits for a buddy, follows outdated setup instructions, and submits his first pull request on day eight. His code reaches production on day twenty-two. Mapping those activities makes waiting and rework visible alongside the coding and review that add value. section 13.5

Table 13.2 Onboarding value stream analysis
Activity
Time
Classification
Reading stale wiki documentation
12 hours
Waste (defective information)
Configuring dev environment from outdated instructions
8 hours
Waste (rework, waiting)
Waiting for buddy availability
10 hours
Waste (waiting)
Waiting for first PR review
24 hours
Waste (waiting)
Actual coding on first task
6 hours
Value-add
Code review rounds (learning from feedback)
4 hours
Value-add
Meeting the team, understanding the domain
3 hours
Value-add
HR paperwork, compliance training
5 hours
Necessary non-value-add
Total
72 hours
18% value-add

Compare onboarding activities by time and classification to see where waste accumulates. section 13.5

How Build High Value Software Systems covers it

How deep it goes
Maps activities to value-add, waste, and necessary non-value-add, then recommends process changes without detailing their implementation.
Examples
Follows James through outdated documentation, setup delays, a first pull request on day eight, and production deployment on day twenty-two.
What it assumes
Assumes familiarity with value stream mapping and applies it to onboarding rather than teaching the mapping method from scratch.
What you can do after
Evaluate onboarding waste with value stream mapping and shorten time to production through automated setup, day-one tasks, and executable documentation.
How it connects
Connects onboarding to value stream mapping, waste reduction, automated environment setup, and executable documentation.

Also explained in

Compare how 5 books explain onboarding →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.