Friction is invisible until you map it. We asked an AI to analyze process descriptions from various businesses and identify where friction accumulates.
The patterns were consistent: handoffs between teams, format conversions, approval chains, and "waiting for" dependencies. These friction points had been normalized — people worked around them without questioning them.
Mapping friction isn't about blame. It's about visibility. Once you see where things slow down, you can decide whether the slowdown is intentional (a checkpoint) or accidental (a bottleneck).
AI sees friction because it doesn't have the context that makes friction feel normal.
O
OOretz Team
Building tools for AI-augmented thinking