What friction looks like in practice
Retyping a customer's details into a second system. Exporting one report to build another. Taking a photo, emailing it to yourself, then attaching it somewhere else. None of these steps produce value; they exist to move information between things that do not talk.
Friction is easiest to spot by watching where people invent workarounds.
Why teams quietly abandon tools
Most abandoned software was not rejected on principle. It was skipped once during a busy week, then skipped again, until the data inside it stopped being trustworthy.
Once a system is incomplete, using it becomes riskier than ignoring it, and the decline is hard to reverse.
A practical test before adopting anything
- Which existing step disappears entirely?
- Who has to enter data, and what do they get back for it?
- What happens on a bad day, in the field, on a phone?
- How many other tools does it need to stay in sync with?