Skip to content

Onboarding and Role Shadowing Runbook

Competence-building process — instantiates Role Expectation Architecture

A structured ramp that brings a new holder up to a role's competence bar by provisioning support and mentorship and by having them learn through supervised shadowing of an experienced holder.

An Onboarding and Role Shadowing Runbook is the scaffolded journey from appointed to competent. Its defining move is that competence is built through participation over time, not assumed at the moment of hire: the runbook provisions the support a newcomer needs — a mentor, materials, access, protected ramp time — and sequences a period of shadowing an experienced holder before the newcomer works alone. This is what sets it apart from its neighbours: a position description defines the competence bar and a handoff checklist transfers one departing holder's live state in a single event, whereas this runbook is the weeks-long process that closes the gap up to the bar.

Example

A school district runs an induction program for first-year teachers rather than dropping them into a classroom cold. The runbook provisions the scaffold: each new teacher is assigned a mentor teacher, given a reduced initial course load (protected ramp time), and scheduled into a sequence of shadowing veterans and being observed in return. It also defines the competencies to reach by term's end — classroom management, the grading system, parent communication — and checks them along the way.

By a known milestone, the new teacher is operating independently, with the tacit craft that no manual conveys picked up by watching it done. Structured induction and mentoring of this kind is a recognized practice precisely because it turns shadowing into legitimate peripheral participation — the newcomer learns the role by doing a real, supervised slice of it alongside someone fluent, rather than sinking or swimming.[1]

How it works

  • Provision the scaffold. Arrange the mentor, materials, access, and protected time a new holder needs to become effective.
  • Sequence the ramp. Move the holder through shadow → supervised practice → independent work, rather than starting them solo.
  • Define and check milestones. Name the competencies the holder must reach and verify them along the way, so "onboarded" means demonstrated rather than elapsed.
  • Fade the support. Withdraw mentorship and protected time as competence grows, handing the role fully to the new holder.

Tuning parameters

  • Ramp length — how long the supported period runs. Longer produces more secure competence at the cost of mentor time and delayed full productivity.
  • Support intensity — heavy mentorship and reduced load versus sink-or-swim. Intensive is safer and expensive; thin is cheap and raises early-failure and burnout risk.
  • Shadowing ratio — observation versus supervised doing versus solo work. More doing builds competence faster but risks live mistakes.
  • Milestone strictness — hard competence gates versus soft targets. Gates ensure readiness before independence; they can also bottleneck a holder who is ready.
  • Fade schedule — abrupt versus gradual withdrawal of support. Gradual is gentler and ties up the mentor longer; abrupt frees resources and can strand the newcomer.

When it helps, and when it misleads

Its strength is that it turns an appointment into actual capability and transfers the tacit craft that documents cannot — reducing the early-failure-and-burnout gap where an under-supported new holder flails in a role they nominally hold.

Its failure modes come from the same apprenticeship logic. Shadowing propagates the mentor's bad habits alongside the good, so a role's dysfunctions reproduce themselves through onboarding; and a runbook can decay into box-ticking that certifies "onboarded" by time served without real competence behind it. The classic misuse is to run it so thin that it is onboarding in name only, or to invoke it to justify a hire already made. The discipline that keeps it honest is to tie completion to demonstrated competence rather than elapsed weeks, and to periodically refresh what "good" looks like so shadowing renews practice instead of ossifying it.

How it implements the components

This process fills the competence-building slice of the archetype — bringing a holder up to the bar and equipping them to work:

  • resource_and_support_provision — arranges the mentor, materials, access, and protected ramp time a new holder needs to become effective.
  • eligibility_and_competence_conditions — builds the holder up to the role's competence bar and verifies the milestones are met. (The bar itself is defined by the Position Description or Office Mandate and screened at appointment by the Role Compatibility Check; this process closes the gap to it.)

It builds competence but does not define the bar (that is the Position Description or Office Mandate), screen eligibility at appointment (that is the Role Compatibility Check), or transfer a specific departing holder's live state (that is the Handoff Checklist).

Notes

This runbook shares the competence component with the Role Compatibility Check, but from the opposite side: the check screens whether a candidate already clears the bar at appointment, while the runbook builds a holder up to it afterward. The two are sequential, not redundant — a candidate can pass the screen on paper and still need the ramp to become effective — and the runbook typically follows a Handoff Checklist, taking the live state the checklist transfers and turning its recipient into a competent holder.

References

[1] Legitimate peripheral participation — Lave and Wenger's account of how newcomers learn a practice by taking part in real, low-stakes portions of it alongside experienced members, moving from the periphery toward full participation. Role shadowing is a direct instance, which is why the ramp is structured around supervised doing rather than instruction alone. ↩