Thought piece

Many presentations, one mechanism

Neil Middleton · 15 October 2026

Cindy, a co-founder, is a doctor. In her practice the presentations differ and the people differ, and her working hypothesis is that one underlying process sits beneath many of them, so one toolkit applies, subject to the individual. I have come to see the same shape in UnityTrip.

The presentations I am shown are never the same. A finance team shows me leakage: travel spend that reached the ledger with no approval in front of it, and a seat on the company aircraft that its spend report values at zero. An operations desk shows me a flight that left half empty while people were told there was no seat. A travel management company shows me a portal its agents have to log into for one client, and re-keying. A people team shows me fairness: who got the seat and who did not, and why. A manager shows me a report that does not agree with what happened.

Each of them believes its symptom is the condition. None of them is wrong about the symptom.

What I see underneath is one thing. An operation that moves people generates events from many sources, bookings, changes, approvals, cancellations, claims, flight logs, payments, from many roles, over days and weeks, and nobody holds all of it at once. The portal is another event source that never reached the record. The empty seat is an allocation nobody rationed, because the seat has no fare. The report that disagrees is reality and its representation drifting apart. The failures look different because each participant sees part of the system. They are the same failure: the representation of what happened is incomplete, late, or held in three places that do not agree.

So the toolkit is the same each time. One record of every movement and every dollar, with two gates on it: no traveller moves without a booking number, and no provider is paid without an approved claim number. Rules held as configuration, so the operation's own way of doing things is data the engine executes, not code someone maintains. And a review that reads the record with the people who ran the operation, because the request is rarely the need, and because the record does not hold what the dispatcher saw when the pilot walked in.

Subject to the individual. No two operations ration the same way, approve the same way or post to the same ledger, and the toolkit does not ask them to. Each tenant's rules are its own; the mechanism underneath them is shared. That is the only sense in which I would use the word personalised.

Both practices are deterministic, and both are adaptive, and the two are not in tension. If Cindy departs from the protocol then the regulator would get interested; if patient condition does not improve, then she loses them. UnityTrip decides every booking the same way under the rules in the model, and the model changes as the technology and the business change; a model that stopped adapting would be the end of us. Deterministic at the point of decision, adaptive in the model. Guidelines are written for the average patient and booking tools for the average trip, and the complex patient and the leased fleet are the same kind of case: rare in the statistics, dominant in the cost.

This is also why the website looks the way it now does. The mechanism is written once, on the pages that hold the model. The presentations each get a page in their own currency: what finance can require, what a TMC can bid with. Nobody is asked to read the whole body of work to find their symptom in it. They find their symptom, and the page points at the mechanism.

The danger in a lens like this is that it starts to explain everything. In a clinic, one underlying process does not make every condition the same condition. In an operation, coordination does not make every problem a coordination problem. Aircraft maintenance, airworthiness, flight and duty limits and fatigue are their own disciplines with their own systems, and UnityTrip does not touch what does not touch a traveller.

What the lens does claim is reality arrives as events. An operation survives by coordinating them. And the quality of that coordination is set by the quality of the one representation everyone works from, which is why the record forgets nothing: a record that cannot forget cannot bury a mistake, and that is the error-correction loop aviation built into itself long before software did. Travel is where I have tested this, since 2018, at the operations that could least afford to get it wrong. I no longer think it is only about travel.

Also: The capacity to surge, The second shift and UnityTrip and SAP: a single source of truth. The pages for finance and for travel management companies are the presentations; the platform thesis is the mechanism.