Cumulative friction: the risk that never makes headlines

I recently spent twelve weeks diagnosing the identity and asset operations of a global financial services group. Over sixteen hundred observations from more than fifty people, distilled down to a handful of structural patterns. The headline finding surprised the leadership team, because it was not a headline at all: nothing was broken. The organisation was operationally strong, with committed teams and genuine delivery bias. And it was quietly carrying material risk anyway.

That combination is the most common condition I find in businesses of every size. It never announces itself, because the organisation optimises for speed at request time. Things get done. Exceptions are handled pragmatically. Experienced people bridge the gaps between systems with judgement, favours and manual coordination. Everyone is busy, everything works, and the risk register stays clean.

How friction compounds

The problem is that each of those pragmatic bridges has a cost, and the costs compound. The most useful analytical tool I know for surfacing them is brutally simple: write every observation as a behaviour and its consequence. Because access decisions rely on precedent, variability embeds at the point of allocation. Because knowledge is concentrated in experienced individuals, key-person risk persists. Because reporting is recreated on demand, every audit and every incident response starts slowly. None of these sentences describes a failure. Each one describes a small tax, paid on every transaction, forever.

At small scale the taxes are invisible. At growth they become material, because growth multiplies transactions faster than it multiplies experienced people. The business that ran beautifully at fifty people starts fraying at a hundred and fifty, and everyone blames workload when the real culprit is structure. The friction was always there. Growth just turned up the volume.

The tell-tale signs

You can diagnose cumulative friction without a sixteen-hundred-observation study. Ask three questions. First, how quickly can you answer a basic control question, such as who has access to what, or where your key assets are, without someone manually assembling the answer? Second, how much of your operation depends on specific named individuals being present and remembering things? Third, when something goes wrong, do your processes prevent it upstream or detect it downstream? Slow answers, name-shaped dependencies and downstream detection are the three signatures of a business paying the friction tax.

What to do about it

The good news is that cumulative friction responds to structural fixes, not heroic effort: clear end-to-end ownership, a single trusted version of the data, workflow instead of email, and preventative controls at the moments that matter. The sequencing matters more than the ambition; each fix should create the foundation the next one depends on. And the honest starting point is an evidence-based picture of today, in your own team's words, because people fix what they recognise and resist what they are accused of.