Start with the handoff you need
A process can work perfectly while the team around it remains uncertain. Someone can follow the demonstration yet struggle to explain a status, interpret an unexpected result or find help when the builder is away. That uncertainty belongs in the project plan.
In The Build Is Not Done, David brings five conference sessions together around knowledge transfer. The sessions contribute perspectives on scalable training, interactive practice, durable adoption, legacy decisions and decentralized administration. The teaching framework here is David’s cross-session synthesis, developed into an operating brief and teach-back rubric.
Choose one process that matters to daily work. Name the person who will use it, the person who maintains it and the person who decides whether it still serves its purpose. Then ask what each must understand for the handoff to hold.
In the recording · 03:05 ↗Set the learning target by role
The same material can support several learning paths without making their expectations identical. An everyday user needs a dependable normal-case routine and an escalation path. A maintainer needs dependencies, approved change boundaries and a way to check results. A process owner needs enough context to evaluate whether the work still fits.
The companion chapter offers four useful questions: what must this person do, what must they understand, what should they avoid changing and when should they ask for help? Answer those before choosing slides or recording a walkthrough.
David’s five levels make the target explicit: orientation, operation, troubleshooting, maintenance and stewardship. Use them to identify missing coverage around a process. They describe learning expectations; access permissions and change approval remain separate decisions.
In the recording · 05:01 ↗Make practice reveal the reasoning
A useful exercise asks for a decision and its explanation. Give a learner a fictional status history, a short process description and a surprising result. Ask which detail matters, what they expect to happen next and when they would involve the owner.
Choose evidence that fits the role. An operator might explain the next step and the exception route. A maintainer might describe the dependencies an approved change would affect. Neither needs to recite every configuration detail to show useful understanding.
At teach-back, listen for purpose, data sources, major logic, risk and the support path. The workbook also asks for task evidence, documentation and the ability to teach another user. Record the particular gap when an explanation stalls. A missing definition calls for a better definition and another example, rather than replaying the entire training.
In the recording · 07:27 ↗Preserve why the process exists
Inherited objects often retain a name long after their original reason becomes difficult to recover. A workaround may still protect an important exception. A report may reflect an older definition. Teaching only the clicks leaves the next person unable to judge those differences.
Capture the purpose, known decision history, current owner, important dependencies and consequences of a change. Mark an unknown reason as unknown and identify who can investigate it. Guessing at the original intent creates a new source of confusion.
Keep the teaching brief compact enough to use during work. Pair normal steps with expected results, common exceptions and escalation instructions. A checklist supports action; a reference note explains the logic; a short demonstration shows the interface. Give each format a clear job.
In the recording · 11:40 ↗Make local responsibility supportable
Decentralized teams need to understand both local choices and shared standards. A department user should be able to locate the relevant guidance, recognize a situation outside their responsibility and raise it through a dependable support channel.
The central team has learning work too: listen to recurring questions, explain why a shared rule exists and keep the support route visible. Repeated confusion can reveal a missing example or an unclear boundary. Feed that evidence into the next version of the brief so each new user benefits from what the previous user discovered.
In the recording · 13:49 ↗Keep the brief connected to change
Assign the teaching artifact an owner, a review date and update triggers. A renamed status, revised population rule, new process owner or changed report can invalidate an otherwise polished explanation. Learner confusion is another reason to review it sooner.
When the process changes, identify which examples, screenshots, expected results and practice cases need revision. Recheck those pieces with the intended learner. The maintenance task includes the explanation people depend on, as well as the configured object.
Start with one knowledge gap this week. Ask someone other than the builder to explain a process, create the smallest useful teaching artifact and try it with that person. Keep the evidence of what they can now explain. That gives the next training decision a concrete starting point.
In the recording · 22:41 ↗