Social Mechanical Optimization

Two Theories of What a Business Is

Ask a Japanese manager what makes a company run and they'll say: relationships. Ask an American manager and they'll say: the process. These aren't just cultural differences. They're genuinely different theories about what a business actually is — and they produce genuinely different companies.

The Japanese model treats the company as a shared field of experience first. Researchers Nonaka and Takeuchi, in their landmark work on how Toyota and Sony create knowledge, showed that competitive advantage isn't in the machinery or the org chart — it's in the quality of the relationships through which knowledge flows. When that relational fabric is healthy, the firm learns fast. When it's damaged, learning stops, regardless of how sophisticated the equipment is.

The Western model sees things differently. From Frederick Taylor's stopwatch to Eli Goldratt's The Goal, the company is a directed graph of operations. Every system has a constraint — a slowest node — and the whole firm should focus on widening it. People show up in this picture mostly as operators of steps. Relationships are overhead, not production.

Both are right about something. The Japanese model breaks down when it tries to scale across cultures: the knowledge stays locked inside a relational context that doesn't export. The Western model breaks down when it ignores the human system that actually enacts the steps — a perfectly engineered process in a socially unprepared firm produces the same result as a bottleneck.

The framework I call Social Mechanical Optimization (SMO) takes that joint problem seriously — and treats it not as a cultural sensitivity exercise, but as an engineering problem with a specific equilibrium and a specific intervention that raises it.

A Problem That's Been Around Since 1951

The idea that you have to design social systems and technical systems together isn't new. In 1951, Eric Trist and Ken Bamforth studied what happened when British coal mines mechanized. The machinery was a clear upgrade. But mechanization destroyed the small, tight-knit work groups that had made the old method effective. The new technical system was better. The new social system was worse. Net result: lower output, more conflict, more worker resistance.

Trist called this the joint optimization problem: you can't maximize the whole by maximizing each part in isolation. The optimal state for the system often requires each subsystem to operate at slightly less than its individual peak.

That was seventy-five years ago. Two more bodies of research have since added important texture.

The first is absorptive capacity — from Cohen and Levinthal's 1990 research on how firms learn. Their finding: a company's ability to absorb new knowledge depends on the knowledge it already has. Absorptive capacity is cumulative. Firms that don't invest in it get locked out of future learning cycles.

The second is psychological safety — Amy Edmondson's finding that the single strongest predictor of whether a team actually learns from information is whether its members feel safe enough to speak up. Without that safety, even well-designed teams don't convert what they know into what they do.

Put these three ideas together — Trist's joint optimization, Cohen and Levinthal's absorptive capacity, Edmondson's psychological safety — and a clear picture emerges. What actually governs throughput in a modern firm isn't the machines. It's the rate at which the human system can absorb and enact change.

When the Technical System Arrives Without the Social One

The clearest contemporary example of the SMO problem is one that has played out across several cross-border semiconductor expansions: a world-class technical system, built and refined over decades in one culture, gets transplanted into a different one — without the social system that made it work.

The technical side of these operations is genuinely extraordinary. Equipment refined over forty years. Processes specified to tolerances most industries never approach. The specifications transfer perfectly. What doesn't transfer is the relational fabric that makes the specifications live.

In the originating culture, engineers are on call around the clock. Hierarchy is steep. Meeting loads are heavy. Obedience to process is the norm. This isn't arbitrary — it's a tightly integrated social system that makes the technical one work. Knowledge moves fast because the relational network was designed to carry it.

In the receiving culture, that same technical system lands differently. Engineers push back on hierarchy they read as counterproductive. Veterans read that pushback as lack of dedication. Meeting expectations become flashpoints. The company adjusts — fewer meetings, communications training, public acknowledgment that what worked at home can't simply be airlifted abroad.

The standard framing — "culture clash," "HR issue," "labor relations" — treats the social friction as separate from the facility's real job. That's exactly wrong.

The friction shows up as delayed production ramp, higher turnover, longer time-to-yield, and slower diffusion of the tacit process knowledge that makes these operations work. The technical system was specified at world-class. The social system was specified by default. The result is exactly what Trist predicted in 1951: neither the equipment nor the people perform at what each is individually capable of.

Four Ways a Company Can Be Wrong

To see why this requires joint optimization — not a fix to either side alone — think of a company as having two dials: the mechanical dial (how much energy and change is the technical system demanding?) and the social dial (how much capacity does the human system have to absorb it?).

Low mechanical, low social (2,2): The stagnant bureaucracy. Nothing is pushing and nothing is absorbing. Stable, but no growth. This is the default state of a large, mature organization that stopped trying.

High mechanical, low social (1,4): The cross-border transplant cell. The technical system demands high velocity. The human system can't absorb it. The result: burnout, turnover, quality incidents, friction. This is also where most AI deployments are currently headed.

Low mechanical, high social (4,1): The opposite failure — a company with excellent culture and psychological safety, but a timid technical roadmap. The relational capacity is there but never called on. This is the modal failure mode of companies that have genuinely invested in culture but haven't connected it to operational ambition.

High mechanical, high social (5,5): The SMO equilibrium. High energy matched by a social system built to receive it. Maximum throughput.

Here's the critical point: the (5,5) cell is only reachable through coordinated movement. If the technical system raises energy unilaterally, the firm slides into burnout. If the social system builds capacity unilaterally, it builds slack no one uses. You get to (5,5) together, or not at all — which means you need a protocol that governs the rate of change and simultaneously expands the capacity to absorb it.

The Turbocharger

The engineering analogy that keeps coming back: the turbocharger.

A naturally aspirated engine draws air in on its own intake stroke. A turbocharger uses exhaust pressure to force more air in — raising peak power without changing the engine's size. But you can't bolt a turbocharger onto a block that wasn't designed for the pressure. You'll crack the block.

AI agents are the turbocharger. In the last three years, the rate at which mechanical energy can enter a firm has increased by an order of magnitude. Tasks that took a quarter can be drafted in a day. Analyses that took a team can be run by one operator. The number of parallel workstreams a single person can manage has exploded.

The relational infrastructure — the review cadences, the approval chains, the trust relationships, the psychological safety to flag a bad agent output without career risk — has not been redesigned for that higher pressure. Most firms are running a turbocharger on a block that's about to crack.

SMO's answer: introduce agentic energy at the rate the social system can actually absorb it, while actively building that absorption capacity. A protocol that only slows change becomes a brake. A protocol that only builds capacity without governing rate produces burnout. Both levers, moved together.

What the Framework Produces

SMO isn't just a conceptual frame. The research program behind it produces three concrete things.

A formal model — a two-system control problem with state variables for absorptive capacity, agentic energy, and throughput. The matrix above is the intuition; the model makes the equilibria computable and lets you measure how far a given firm is from the optimum.

Empirical simulation results. AI agents are now available as instrumented research subjects — populations of agents with configurable parameters, measurable throughput outcomes. The simulations test different protocol regimes: no protocol (the cross-border baseline), harmony-first, process-first, and full SMO. The goal isn't to prove SMO always wins; it's to map the conditions under which each regime does.

An operating document — what an SMO-compliant firm actually does on Monday morning. Meeting cadences. Review rituals. Escalation paths. Agent-deployment gates. Written for a corporate planner at any facility where the joint-optimization problem is live and not theoretical.

Where This Leads

The firms that define the next two decades won't be the ones with the best machines or the best culture. They'll be the ones that figured out how to move both dials together.

Cross-border fabs. AI-augmented operations. Teams spanning high-trust and high-velocity contexts. These aren't edge cases anymore — they're the baseline condition of any serious global company. The question isn't whether to design for it. It's whether you do it intentionally or land in one of the failure cells by default.

Social Mechanical Optimization is the framework that names this problem, makes it formal, and offers enough of a solution to be useful on Monday morning.