gtmjosh
Improve the System
Chapters · 8 of 9
  1. 01 · Establish a Review Rhythm
  2. 02 · Inspect Errors, Exceptions, and Overrides
  3. 03 · Compare Expected and Actual Outcomes
  4. 04 · Measure Adoption, Cost, Speed, and Quality
  5. 05 · Find Drift and Stale Definitions
  6. 06 · Test Changes Before Broad Release
  7. 07 · Roll Out and Roll Back Deliberately
  8. 08 · Update Owners, Documentation, and Training
  9. 09 · Capstone: Run the Quarterly Operating Review
Guide overview →

About 14 min · Lesson and activity

Chapter 8 of 90 complete

Update Owners, Documentation, and Training

The change reaches the people and documents that have to move with it.

4c · update owners docs training

A change has downstream owners

Start with the example, then try it yourself. The last case is optional practice.

See the situation

Start with the situation below. Next, we will work through an example together before you try the activity.

Elena’s reporting room. A bookshelf, pinned charts, a reading lamp, and reports laid out on a desk.
Elena, reporting lead, explain pose
Elena · Reporting lead

The case

When the drift report becomes the problem

Release work includes updating each affected owner, document, report, and training path.

Change made
Deliberate, correct, shipped
Documentation updated
No
What the drift check now reports
The deliberate change, as a defect
Possible consequence
Reviewers may lose confidence in the drift report
Why this matters
A stale document can make a deliberate change look like a defect

Your place saves as you go.

Chapter 8 of 90 complete