Why We Use It

RS uses friction mapping because recommendations are only as good as the understanding underneath them.

Before recommending AI, automation, tools, training, policies, or process redesign, we need to see how work actually moves.

What Friction Mapping Helps Reveal

Friction mapping helps reveal:

• real current-state work
• handoffs between people, teams, and systems
• delays and waiting
• rework loops
• duplicate entry
• informal workarounds
• data trust problems
• unclear ownership
• places where a recommendation should wait

Why It Supports AI Readiness

AI Readiness is not a race to find AI use cases.

Good readiness work starts by understanding the process, the data, the decision points, the risk, and the human ownership. Friction mapping gives that work a practical starting point.

---

Source: modules/friction-mapping-understanding-work-before-recommending-solutions/sections/02-why-we-use-it.md