The Space Between: What a children’s hospital learned from Ferrari’s Formula One pit crew

Working in Finance for years has taught me something slightly uncomfortable: the biggest issues rarely sit inside the actual work, but in the handovers.

The month-end close is structured, the controls are defined, roles and responsibilities are documented. And then comes the transition - the point where one team “finishes” and another is supposed to “just pick it up.” That invisible moment has a remarkable ability to generate follow-up emails, clarification calls, and the occasional existential crisis.

In this article, I explore why risk concentrates at these transition points. I use a case from Great Ormond Street Hospital and benchmarking insights from Scuderia Ferrari to examine what happens when coordination is engineered with the same discipline as the core task itself.

Spoiler: the solution wasn’t “communicate better.”

Whether it’s financial close cycles, SaaS implementations, or AI moving from development to production, the pattern is consistent - when ownership shifts without explicit orchestration, variability moves in quietly and makes itself comfortable.

The article ended up longer than intended, so over the next few weeks I’ll break parts of the case into short carousels with more practical angles.

If you’ve ever thought, “But we followed the process,” and still ended up firefighting - this one might be of interest.

#LeanSixSigma  #DMAIC  #OperationalExcellence  #SystemsThinking hashtag #ContinuousImprovement  #RiskManagement

In every organisation, there are specific moments when risk does not build slowly over time but instead concentrates in a narrow window of activity. In my experience, these moments are typically not found in the core execution itself; they emerge at transition points - when responsibility moves from sales to implementation, when development hands over to manufacturing, or when a case is escalated from Tier 1 to Tier 3 support. It is in these spaces between defined domains that exposure increases.

Within each function, the work is usually structured with care. Roles are defined, performance expectations are measurable, and expertise is cultivated over time. What often receives less deliberate attention is the transfer between these domains. The transition is treated as an administrative step, something procedural and routine, rather than as a critical coordination event that requires its own design discipline.

That difference has consequences. Transitions rely on synchronisation between teams, clarity around decision rights, shared understanding of context, and a disciplined sequence of actions that frequently unfolds under time pressure. When these elements are left implicit instead of intentionally structured, variability enters the system quietly and begins to compound. Over time, this variability shows up as delays, rework, missed assumptions, and ultimately as risk that appears unexpected but was, in fact, embedded in the way the transition itself was designed.

A Healthcare Case That Illustrates the Pattern

At Great Ormond Street Hospital, a fragile transition became visible in the space between the operating theatre and the Intensive Care Unit (ICU). Inside the theatre, surgical performance was highly specialised and executed with technical precision shaped by years of training and repetition. What followed the procedure, however, required a different form of excellence: the coordinated transfer of a vulnerable patient into intensive care, where multiple specialists needed to align in real time while the patient’s condition could evolve minute by minute.

As the surgical procedure concludes, the environment undergoes a critical shift: the singular technical focus of the operation gives way to a period of multi-disciplinary urgency. While the clinical activity remains intense, the transition introduces a new layer of systemic complexity. Specialists from anesthesia, intensive care, and surgery converge, creating a high-density exchange of information and responsibility.

In this window, communication often unfolds in parallel rather than in sequence. Precise, necessary instructions are issued and acknowledged, yet they lack a unifying cadence. Although every participant possesses deep expertise and total commitment, the transition begins to rely on shared intuition rather than explicit orchestration.

Two physicians, Martin Elliott and Allan Goldman, recognised a subtle but consequential pattern. The surgical phase reflected deep individual mastery supported by well-established protocols, yet the handover depended largely on simultaneous communication among experts without a clearly defined orchestration structure. Everyone involved was highly competent, but the coordination mechanism itself had not been engineered with the same rigour as the surgery.

Their recognition of the vulnerability did not arise from a single failure but from observing recurring variability during transfer: overlapping communication, parallel instructions, and moments where responsibility felt shared rather than clearly anchored. The question shifted from individual performance to system design. If surgery was engineered with precision, why was the handover left to unfold organically?

Exposure to high-reliability environments outside healthcare provided the catalyst. Elliott encountered the structured choreography of Formula One pit stops, where complex, high-risk tasks are executed under extreme time pressure through predefined roles, controlled communication, and disciplined sequencing. What stood out was not speed but coordination architecture.

This insight led them to study the pit lane operations of Scuderia Ferrari within Formula One, translating principles of explicit leadership, scripted communication, and structured micro-sequencing into the clinical transfer between theatre and ICU.

The Benchmarking Insight: Systemic Synchronisation

A Formula One pit stop is frequently associated with speed, yet speed is merely the visible outcome of a deeper structural discipline. The operation depends on tightly choreographed sequencing, absolute clarity of role allocation, and a clearly established single point of authority. Every movement is predefined, every specialist understands the precise trigger for action, and ambiguity is intentionally engineered out of the environment so that expertise can function without friction.

When engineers from Scuderia Ferrari later observed the hospital handover at the Gemba, the differences were structural rather than clinical. They noted simultaneous dialogue unfolding without defined sequencing, physical positioning that obstructed visibility and flow, leadership that remained implicit instead of formally assigned, and information exchange that lacked structured confirmation loops.

Within Formula One, the “Lollipop Man” operates as the command anchor during a pit stop, serving as the single authority responsible for signalling stage completion and authorising the car’s re-entry into the race. All actions converge toward that signal, creating unambiguous authority and sequence alignment.

During the hospital transition, no equivalent coordination role existed. Leadership diffused at the very moment synchronisation was most critical. The resulting variability was subtle rather than dramatic, yet its recurrence embedded risk into the system.

For organisations navigating digital transformation, financial close cycles, SaaS implementations, or AI deployment, the pattern is recognisable. Core technical activities receive optimisation attention, while the interfaces between them are assumed to function through professional goodwill and informal alignment.

DMAIC as Structured System Design

At this stage, Lean Six Sigma's DMAIC methodology transcends its role as a troubleshooting toolkit and matures into a framework for architectural thinking. It shifts the focus from fixing isolated errors to engineering the structural conditions that make reliability inevitable.

Define: Anchor the Problem to the Critical Outcome

The team deliberately avoided framing the issue as communication inefficiency. Instead, the problem was defined in relation to patient safety and reliability during the transfer from surgery to ICU.

That reframing carried strategic weight. Lean Six Sigma begins with what is critical to quality from the customer’s perspective, and in this context the patient represented the ultimate stakeholder. By anchoring the definition to outcome protection rather than convenience or speed, the transition was recognised as a high-risk process deserving explicit design attention.

When problem statements are misaligned, organisations optimise peripheral variables. When definitions are anchored to what truly matters, improvement efforts align accordingly.

If the team had defined the problem as "inefficient handover communication," they might have simply optimized for speed by creating a digital summary - a peripheral variable that ignores the chaotic environment of the ICU. By anchoring the definition to "patient safety and reliability," they recognized that the true goal wasn't just sending information, but ensuring reception and synchronization. This led them to adopt the Formula 1 "Lollipop Man" model - appointing a single coordination lead to anchor the transition, which addressed the core risk of diffused leadership during a life-critical window.

I have found that the urge to 'jump to solutions' is a universal blind spot. It feels productive to act, but action without an anchored definition is just noise. Throughout my career, the LSS methodology has been more than a toolkit; it has been a guiding principle that helps me resist the allure of the quick fix in favour of structural reliability. If we don’t have the patience to define the problem, we rarely have the time to fix it twice. 

Measure: Ground Improvement in Observed Reality

The team recorded live handovers, analysed recurring patterns, and quantified distinct categories of variation. The data did not reveal catastrophic breakdowns; instead, it exposed repeated micro-deviations such as overlapping dialogue, sequencing ambiguity, diffuse leadership during transition, and information gaps under time pressure.

In complex systems, material failures rarely originate from a single dramatic error. They emerge when small variations accumulate and align. In technology environments this resembles cascading failure; in operational settings it reflects compounded variation. In both cases, the underlying source is structural.

Direct observation replaced assumption and created a factual basis for redesign. In many organisations, the documented process reflects the idealised version of execution. Direct observation often reveals a different sequence entirely.

Analyse: Examine Process Architecture

The analytical lens focused on whether the process architecture supported reliable execution. Structural gaps became explicit: the absence of a clearly defined transfer sequence, leadership that dissipated during transition, physical configuration that limited communication flow, and elevated cognitive load without supporting scaffolding.

From a Six Sigma perspective, this pattern represents common-cause variation embedded within the system. Strategically, it signals misaligned process design.

When variability is built into workflow architecture, professionals compensate through vigilance and experience. Such compensation may sustain performance temporarily, yet it remains effort-dependent rather than structurally stable. The more robust design question asks how to shape the environment so that correct execution becomes the natural default.

Improve: Introduce Structural Clarity

The resulting improvement was conceptually simple and structurally intentional. A single leader was formally designated for the transfer phase. Roles and physical positioning were explicitly defined. Communication followed a predictable sequence. The handover evolved into a rehearsable and standardised routine.

Standard work stabilised the environment in which clinical expertise operated. Measurable outcomes followed: fewer technical errors, reduced information omissions, and a lower probability of compounded risk.

The most meaningful gain was not speed or efficiency, but risk de-amplification. As variation decreases, reliability strengthens without increasing human effort.

Control: Institutionalise Reliability

The redesigned process was embedded into training and daily practice so that reliability no longer depended on informal alignment or individual heroics.

Within Lean Six Sigma, control is often misunderstood as oversight. In practice, it protects sustainability. When stability is built into process architecture, performance becomes predictable and less reliant on exceptional effort.

This is where many digital initiatives encounter difficulty. Tools are implemented and workflows adjusted, yet behavioural reinforcement and structural embedding remain insufficient. Without deliberate control mechanisms, improvements gradually erode under operational pressure.

A Practical Diagnostic: Locating the Structural Root

When performance deteriorates, organisations frequently default to additional training, new technology, or expanded controls. In many cases, however, the underlying issue resides at a transition boundary.

Before committing to intervention, it is useful to examine a structured line of inquiry that distinguishes between task-level variation, capability gaps, minor optimisation opportunities, and transition design failure.

This logic helps differentiate between:

• A local task-level variation

• A capability or training gap

• A minor optimisation issue

• Or a transition design failure

If the issue concentrates at a boundary between teams or process phases - and skilled people are already involved - the likelihood increases that the underlying problem is architectural rather than individual.

In those cases, stabilising the transition should precede further optimisation.

Beyond Healthcare: A Systems-Level Implication

This case reflects a broader organisational dynamic. Risk concentrates at transition points: financial close handovers, project phase-gate movements, DevOps boundaries within SaaS environments, system integration interfaces in fintech platforms, and AI model deployment from development to production.

As organisations adopt automation, distributed teams, and AI-enabled workflows, the number of transition interfaces expands. Each boundary between systems, teams, or algorithms represents a potential concentration point for variability.

Designing these boundaries intentionally extends beyond operational refinement; it constitutes strategic architecture. If you automate the work but leave the handovers ambiguous, you have accelerated variability - not eliminated it.

The most consequential improvements often emerge not within the visible centre of activity, but within the interfaces connecting those activities. When those interfaces are engineered with the same discipline as core execution, risk diminishes, cognitive load stabilises, and performance becomes structurally dependable rather than effort-dependent.

Ready? Let's talk.