Friction Is a Signal, Not a Complaint
The complaint is data
When a team says a process is "a nightmare," the instinct is to treat it as morale. It is better treated as measurement. Friction is the most reliable, lowest-cost signal a business has about where its operating model does not match how work actually flows.
The task is translation: turning a complaint into a locatable fault.
Four frictions and what they mean
Duplicate entry. The same information is typed into more than one place. This almost always means two systems own the same record and neither is authoritative.
Chasing. Someone must ask for status. This means the process has no visible state — work exists, but its position is not observable.
Rework. Output is corrected after the fact. This means requirements are confirmed downstream of where the work is performed.
Waiting. Items sit idle between steps. This means the process depends on a person noticing, rather than being routed.
Friction is rarely about effort. It is about information arriving in the wrong place, at the wrong time, to the wrong person.
Separating frequency from severity
A painful problem that happens twice a year is a story. A mild problem that happens forty times a week is a cost. Score both:
- How often does the friction occur?
- How many people does it pull in each time?
- How long does each occurrence take to resolve?
Multiply, annualise, and the ranking usually rearranges itself. The loudest friction is seldom the most expensive one.
From signal to priority
Once friction is located and sized, the improvement path is narrow and obvious: eliminate the step, standardise the input, move the decision earlier, or make the state visible. In that order.
Start by scoring one process with the Process Priority Toolkit.