Twenty Perspectives Later: How Tektology Thinks
When we started publishing Perspectives, the intention was straightforward. Tektology has an unusual depth and breadth of expertise for a business of our size, and we wanted to make more of that thinking visible.
Twenty Perspectives later, we have written about hospitals, digital health, data, AI, Lean, leadership, governance, workforce, estates and the difficult middle ground between strategy and delivery. They are different subjects, written by different people in the business, with different professional backgrounds. But, when we stood back and looked at them together, there’s a golden thread running through the work.
We believe the quality of transformation is determined remarkably early by the questions an organisation allows itself to ask before it commits to an answer.
It helps explain not just what Tektology does, but how we think, and perhaps why clients repeatedly trust us with difficult transformation problems.
Systems transformation has a sequencing problem
Complex transformation is often described as a delivery challenge. But, many transformation problems begin earlier, because when an organisation identifies a need it quite naturally begins translating it into an answer and this sequence needs disruption.
If we start with, we need another 500 beds, we need to recruit someone into this role, we need an AI strategy, each may ultimately be the right answer. The problem is not that somebody has formed a hypothesis. The problem comes when the hypothesis becomes the starting point for everything that follows. The organisation can then begin gathering evidence to support the answer rather than using evidence to solve the problem.
If someone walks into a doctor's surgery and says, “I think my leg is broken”, the clinician does not immediately start preparing a cast.
They ask what happened. Where does it hurt? What function has been lost? Can the patient bear weight? They conduct an examination and perhaps an X-ray and ask what does that tell us? What does the evidence show?
The patient's hypothesis is useful information, it is not yet the diagnosis. And the more plausible or passionately held the hypothesis is, the more important it is that certainty does not substitute for a thorough diagnostic process..
And yet in large-scale transformation, the presenting hypothesis can very quickly become the programme.
Going further upstream
Across our Perspectives, we keep returning to this point from different directions.
When we think about hospitals, we do not begin with the building. We ask what care the population will need, how models of care are changing, which activity genuinely requires a hospital setting and what technology may make possible elsewhere.
When somebody says they need 500 beds, we want to understand what is driving that number. What population and demand is it intended to serve? What activity genuinely needs to happen in an inpatient setting? What assumptions are being made about length of stay, occupancy, flow and models of care? What could happen differently elsewhere in the system? Only then can we understand how many beds are actually required.
When the problem appears to be an EPR, we want to understand the outcome the organisation is trying to achieve, the processes underpinning it and where the existing system is creating friction before deciding what technology needs to change.
When a role becomes vacant, replacing the person like-for-like may be exactly right. But it is also an opportunity to ask what work needs to happen, which tasks require human judgement, which could be redesigned or automated and whether the role should exist in precisely the same form.
The same pre-diagnostic instinct appears in our thinking about data, governance, Lean, artificial intelligence and organisational change.
But going upstream does not mean leaving technology until the end. Understanding what is now possible, and what is becoming possible in that space, can itself change the questions we ask and the answers available to us.
A blank sheet is not an empty one
Complex systems rarely produce problems in neat isolated categories, which is why we look at system transformation on several planes at once. A technology problem may actually be a process problem. A capacity problem may actually be a flow problem. A people problem may actually be an incentive problem. And often, several of those things are true at once.
We often describe our approach as beginning with a blank sheet of paper and that can be misunderstood. It does not mean arriving without a point of view, evidence or experience. Quite the opposite.
Across Tektology there is deep experience of running public systems, designing and operating healthcare, digital transformation, infrastructure, finance, technology, Lean, organisational behaviour, leadership communication and major programmes across multiple countries.
That experience matters because it changes what we can see. It allows us to recognise patterns, understand dependencies and know which questions may expose something important.
But experience can also become a constraint if every new situation is made to resemble the last one. The discipline is not to forget what we know, but to avoid allowing what we know to diagnose the problem too early.
Expertise should expand the questions available to us before it narrows the answer, because we also don’t want to be slow to act once solutions begin to form.
Judgement is what connects the pieces
This is perhaps the strongest thread that has become visible to us through the first twenty Perspectives.
Clients do not only need access to expertise. In complex transformation, expertise is abundant. There are specialists in technology, estates, finance, operations, workforce, data and almost every other component of a system.
The harder question is what to do with all of it.
Which evidence matters?
Which assumption needs challenging?
Which part of the system is producing the effect we can see somewhere else?
What should remain fixed and what is genuinely open to redesign?
Where is technology the answer, and where is it merely digitising a poor process?
When does experience give us confidence, and when should it make us more curious?
That is where judgement becomes critical. Systems transformation does not happen one discipline at a time. Technology, infrastructure, people, behaviour, finance, governance and operations move together. A decision in one part of the system alters the conditions somewhere else.
The work is therefore not simply to know more, it is to see more of the system before deciding.
From twenty Perspectives to the next twenty
We started Perspectives to show more of what sits inside Tektology and we will keep doing that. After twenty pieces, we can now see that the more important story may be the way that expertise is applied.
Across the company our approach is remarkably consistent: challenge the starting assumption, understand the system around it, define the outcome and only then begin narrowing the answer.
It is one reason our work does not always start where a client expects it to and why our clients often bring us back when the next difficult problem appears.
In systems transformation, some of the most consequential decisions are made before anything has been designed, procured or implemented.
They are made in the questions we choose to ask first and that’s something we are committed to doing excellently.
Tektology is a global systems transformation advisory. We help organisations make better decisions through complex transformation, bringing together deep expertise across technology, infrastructure, process, people and governance. Our approach is digital-first and human-led: using what technology makes possible to rethink systems from the outset, while keeping human judgement at the centre.