The Horizon You Can Already See
Ask a leadership team what technology should do for the business and the answers arrive quickly, because everyone already has a list. The reporting is slow. The scheduling is manual. Someone rekeys the same data into two systems every Tuesday. These are real problems and fixing them is real value.
This is Horizon One — Scale Up. Doing what you already do, but better, more consistently and with less manual effort. It is the closest horizon, the easiest to justify, and the one with the shortest path to a return. It is also the one your competitors are working on this quarter.
Why the honest version of the question has a number in it
“How do we improve efficiency” produces a wish list. A better question is more specific and slightly uncomfortable: what breaks if you grow by fifty per cent tomorrow?
Not gradually. Not next year. Tomorrow. Answers to that question are never abstract. They have names in them — the coordinator who would be underwater by Wednesday, the spreadsheet that stops reconciling past a certain volume, the approval step that only works because someone senior is watching it, the quality that holds up right until the week everyone is busy.
That is the Horizon One list, and it is a genuinely useful one. It describes where the business is load-bearing and where it is held together by attention.
Why coordination is usually the strain, not the work
Draeger runs a field team of technicians on mining and medical equipment: schedules that shift, time to log, materials to order, and emergencies that cannot wait. Nothing about the technical work was broken. The strain was in knowing who was where — which jobs were active, which were next, how long travel would take. Without that picture, keeping technicians productive and honouring service agreements meant working from guesswork.
What we built was a hybrid app and website working as one. Technicians get their schedule, report on jobs, log time and order materials, with notifications when things change. The coordination team gets a live map of every technician, their clients, and the active and next jobs with travel times alongside. Coordination and the field share the same view of the same day.
The result was more jobs completed with the materials the job actually needed, better use of each technician’s time, and service agreements held under pressure. Customers noticed something too, which is the tell that a Horizon One build has been done well: they were confident the right person would be sent, and that they would be kept informed while things changed.
Why this is the least differentiated horizon
Everything above is worth doing. None of it makes Draeger impossible to replace. A competitor can buy field-service software. Several vendors will sell it to them by Friday.
That is the honest limit of Scale Up, and it is worth naming plainly because the business case for Horizon One is so easy to write that businesses can spend a decade there without noticing. Getting faster at the same thing makes you more efficient. It does not make you harder to replace. Efficiency keeps you in the race; it does not change which race you are in.
Why the first build quietly decides the second one
There is a decision hiding inside every Horizon One project, and it is usually made without being discussed. The technology you choose, the architecture you build on and — most of all — the data you decide to capture in the first phase all look different depending on where you might go next.
Build purely for today’s users and today’s volumes and you get something reasonable and cheap that does exactly what was asked. Then, eighteen months later, the interesting opportunity turns up and the answer is that it would mean starting again. That cost is not only the rebuild budget. It is the confidence spent between the first promise and the second one, which is far harder to raise a second time.
Draeger’s live picture of the field is a Horizon One capability. It is also, structurally, the raw material for something larger — because once a business can see its own operation truthfully in real time, questions become answerable that were not worth asking before.
Where to stop and look up
Start at Horizon One. The early wins live there, the first return on investment is established there, and a team that has felt one real improvement will back the next one.
Just don’t mistake the horizon you can already see for the whole landscape. Before the first build is scoped, spend an hour on the other two: who could use what you know but can’t reach you today, and what would a well-funded competitor build if they started tomorrow. The answers rarely change whether you do the Horizon One work. They frequently change how you build it.
Efficiency is the entry fee. It is not the game.