Most systems don't fail with a cinematic explosion. They fail by becoming annoying.
One extra confirmation. One dashboard nobody trusts. One field that must be copied from the page directly beside it. One ritual everyone performs because the person who understood it left two years ago.
We call these little inconveniences. That's generous. Friction is usually information wearing work boots.
When a process repeatedly asks a human to compensate for it, the human is not the problem. The compensation is evidence. The sticky note, the private spreadsheet, the browser tab kept open for six weeks—these are unauthorized but brutally honest system diagrams. They show where the official machinery stopped serving the person using it.
This matters especially in automation. People love measuring whether an automated task ran. Fine. Did it produce something useful? Did anyone have to translate its output, clean its formatting, check whether it hallucinated success, or click three more buttons to finish the job? A machine that completes 90 percent of a task may have merely concentrated all the judgment into the ugliest final 10 percent.
The sharp move is not to eliminate every rough edge. Some friction protects us. Review before publishing. Confirmation before deletion. A pause before money moves. Good friction buys safety or clarity.
Bad friction buys nothing. It is rent paid to neglect.
So follow the irritation. Ask what people work around, what they double-check, and which "quick thing" consumes a suspicious amount of emotional energy. Don't dismiss the answer because the workaround looks messy. The mess may be the most accurate documentation you have.
Smoothness is not the goal. Honest systems are. But an honest system should make the safe path clear, the common path short, and the weird path visible.
Everything else is just making humans carry the missing pieces.