No One Wins Le Mans from the Org Chart

01

Ford had the parts, not yet the system

Ford had almost everything: capital, engineering capability, manufacturing scale, brand power, executive attention and a clear ambition — defeat Ferrari at Le Mans.

What it did not automatically have was a coherent system capable of turning those assets into a winning car.

That is the organisational story inside Ford v Ferrari. Ken Miles understands the car through direct contact with reality. Carroll Shelby connects that knowledge to engineers, mechanics, executives and the purpose of the programme. Around them sits an organisation with enormous capability — and boundaries strong enough to prevent that capability from becoming one system.

The story is often framed as talent fighting bureaucracy. That is too simple. Every part of the organisation sees something different, each perspective is rational within its own boundary, and no formal structure guarantees that those perspectives can combine without one of them taking control of the whole reality.

No one wins Le Mans from the org chart. The race is won in the relationships the org chart cannot show.

An organisation chart could locate executive authority, engineering responsibility, team ownership and operational delivery. It could not show how a sensation felt by a driver at speed should become engineering information, how quickly that information needed to travel, who had authority to act on it, or how a technical insight should survive contact with corporate reputation and internal politics.

Ford’s early GT40 programme had resources and technical ambition, but its first attempts at Le Mans did not finish. The car had to become more than a designed object. It had to become the output of a learning system connecting track experience, engineering, mechanics, logistics, leadership and rapid decision-making.

The winning capability did not sit inside any single function. It emerged between them.

02

Miles knew the car from the edge

Ken Miles did not experience the GT40 as a collection of specifications. He experienced it at the boundary between driver, machine and track — the place where assumptions became physical consequences.

A report could describe temperature, vibration, speed or braking force. Miles could feel how those variables interacted when the car was operating near its limit. His knowledge was technical, but also embodied. He did not merely drive the product after it had been designed. His experience helped reveal what the product actually was.

This kind of knowledge exists throughout organisations: with the employee who knows why the official process does not work in practice, the customer-facing team that sees behaviour no dashboard captures, the operator who recognises a weak signal before it becomes a measurable failure, or the technician who cannot yet prove the system is unstable but knows it does not feel right.

This is knowledge from the edge of the system. It is often incomplete, difficult to standardise and uncomfortable for formal authority. But it is also where reality first challenges the model.

Miles could reveal the truth of the car. That did not mean he could make the organisation act on it. Expertise is not the same as mandate.

03

Shelby connected the perspectives

Carroll Shelby occupied a different position. He understood enough of the car to recognise the value of Miles’s feedback, enough of racing to understand the team and enough of Ford to know that technical truth alone would not move the organisation.

His role was not simply to carry messages between parties. It was to preserve coherence across boundaries.

He had to translate sensation into an engineering problem, engineering constraints into operational choices, executive ambition into resources, and the reality of the track into decisions the corporate system could accept.

He also had to protect the conditions in which the team could learn: access to the driver, permission to test, room to challenge assumptions and enough sponsorship to continue when the system became uncomfortable.

Shelby did not know more than every specialist. He made it possible for what each specialist knew to become part of one system.

And he had to keep that system connected while each part continued pulling in a different direction. Coherence was not achieved once. It had to be actively maintained through setbacks, internal resistance and repeated attempts to restore conventional control.

The Business System Architect does not merely connect the system. The function holds it together long enough for the system to learn.

04

Every perspective was rational

The strength of the story is that the perspectives do not divide cleanly into right and wrong.

• Miles sees performance, feedback and the physical truth of the car.
• The engineers see technical parameters, reliability and the constraints of design.
• The mechanics see serviceability, preparation and execution under pressure.
• Shelby sees the relationships between them and the outcome they must produce together.
• Ford’s leadership sees capital, reputation, accountability and the strategic value of victory.
• Corporate management sees control, predictability and the risk of allowing an unconventional individual to become indispensable.

Each perspective protects something real.

The problem begins when one perspective is allowed to define the whole reality. Performance without reliability does not win a 24-hour race. Engineering without track feedback perfects the wrong assumptions. Executive ambition without operational understanding creates pressure rather than capability. Control without learning protects the programme from the people most capable of improving it.

The Business System Architect connects the perspectives without allowing one to become the entire system.

05

The function before the title

There was no position called Business System Architect in the GT40 programme. That is precisely the point.

The function appears whenever someone protects coherence across boundaries that the formal organisation separates. Early on, it may be concentrated in one person. In practice, it may be distributed between several people.

Miles carries knowledge from the edge. Shelby connects and translates it. Engineers turn it into design. Mechanics test whether the design can survive operational reality. Executive sponsorship creates the space and resources for the system to act.

No individual contains the whole capability. Together, they perform the function.

Giving one person a new label does not create system coherence. The capability exists only when the organisation can connect perspectives, expose relationships, translate understanding into decisions and learn from consequences.

The title may help create visibility. It cannot substitute for the conditions required to do the work. And the most important of those conditions is mandate.

The Business System Architect does not need to know more than every expert. The function must ensure that what each expert knows can become part of one coherent system.

06

The mandate problem

Seeing the system does not create the right to change it.

A Business System Architect crosses boundaries, questions local optimisation and reveals contradictions between stated purpose and operating reality. The function therefore touches authority even when it does not seek power.

It asks for information controlled by different functions. It brings perspectives into decisions that may previously have belonged to one leader. It makes dependencies visible. It challenges the narrative that the current structure is already coherent.

This is why the function becomes most necessary precisely where it may be least welcome.

• Formal mandate establishes who has authorised the work.
• Practical mandate determines whether people actually share information, time and expertise.
• Cognitive mandate allows the official interpretation of reality to be questioned.
• Political mandate protects the function when understanding begins to disturb established authority.
• Execution mandate allows conclusions to be tested through real decisions and changes.

Without these, system understanding remains intellectually interesting but operationally harmless.

Understanding without mandate becomes theatre. Mandate without understanding becomes control. Adaptive transformation requires both.

07

Holding the system together under pressure

Connecting perspectives sounds collaborative. In practice, it places the Business System Architect inside unresolved tension.

Experts may fear that translation will dilute their knowledge. Functional leaders may see cross-boundary questions as interference. Executives may support the objective while becoming uncomfortable with the implications. The people closest to reality may distrust anyone who still speaks the language of the institution.

The function can therefore be simultaneously necessary to everyone and fully owned by no one.

Shelby had to retain Miles’s trust without becoming isolated from Ford. He had to navigate corporate politics without allowing those politics to silence the track. He had to know when to negotiate, when to compromise, when to escalate and when to risk open confrontation.

This requires judgement, determination and personal resilience. It also carries a cost. The person connecting the system often absorbs tensions that the structure itself has not learned to resolve.

That burden should not be romanticised. If the organisation depends indefinitely on one individual’s energy and political skill, it has borrowed coherence rather than built it. But during the transition, someone may still need to protect the fragile connections through which learning becomes possible.

08

When the system fights back

Organisations rarely reject transformation openly. More often, they accept its language while limiting the mandate required to change decisions, boundaries and behaviour.

The film uses Leo Beebe to embody much of this tension. He represents the corporate need for control, reputation and predictability. Those concerns are not inherently irrational. A large organisation cannot place unlimited authority in the hands of every gifted individual. It cannot ignore brand risk, accountability or succession.

But the same logic can become defensive.

The system may accept the result while resisting the behaviour that produced it. It may celebrate innovation but distrust the person who challenges established authority. It may adopt the language of collaboration while keeping information and decisions inside existing silos. It may claim the success as organisational while treating the source of learning as a disruption to be managed.

The staged finish at Le Mans captures this conflict symbolically. The race had been won through the relentless search for performance and coherence. At the final moment, the meaning of victory was reframed through corporate image and control.

The organisation wanted not only to win, but to determine what the win should look like.

A system may celebrate the result while resisting the person, behaviour and decision logic that made the result possible.

This does not require villains. It requires only locally rational actors protecting different forms of value without a mechanism strong enough to keep those protections connected to the purpose of the whole.

09

Mandate must be earned — and protected

Formal authority alone would not have made Shelby effective. He also needed credibility with Miles, the engineers and the team. He had to understand enough of each perspective to translate without distorting it, demonstrate that connecting the system produced better decisions, and retain sponsorship strong enough to protect the work while results were still uncertain.

Mandate is formally granted, practically earned, continuously protected — and sometimes repeatedly rebuilt.

Too little mandate and the function becomes facilitation: workshops, maps and recommendations with no effect on reality.

Too much authority without continued connection to reality and the function becomes another centre of control.

The objective is not to stand above the system. It is to maintain enough independence to connect it, enough credibility to influence it and enough accountability to remain governed by its purpose.

10

From exceptional people to organisational capability

The lesson is not that every organisation needs its own heroic Shelby and Miles. Heroism is often evidence that the system has not yet developed the capability it needs.

Exceptional people can bridge boundaries through personal trust, energy and courage. But if the connections disappear when they leave, the organisation has not learned. It has temporarily borrowed coherence from individuals.

A mature Business System Architect function transfers that capability into the organisation. It creates interfaces through which critical information can travel. It makes decision rights and escalation logic explicit. It protects legitimate challenge. It connects expert knowledge to system consequences. It ensures that learning from reality can alter the operating model rather than merely improve performance inside it.

The function succeeds when the organisation becomes less dependent on the person who first performed it.

That is the difference between solving a problem and building adaptive capability.

11

The race beyond the org chart

Ford’s achievement at Le Mans was not the product of one driver, one leader, one engineering team or one executive decision. It emerged from their relationships.

Miles could feel what the car was doing. Shelby could protect and translate that knowledge. Engineers and mechanics could turn it into a machine capable of surviving reality. Ford could provide ambition, capital and scale.

The system worked when those perspectives became connected. It became vulnerable whenever authority, expertise or reputation attempted to contain the others.

This is the work of the Business System Architect: not designing every component, owning every decision or knowing more than every expert, but protecting the coherence through which the whole system can learn and act.

The organisation chart will always matter. It allocates responsibility and formal authority. But it will never show the entire race.

The Business System Architect protects what must happen between the boxes — and the mandate required to turn understanding into reality.

This story uses the organisational dynamics portrayed in Ford v Ferrari as a lens. Ken Miles was central to the development and testing of the GT40, Carroll Shelby led the programme that delivered Ford’s breakthrough, and Ford’s planned formation finish shaped the official result of the 1966 race. The film compresses events and dramatises individuals, particularly Leo Beebe. The argument concerns the organisational mechanism represented by the story, not a definitive historical judgement on any individual.

Selected historical references: Shelby American and Motor Sport Magazine.