campus-adopt · deliverable

Action Map — The Quad

Kit 21 · The Quad · deliverable · designed and built by I Wayan Usada — instructional design portfolio · fictional composite

The goal (proposed, not measured)

Programme plans name a receiving owner per practice before launch, and pilots are handed to a faction that already runs them.

What people do instead

Order adoption on day one, or keep showcasing until the funding stops; hand the practice to the sponsor rather than to whoever runs it.

The actions that close the gap

#	Behaviour	What it looks like	Where the artifact trains it
1	Read the factions before moving	the first co-owner is the faction whose cue shows the most willingness	cues + willingness fog
2	Build ownership before locking it in	CO-OWN comes before FORMALIZE or MANDATE	move order; formalize only locks in ownership ≥ 40
3	Hand over to whoever holds it	HANDOVER goes to a faction with ownership ≥ 60	Q4 handover; the banner lands or droops

What is not a training problem

If project funding always ends at 12 months with no receiving budget, even a good sequence ends in theatre; the funding model needs a handover line.
Faction willingness is partly earned by being asked: consulting central services on workload is a governance step, not a training topic.

Revision note

One vocabulary (willingness, ownership); the taught sequence now fits four quarters; the L2 target no longer counts a "mixed landing" as success. Nothing has been measured.

Prefer the source? Download the raw markdown.