21. Campus Adopt — The Quad (light, university brick)

Audience: programme & implementation managers in public organizations · Artifacts: quad.html (2D) · 3d.html + quad.js (3D quad) · shared data quad-data.js · Case study: index.html

In one line: a governance-move board: four factions, four quarters, six moves. Read who is willing, build ownership before locking it in, and hand the practice to whoever holds it.

Why this kit exists

Successful pilots die in the gap between 'worked' and 'is how we work now'. Implementation turns on two things that are hard to see: how willing each faction is, and how much of the practice it actually holds. The two failure modes (day-one mandates, endless showcasing) are both rational and both fatal. The board makes both visible.

What the artifact does

Four factions whose willingness is hidden until you showcase or work with them, each with a readable cue; six moves (SHOWCASE, CO-OWN, MANDATE, FUND, FORMALIZE, HANDOVER); four quarters, one move each. Mandating after co-owning lands on prepared ground, mandating first collapses willingness; formalizing only locks in ownership that exists; a handover lands only on a faction that already holds the practice. The debrief scores durable ownership per faction, checks three habits, and shows the taught four-step sequence, which fits the four quarters.

The design decisions worth noticing

• Two quantities, one vocabulary — willingness (readiness, hidden until learned) and ownership (what the faction holds); showcasing raises the first, co-owning and policy build the second
• The mandate conditional — MANDATE isn't wrong, it's sequencing-dependent: mild resistance after co-owning, collapsed willingness without
• HANDOVER unlocks at Q4 — the button label teaches the rule before the rule is explained: you cannot hand over what nobody holds

Honest limitations

Noorderlicht University and its factions are fictional composites of Dutch higher-education governance patterns. Real implementations have more than four stakeholders and more than four quarters; the board trains the ownership-vs-visibility instinct, not a playbook.

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