Module Source
Facilitator Notes
Source note for Friction Mapping -- Understanding Work Before Recommending Solutions: Facilitator Notes.
Status: Working facilitator notes.
Facilitator Purpose
Help learners slow down before recommending solutions.
This module is not about creating perfect diagrams. It is about learning how to understand work, describe friction without blame, and know when a recommendation is premature.
Emphasis Points
- Do not recommend too soon.
- Current state comes before future state.
- Friction is usually a system signal.
- Workarounds are clues, not failures.
- Missing answers should become follow-up questions.
- The map is useful only if it helps explain the work.
Common Learner Moves
Learners may jump quickly to “they need AI,” “they need training,” or “they need a better system.”
Bring the conversation back to:
- What did we observe?
- What is the process boundary?
- What is the input, output, and transformation?
- What is known, and what is still a hypothesis?
- What should not be recommended yet?
Closing Point
Friction mapping is not about making a client’s work look broken. It is about making hidden work visible enough that better decisions become possible.
Provisional timing for facilitator planning
These inherited estimates are starting points for facilitation, not completion targets for learners. Refine them after observing setup, access needs, discussion, and actual participation.
- Module: * Time: about 60 minutes for the full module or 20–30 minutes for the in-page practice.
Source: modules/friction-mapping-understanding-work-before-recommending-solutions/facilitator-notes.md