The Catalytic Path
From the real system to a change the institution can own and prove.
Research the Real System
Watch how work really moves, not how it is described. Follow one journey across people, documents and systems. Compare the stated rule with actual practice, retaining the source, time and conditions of each observation. The output is a current-state picture and a baseline that the institution can revisit.
Map the Friction
Find where decisions wait, bounce or get lost. Distinguish a missing instruction from unclear authority, an overloaded handoff or a conflicting incentive. State who experiences the friction, who can change it and which evidence would challenge the explanation. The output is a prioritized friction map, not a list of complaints.
Architect the Path
Set who decides what and how work moves. Define the next step, decision rights, escalation conditions, handoff information and acceptance criteria. A path may require a rule, role, protocol, interface or integration. Choose the smallest structure that addresses the observed friction.
Activate in the Field
Test the path under real pressure. Use an agreed pilot, include exceptions and different shifts, and record where people need help. A workshop can prepare the team; it cannot substitute for use in a real week. The output is a tested path with failures and revisions visible.
Embed Ownership
Hand the path to the people who run it. Assign an operating owner, a review routine, access permissions and a way to update the playbook. Ask whether the institution can use and maintain the path without Roadyom. Ownership is demonstrated in practice, not by a handover presentation.
Prove the Movement
Show what changed and what cannot be claimed. Re-observe against the baseline under comparable conditions. Keep alternative explanations, contradictory observations and missing coverage visible. Separate completion, delivery, acceptance, observed outcome and attributed impact. Agree the next observation with the institution.