Define the enduring purpose
Name the pressure point, people served, desired experience and outcome, and long-term capability to build.
CHAPTER 8 - PROTOCOL 7
Infinite Game System Builder
TIME90 minutes plus 30-day cycle
OWNERPrincipal with cross-role design team
ARTIFACTSystem design canvas + thirty-day learning test
- The design begins with purpose and user experience rather than a preferred solution.
- Roles, decisions, knowledge, routines, feedback, safeguards, and adaptation are coherent.
- The system reduces dependency and develops capability.
- A bounded test produces evidence before full-scale adoption.
Make five design decisions
Clarify ownership, decision rights, essential routine, evidence and feedback, and how learning will change the design.
Run the Integrity Pause
Test coherence, burden, equity, safeguards, dependencies, likely drift, and fidelity without rigidity.
Launch the smallest coherent test
Pilot one complete cycle, gather evidence, and decide whether to adapt, scale, pause, or stop.
WORKING ORGANIZER
Run the protocol.
Your responses save on this device. Use Print / Save PDF when you are ready to keep or share the artifact.
Your protocol can be complete here. Save or share the artifact and use it for the need in front of you.
REFLECTION PROMPTS
- Are we designing a system or packaging an activity?
- What capability will be stronger after one full cycle?
- How will the design adapt without losing integrity?
EQUITY GUARDRAILS
- Do not scale before testing lived experience and differential impact.
- Remove obsolete work when introducing a new system.
- Preserve legal, safety, privacy, accessibility, contractual, and due-process protections.