Issue 019
The Physics of Organisational Friction
VISPAICO Journal, Issue 019
Take a mechanical system with fifty points of contact, bearings, joints, gears, anywhere one moving part touches another, and assume each one loses a modest two percent of the energy passing through it to friction. Intuition suggests the total loss should be manageable, something in the region of the sum of the parts. The actual mathematics is considerably less forgiving. Multiply those small losses together across all fifty points, and the system delivers not ninety-eight percent of its original power, nor even eighty percent, but closer to thirty-six. Nearly two-thirds of the energy that entered the system has vanished, not through any single dramatic failure, but through fifty individually negligible points of resistance, each one too small to notice, compounding into a loss too large to ignore.
This is not a hypothetical curiosity. It is the exact problem that occupied some of the most serious engineering minds of the industrial era, and the solution to it, unglamorous, almost invisible, entirely unconcerned with making anything more powerful, turned out to be one of the more consequential inventions of the early twentieth century. In 1907, a Swedish engineer named Sven Wingquist patented a self-aligning ball bearing, designed to solve a problem that had quietly plagued industrial machinery for decades: shafts that were never perfectly straight, bearings that wore unevenly, friction that accumulated at every rotation until a meaningful share of a machine's power was being spent simply overcoming its own resistance rather than doing anything useful at all. Wingquist's bearing did not make engines stronger. It made the friction disappear, and in doing so, it delivered something closer to a free improvement in capability than industry had seen from any single invention in years.
There is a lesson buried in this story that applies with unusual precision to how companies think about productivity today, and it is worth extracting carefully, because most organisations are still solving the wrong half of the equation.
Why Engineers Learned to Distrust Raw Power
For a long stretch of the industrial era, the instinctive response to a machine that wasn't performing well enough was to make it more powerful, a bigger engine, more horsepower, brute force applied to whatever the problem happened to be. This instinct made intuitive sense and was, for a surprisingly long time, the default engineering response to almost any performance shortfall.
What experienced engineers eventually learned, often the hard way, was that adding power to a system full of unaddressed friction is a remarkably inefficient way to improve it. A more powerful engine bolted onto a poorly lubricated, badly aligned transmission simply burns more fuel overcoming the same resistance that was always there, delivering a smaller improvement in actual output than the size of the new engine would suggest. The genuinely transformative gains, again and again across the history of mechanical engineering, came not from adding force but from removing resistance, better bearings, better lubrication, more precise alignment between moving parts. A machine relieved of its friction could do considerably more work with considerably less power than the same machine simply given a stronger engine and left to fight its own resistance as before.
This is a specific and counterintuitive insight, and it is worth stating plainly because it inverts the instinct most organisations still bring to their own productivity problems. The question was never really "how do we add more force." It was "where, precisely, is this system quietly losing energy to resistance nobody has bothered to measure."
The Invisible Friction Inside Every Company
Companies contain a version of exactly this problem, distributed across thousands of small daily interactions rather than concentrated in a handful of mechanical joints, and it behaves with the same compounding mathematics that makes Wingquist's bearing story so instructive. Consider what an ordinary employee actually experiences across an ordinary week. Searching for a document that exists somewhere but not where they first looked. Waiting for an answer from a colleague who is in another meeting. Clarifying an instruction that was slightly ambiguous the first time it was given. Repeating an explanation to a new team member that has already been given, in nearly identical form, to several previous new team members. Answering, for perhaps the hundredth time, a question that has a perfectly good answer sitting somewhere in the organisation's own accumulated knowledge, if only the answer could be located as quickly as the question was asked.
Each of these, in isolation, looks exactly like Wingquist's two percent, trivial, barely worth measuring, certainly not worth a serious engineering intervention. Ten minutes lost here. A slightly delayed response there. A repeated explanation that takes five minutes rather than zero. No single instance of this friction would ever appear on a performance review, or trigger a process improvement initiative, because no single instance is large enough to notice.
But organisations, like mechanical systems, are not built from a single point of contact. They are built from thousands of them, repeated daily, across every employee, every project, every handoff between one part of the business and another. The same multiplicative mathematics that turns fifty small mechanical losses into a system running at little more than a third of its potential applies with equal force to an organisation running on thousands of small human ones. The aggregate loss is not the sum of the individual frictions. It compounds, quietly, the same way Wingquist's fifty two-percent losses compounded into something considerably larger than intuition expected.
Why This Loss Stays Invisible
It is worth dwelling on why this particular category of loss so consistently escapes serious executive attention, because the reason is structural rather than a failure of anyone's diligence. Mechanical friction, at least, eventually announces itself, a bearing overheats, a machine underperforms its rated capacity, an engineer with a stopwatch can measure the gap between expected and actual output. Organisational friction rarely announces itself with anything approaching this clarity. It is distributed across so many people, so many small moments, so many interactions too minor to log, that no single measurement ever captures it. A company can run an efficiency review of its major processes and find everything technically functioning as designed, entirely missing the accumulated cost of ten thousand small moments of searching, waiting, and repeating that no process review was ever built to detect.
This is precisely why the instinctive response to a productivity shortfall has so often been to add more force rather than to look for the resistance. Hire more people. Extend working hours. Ask existing staff to simply move faster. Each of these is the organisational equivalent of bolting a bigger engine onto a poorly lubricated machine, a real intervention, producing some real improvement, while leaving the underlying friction almost entirely untouched, quietly consuming a share of the added capacity exactly as it consumed a share of the original capacity before the intervention arrived.
Reducing Resistance, Not Adding Labour
This is the precise distinction worth drawing out, because it reframes what a genuinely useful intervention in organisational productivity should actually be trying to accomplish. The goal was never to add more raw capacity to a system still losing a meaningful share of its output to unaddressed resistance. The goal is to find the equivalent of Wingquist's bearing, the unglamorous, almost invisible fix that doesn't make anyone work harder or faster, but simply removes the friction that was quietly consuming a portion of everyone's effort before it ever produced anything useful.
A system that can locate the right document instantly, rather than after several minutes of searching across scattered folders, has not asked any employee to work harder. It has simply removed one small point of resistance, repeated many times a day, across every employee who would otherwise have lost those minutes to searching. A system that can answer a routine question immediately, correctly, without requiring a colleague to pause what they were doing to provide it, has not added labour to the organisation. It has removed a small, recurring point of friction that was quietly taxing both the person asking and the person being asked, dozens of times a day, across the whole organisation, compounding exactly the way Wingquist's fifty small mechanical losses compounded into something the naive arithmetic never predicted.
This is the correct lens for understanding what a genuinely useful intelligence layer actually contributes to a business, and it is a considerably more precise lens than the language of labour substitution that so often gets applied to this conversation instead. The value was never primarily about doing work that a person used to do. It is about removing the accumulated resistance that was quietly consuming a portion of everyone's work, every day, in increments too small for any single person to notice, but large enough in aggregate to determine whether the whole system runs anywhere close to its actual potential.
What Gets Unlocked Once the Friction Disappears
It is worth returning, finally, to what actually happened once bearings like Wingquist's became standard across industrial machinery. Engines did not need to grow nearly as large to deliver the same output, because so much less of their power was being wasted overcoming the system's own resistance. Machines that had previously seemed to be operating near their practical limit turned out to have considerably more capacity available all along, capacity that had been there the entire time, simply consumed by friction nobody had thought to measure carefully enough.
Organisations that take their own equivalent of this problem seriously should expect something structurally similar. Not a workforce suddenly working harder, or a sudden influx of additional capacity from anywhere external to the business. Simply the quiet discovery that a meaningful share of the organisation's actual potential was present the entire time, sitting unused behind thousands of small, individually forgettable points of resistance that nobody had ever bothered to add up. The businesses that understand this will not describe what they've done as working faster. They will describe it, more accurately, the way an engineer might describe the effect of a well-designed bearing: not more force, applied to the same resistant system, but the same force, finally moving freely through one that no longer fights it at every turn.
Other Issues
Continue reading from the journal.
Sovereign Intelligence: Why Ownership Will Define the Next Decade of Business
The greatest infrastructure advantages rarely looked like infrastructure at the time, they looked like plumbing. This feature essay argues that AI is becoming the cable every company depends on, and the question is no longer whether you use it, but who owns it.
Issue 018Everyone Gets a Cabinet
For most of history, a ruler was expected to personally understand everything the state did. The cabinet changed that. Now something structurally similar is becoming available to every employee inside a company, not merely to the executives at the top of it.
Issue 017The Intelligence Economy
Every economic revolution solved one scarcity only to reveal another. The agricultural revolution solved the scarcity of calories, only to reveal the scarcity of allocation. The industrial revolution solved the scarcity of production, only to reveal the scarcity of distribution. Information abundance created a poverty of attention. Now, for the first time, the capacity to turn information into sound judgment, intelligence itself, is becoming the scarce resource that determines who thrives.
Issue 016The Architects of Intelligent Enterprise
A city is not a machine to be optimised for throughput. This essay argues that intelligent enterprises are not built by installing isolated AI tools, but by redesigning the relationships, workflows, and decisions that make the whole organisation function.
Issue 015The Hierarchy of Thinking
In the 1790s, Gaspard de Prony organised thinking into a hierarchy for the first time. For two centuries, every tier required a person. AI now occupies one of those rungs, and the question facing every organisation is not how to adopt a new tool, but how to redesign the hierarchy itself.
Issue 014The Knowledge Dividend
When Benjamin Franklin left money to grow untouched for two centuries, it became millions. The same math applies to organisational knowledge. On the difference between spending a return the moment it arrives, and leaving it to compound into something considerably larger.
Issue 013The Best Technologies Disappear
Nobody in a modern office building has ever paused to admire the water pressure. The technologies that changed civilization most completely are the ones we stopped talking about. This essay argues that AI is heading for the same fate, and that is the highest compliment it can receive.
Issue 012Every Company Will Eventually Have Two Brains
A company has always had one kind of memory: the fragile, individual, endlessly leaking kind. This issue argues that the next great organisational shift is building the second brain that lets experience consolidate across the whole business.
Issue 011The Company That Never Forgets
When NASA went to rebuild the F-1 engine decades later, it had the original drawings. What it had lost was the judgment behind them. The same pattern plays out in every growing company, invisibly, expensively, and almost never noticed until the cost has already been paid.
Issue 010The Rise of the Intelligent Enterprise
A clock knows nothing. A body adapts and remembers. The distinction between a mechanism that repeats and an organism that learns is the one most executives have not yet drawn about their own companies.
Issue 009AI Is Becoming Electricity for Knowledge Work
For thirty years after electrification began, factory productivity barely moved. The gains came only when companies redesigned the factory itself. Executives adopting AI as a faster tool today are repeating the same mistake, and missing the same far larger reward.
Issue 008From Search to Conversation: The Next Interface of Business
The grand hotels of the nineteenth century solved a problem that had nothing to do with rooms. They hired a concierge so a guest never had to search. Corporate computing has spent a century asking employees to behave like a guest without one.
Issue 007Every Business Will Have an Operating System. Most Just Don't Know It Yet.
In 1956 the shipping container turned a fragmented industry into one interoperable system. Businesses are running their software the way global shipping ran before the container, a stack of excellent, isolated tools, none able to hand information to the next without a human repacking it by hand.
Issue 006Your Competitive Advantage Is Already Sitting in Your File Server
The economist Hernando de Soto showed that the world's poor were rich in assets they could not use, dead capital, unconnected to any system of record. Most companies are sitting on the exact same problem, hidden in an archive of proposals, contracts, and notes that almost nobody can find when it matters.
Issue 005The Future CEO Will Manage Humans and AI Employees
In 1841 two trains collided and the org chart was invented. Executives now face a comparable inflection point: what does an organisation look like once part of its workforce is not human, and what kind of leadership does that require?
Issue 004Why Data Lakes Failed but Company Brains Won't
Companies spent a decade building data lakes that centralised everything and clarified nothing. The Rosetta Stone sat unread for twenty-three years, the lesson is that storage was never the problem, relationship was. This essay explains why Company Brains win where data lakes didn't.
Issue 003The Varnish Nobody Could Replicate
For two centuries, chemists have tried to reproduce Stradivari's varnish, and failed. The secret was never the formula; it was a lifetime of judgment that died with him. The same pattern plays out inside companies every time a long-tenured employee walks out the door.
Issue 002Every Company Is Now a Software Company (Even Without Engineers)
For fifty years, software meant a product built by engineers and sold to businesses. That definition is quietly becoming obsolete. What happens when a company can turn its own accumulated judgment into something operational, without hiring a single developer?
Issue 001The Invisible Cost of Organisational Forgetfulness
Every company keeps a balance sheet. Nobody tracks what the organisation actually knows, or what it loses when someone walks out the door. This essay examines why institutional memory is the most undervalued asset in business, and why the companies that preserve it will quietly stop making the same mistake twice.