25. The Handover — The Handover (dark, async indigo)

Audience: anyone handing over a process across teams or timezones · Artifacts: handover.html (2D) · 3d.html + handover.js (3D night corridor) · shared data handover-data.js · Case study: index.html

In one line: a handover-doc builder stress-tested by a Friday-night simulation: ten process elements, a clarity budget, and a colleague who cannot ask you anything.

Why this kit exists

Handover documents fail in two symmetrical ways: the comprehensive wall-of-text (everything rich, nothing prioritized) and the bullet-and-a-prayer ('ask me if unclear'). Both come from the same root — the writer optimizes for writing effort, not for the reader's 22:00 with no one to ask. The budget forces the prioritization; the simulation shows the cost of skipping it.

What the artifact does

Ten process elements, each assigned one of six structure cards (one-liner 1, IF-THEN 2, worked example 3, failure gallery 1, contact path 1, none 0) inside a 15-point budget that exactly fits the best answer. The Friday-night replay runs with real IST/CET clock arithmetic; every gap becomes a guess the learner can rebuild and replay. Pass = 16/20 inside the budget with deadline, exceptions and verification answered. The 3D version is the night corridor of a Bengaluru office at 22:04 IST in the monsoon: each element is a glass-fronted meeting room, and the card decides what is in it (a plaque, a whiteboard flowchart, a worked-example screen, framed failure photos, a desk phone with a contact card, or nothing). Priya stays off-screen: motion-sensor lights follow her, rooms that answer light warmly, and where she has to guess her phone torch sweeps a dark room and a ? stays on the door. Frames from the build are in storyboard.md.

The design decisions worth noticing

• Structure must match failure mode — a glossary dressed as a failure-gallery fails the simulation: conditionals want IF-THEN, procedures want worked examples, people want paths
• The simulated reader — Priya's timestamped execution makes 'the reader' concrete; every guess is attributed to a specific gap
• The budget as prioritization — 15 points across 10 elements means the wall-of-text is impossible; triage is the assignment

Honest limitations

Vanleeuw & Partners and the enrolment process are fictional composites. Real handovers also need a live walk-through; the drill covers the document layer that survives when the walk-through is over.

Part of I Wayan Usada's learning-design portfolio · all clients and scenarios are fictional composites built from realistic domain patterns · drafted with AI assistance and fully rewritten, fact-checked and owned by a human.

Process deliverables

• action-map.md — Action map — the behaviors the artifact must produce, traced to the business goal
• storyboard.md — Text-based storyboard — the scene plan written before build
• visual-mockups.md — Visual mockups & style guide — mood, type, key screens, component decisions