About
Some problems arrive before the field built to solve them.
Established disciplines are extraordinarily good at answering established questions. The harder problems often appear between them.
The approach
Established disciplines are built to answer established questions, and they do it well. The difficulty arrives when a question does not belong cleanly to any of them. A technical decision becomes a security problem. A medical innovation becomes a question of human judgment. An operational advantage becomes a dependency. A new capability changes the rules that form around it.
Each assessment along the way can be individually correct while the combination is wrong. The failure modes that matter tend to live in the space between them — in a dependency nobody owned, an assumption nobody restated, or a control that was never capable of producing evidence.
Sometimes the first task is not finding the answer. It is understanding the problem. Several people can look at the same situation and each describe something different; often none of them is wrong, and none of them is looking at the whole of it.
We work from the problem outward. The two halves of the name are the method: applied, because we care what can actually be built, secured, operated, and demonstrated; horizons, because the consequences worth planning for are usually the ones not yet fully in view.
Some of that perspective is first-hand. Our work in health and human systems is informed by direct clinical and operational experience — advanced-practice nursing and emergency medicine — rather than by observing the field from outside. High-consequence environments are a useful corrective. They make the distance between how a system performs and how it behaves difficult to ignore.
Applied Horizons works on problems that do not yet have a playbook.
How we work
- The question before the answer
- A well-framed problem is usually most of the work. We would rather spend the first part of an engagement establishing what is actually being asked than answer the wrong question efficiently.
- Whole systems
- A technical question is followed through to its operational, security, governance, and institutional consequences rather than handed across at each boundary.
- Second order first
- The immediate effect is usually well understood by the time we are asked. The value is in what the capability makes load-bearing, and what that makes fragile.
- Evidence over assertion
- A control that produces no artefact is a preference. We are interested in what an organisation could actually demonstrate, to a regulator or to itself.
- Tested where possible
- Where a question can be settled by building something small, we would rather build it than argue about it. That work is published under Research.
- Written plainly
- Analysis that cannot be read by both the engineering team and the board has failed at the boundary it was meant to cross.
What we are not
Applied Horizons is a boutique practice, and describes itself as one. We are not a research laboratory, a law firm, a healthcare provider, a large organisation, or a government contractor, and we do not present ourselves as any of them.
We examine health technology, regulation, and governance as a research practice. That is not the same as practising in either field: we do not provide clinical care or medical advice, and we do not provide legal advice or representation.
We publish analysis and technical work. We do not publish client names, invented case studies, or metrics that cannot be substantiated. Where a project is conceptual rather than built, it is labelled conceptual. Where we have not done the work, we say so.
This is a deliberate constraint. The credibility of the practice rests on the quality of the thinking and the accuracy of the claims — which means the claims have to stay accurate as the practice grows.
We keep looking after the obvious answer appears.
If that is roughly how you already think about your own problems, we should probably talk.