Define the system boundary
Name the function, intended result, people served, starting point, endpoint, and required safeguards.
CHAPTER 8 - PROTOCOL 1
System Mapping
TIME75-90 minutes
OWNERPrincipal with representative system users
ARTIFACTCurrent-state system map + one leverage question
- The map names purpose, people, decisions, information, routines, handoffs, and feedback.
- Formal steps and informal workarounds are both visible.
- Gaps, duplication, delay, dependency, and inequitable experience are identified.
- The team selects one evidence-based leverage question for the next protocol.
Trace the lived pathway
Map actions, decisions, handoffs, information, tools, wait time, feedback, and workarounds from a real example.
Mark friction and strength
Identify where the system accelerates, protects, delays, duplicates, obscures, or depends on one person.
Choose the inquiry
Select one high-leverage system question and define the evidence needed before redesign.
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
- Which handoff is largely invisible to leadership?
- Where does the written process differ from lived experience?
- Who compensates when the system fails?
EQUITY GUARDRAILS
- Include people closest to the work and those most affected by it.
- Do not expose confidential student, family, or personnel information on the map.
- Avoid blaming individuals for predictable failures created by system design.