After the previous article in this journal, a question stayed.

Not a comfortable one.

Every story I’d shared had the same shape underneath it. An organisation with significant capability. A brief that defined the boundary. And a gap — sometimes vast, sometimes precise, always preventable — between what was delivered and what could have been.

The question was this.

What would have to be true for that not to happen?

Not in one organisation, in one programme, at one moment. Consistently. As a matter of how an organisation operates rather than how it occasionally performs when the right person asks the right question at the right time.

I’ve spent considerable time with that question. Tested it against the stories in this journal and against thirty years of watching organisations make large decisions. And I’ve arrived at something I want to share here — not as a finished answer but as a working proposition.

Three lenses

Three concentric lenses make the structure visible. Not as a replacement for existing strategy frameworks, as a specific tool for examining where purpose currently lives and where it could extend.

The primary lens — what you actually are

This is the innermost lens. It asks the organisation to define itself with operational honesty rather than aspirational language.

What is your core business? Not what do you say you exist to do — what do you actually do, every day, that generates value and sustains the organisation? What are the capabilities at the centre of that activity? What does your infrastructure enable? What does your data contain?

This lens is not about limiting the organisation’s sense of itself. It’s about being precise enough about what the primary purpose actually is that the boundaries become visible. Because it’s at those boundaries that the secondary lens starts to reveal something useful.

The secondary lens — who is already in your world

The second lens looks outward from the primary to the ecosystem that already exists around the organisation. Not the market in the commercial sense — the full network of relationships, dependencies, and connections that the organisation is already part of.

Suppliers. Partners. Users. Communities. The people and organisations whose lives and work the primary business already touches.

The secondary lens almost always reveals capability and potential that the primary lens can’t see. At the telecommunications provider in the previous article, the secondary lens would have revealed a living map of how the country functioned — how people moved, communicated, connected, struggled, and needed. Visible to anyone who looked with genuine curiosity.

Nobody looked.

The tertiary lens — where you operate in the world

The third and outermost lens asks the organisation to look at the context in which it exists. Not its market. Its place.

Where does the organisation operate? What are the challenges in that place — geographic, social, economic, environmental — that the organisation has some capability to address? Not necessarily directly or alone. But in connection with others, through its infrastructure, through its relationships.

The healthcare programme from the article before last had an extraordinary tertiary lens. The challenges in those locations — education, economic development, community resilience — were visible to anyone who looked. The capability to address them was present in the programme’s own architecture.

The tertiary lens was never opened.

The four things the framework requires

The three lenses tell an organisation where to look. But looking is not enough on its own. The stories in this journal have demonstrated that clearly.

Four things need to be in place for the lenses to produce something more than an interesting exercise.

The first is ownership, not as individual responsibility but as collective habit. One person seeing the wider potential cannot move an organisation that hasn’t built the habit of looking. That’s a cultural proposition, not a governance one.

The second is timing as a living practice rather than a scheduled event. The wider question needs to be present at the moments that matter — before the brief is written, before the investment is committed, before the programme is scoped.

The third is language. Organisations that want to develop the capacity to ask the wider question need to build a shared vocabulary for it, a living common language that anyone can use, challenge, and evolve.

The fourth is measurement. What doesn’t get measured remains invisible including the gap between what was delivered and what could have been.

What I’m building toward

The three lenses and the four requirements are the working framework. Practical enough to apply. Honest enough to acknowledge what it doesn’t yet fully resolve.

But sitting underneath all of this — emerging from the stories in this journal, from the framework I’ve been building, and from my reading of how other thinkers have approached the challenge of building deliberate organisational capability — is something larger.

A model for what an organisation looks like when it has built the capacity to ask the wider question not as a programme or a process but as a defining characteristic of how it operates. When the wider question isn’t asked occasionally by the right person in the right moment but consistently, structurally, as a matter of cultural habit.

I’m not ready to name it fully yet. The book is where it gets named properly and built out completely.

But I can tell you the shape of it. It’s an organisation that has decided, deliberately, to develop its capacity to see and act on its wider potential as a core function — not an add-on, not a values exercise. A core function. As fundamental to how it operates as the primary business itself.

That kind of organisation is possible. I’ve seen glimpses of it.

The difference is not small.

An invitation

This framework has been built from thirty years of experience and four specific stories. It is not complete. It will be stronger for being tested.

Does the three lens model reflect how your organisation understands itself or doesn’t? Have you seen the secondary or tertiary lens examined seriously, or does the primary lens absorb everything?

What’s missing from the framework as I’ve described it?

And — the question that matters most — have you been in the room where the wider question was asked and taken seriously? What made that possible?

I’d genuinely like to know. The responses to this article will shape what the book becomes.

Leave a comment

*This is the seventh entry in the Predictive Purpose journal — a book being built in public. If you’re reading this for the first time, start at the beginning. Subscribe at neilcatton.substack.com.

Share

Neil Catton is the author of The Next Evolution, The Cognitive Crucible and The Shadow System - available on Amazon, and writes at the intersection of technology, ethics, and human purpose.

There is a particular kind of frustration that comes from watching something fail that didn’t have to.

Not the frustration of being ignored, that’s common enough and usually survivable. Something more specific. The frustration of being able to see clearly what’s needed, of working every available channel to make that visible to the people who need to see it, and of watching the gap between what you can see and what the organisation can act on prove unbridgeable.

I’ve felt that frustration once more acutely than any other time in my career.

This is that story. Including the part where I got it wrong.

The client

The organisation issuing the bid was not a standard commercial enterprise with sustainability bolted onto its annual report as a concession to investor pressure.

It was a global leader in health, nutrition, and bioscience whose entire operating philosophy was built around a different understanding of what a business exists to do. People, planet, livelihood — not as a values statement decorating the reception area but as the architecture of every significant decision the organisation made. The UN Sustainable Development Goals were not a reporting framework for them. They were the reason the business existed.

When they issued a bid for a major technology and services partnership they were not looking for a supplier. They were looking for a partner who understood what they were actually for and who could demonstrate, concretely and measurably, how the proposed solution would advance the outcomes they existed to deliver.

I read the brief carefully. I understood what was being asked. And I understood immediately that responding to this brief the way we would respond to any other bid would not just fail to win — it would signal a fundamental misreading of who the client was.

What I built and what happened to it

I positioned the entire approach around genuine alignment with the client’s philosophy. I wrote the sustainability component in full. I designed an animation to tell the end-to-end story — not of our services and capabilities, but of the client’s own philosophy brought to life through the solution we were proposing. I argued consistently that this was not an addition to the bid. It was the bid.

The bid executives saw it differently. Not through malice, I want to be clear about that, because the easy version of this story makes them the obstacle and me the visionary and that version isn’t honest or useful.

They saw a client with a significant services requirement and a proven portfolio of capabilities that could meet it. They were experienced people who had won bids before by leading with what they knew how to deliver. That approach had worked. There was no obvious reason it shouldn’t work again.

What they hadn’t fully understood was that this client was different in a way that made the standard approach not just suboptimal but actively counterproductive. Arriving with a services pitch to a client whose identity was built around purpose-led outcomes didn’t just miss the mark. It told the client something about how we saw them.

How it ended

My role was gradually narrowed. The sustainability components were treated as a discrete workstream rather than the spine of the entire response. Once that work was completed I was stepped back from the wider bid discussions.

The bid was lost.

The feedback reflected exactly what I had been trying to prevent - a lack of genuine alignment with the client’s philosophy. The components that were remembered were the sustainability narrative and the animation.

The work that had been marginalised was the work the client had been looking for.

What I got wrong

I worked the informal channels when the situation required formal ones.

I had open discussions with the team. I guided the narrative through the process stages as best I could. I was vocal, directly and persistently, about the direction I thought we were taking.

What I didn’t do was stop at the beginning and force the formal conversation that the situation required.

I should have called an internal management meeting before the bid work started in earnest. I should have laid out precisely what the brief was asking for, what the client’s philosophy meant for how we needed to respond, and what the risks were of defaulting to the standard approach. I should have defined those risks explicitly, not as a concern or a perspective but as a formal risk to the bid outcome, and sought explicit agreement on the strategy before a single word of the response was written.

That process might not have changed the outcome. But it would have given the argument a formal status inside the organisation that informal advocacy never achieved.

Being right about the direction wasn’t enough. The system needed more than clarity. It needed process, ownership, and formal agreement. Without those, individual insight, however accurate, remains exactly that. Individual. Unowned. Unable to move the organisation.

Leave a comment

*This is the sixth entry in the Predictive Purpose journal — a book being built in public. If you’re reading this for the first time, start at the beginning. Subscribe at neilcatton.substack.com.

Share

Neil Catton is the author of The Next Evolution, The Cognitive Crucible and The Shadow System - available on Amazon, and writes at the intersection of technology, ethics, and human purpose.

I want to tell you about a conversation that started differently from almost every other conversation I’ve had in thirty years of technology work.

Most briefs begin with the system. Here is the platform we need. Here is the problem it has to solve. Here is the budget and the timeline and the definition of success. The person who will eventually use it appears somewhere in the middle, usually described as a user type or a customer segment, abstracted to the point where their actual life is no longer visible.

This one started with the person. Immediately, specifically, and without apology.

The founders were former senior military officers. That background gave the conversation a particular quality — a directness, a clarity about what mattered and why, a complete absence of the corporate softening that usually surrounds difficult truths. When they described the problem they were trying to solve there was no preamble and no hedging.

People who serve in the armed forces are being failed by the financial system. Systematically. Not through malice. Through indifference. Through a definition of the standard customer that simply doesn’t account for the reality of a life spent in service.

I remember that moment, not because it was complicated. Because it was so straightforwardly, obviously wrong — and nobody had done anything about it.

The edge case that isn’t an edge case

A soldier is deployed to an active theatre. The circumstances of their financial life change immediately and significantly. Access to standard banking services becomes difficult or impossible. The financial decisions that need to be made don’t pause for deployment. Bills continue. Family needs continue. The mortgage doesn’t wait.

Meanwhile, back home, a spouse needs to act. To access accounts. To make decisions. To manage the financial reality of a household whose primary earner is unreachable in a conflict zone.

In a standard retail banking platform this is an edge case. An unusual circumstance requiring manual intervention and exceptions processes. Something to be managed around rather than designed for.

The founders didn’t see it as an edge case. They saw it as a defining characteristic of the life their customers actually lived. Not an exception to be accommodated. A reality to be designed around from the start.

Auto-delegation — the ability for a serving partner to grant their spouse full authority to act on their behalf, triggered by deployment and managed through the platform — sounds simple stated that way. But in the architecture of a standard financial services platform it is genuinely complicated, because standard platforms were never built with this situation in mind.

That difference in assumptions is everything.

What the founders understood that the mainstream market didn’t

Financial services institutions had looked at serving military personnel and made a calculation. The demographic was small. The circumstances were complex and costly to design for. The return on investment didn’t justify the effort.

So they were served badly, or not at all. Treated as a niche. An edge case.

What the mainstream market had failed to see was that the military community is not just a demographic. It is a culture. A set of values and relationships and mutual obligations that extend far beyond the individuals currently serving. Veterans. Families. The blue light services — police, fire, ambulance — whose circumstances share many of the same characteristics.

The founders understood this because they had lived it. They weren’t designing for a market segment. They were designing for a community they were part of.

The surprise I couldn’t shake

My role was partly technical — establishing the architecture, supporting the business proposition, providing the reality check that every conviction-driven venture needs.

But the feeling I kept returning to throughout the work wasn’t technical satisfaction. It was something simpler and more uncomfortable.

Surprise.

Not at what the founders were building. At the fact that nobody had built it before.

These were people putting their lives on the line. And the financial system that the country they were protecting had built had looked at them and seen an edge case.

Not a priority. Not a community deserving of genuine design consideration. An edge case.

Why? Not because of bad intentions. Because of a definition of the standard customer so deeply embedded in the architecture of financial services that the people who built those systems had never thought to question it.

The mainstream market wasn’t cruel. It was incurious. It had defined its purpose narrowly and built efficiently inside that definition and never looked beyond it to ask who was being failed.

The founders had looked. They had seen clearly. And they had decided to build from the wider frame rather than petition the narrow one to change.

That’s the difference. Not a better version of what existed. A different starting point entirely.

Leave a comment

*This is the fifth entry in the Predictive Purpose journal — a book being built in public. If you’re reading this for the first time, start at the beginning. Subscribe at neilcatton.substack.com.

Share

Neil Catton is the author of The Next Evolution, The Cognitive Crucible and The Shadow System - available on Amazon, and writes at the intersection of technology, ethics, and human purpose.

The most important story in this journal begins with a confession.

Not about something I watched happen to someone else. About something I missed entirely — sitting directly in front of me, for years, while I was too focused on the work to see it.

That’s a harder thing to write. But I think it’s the most important story in this journal. Because if someone with my experience, my access, and my proximity to the capability could miss it completely, the problem isn’t individual negligence or lack of imagination.

The problem is structural. And it’s everywhere.

The work

I was brought in as part of a large-scale digital transformation at a major national telecommunications provider. My responsibility covered significant portions of the architecture — data, artificial intelligence, cloud infrastructure, integration, digital platforms.

The organisation sat underneath a substantial portion of how the country communicated. Consumers. Businesses of every size. Public institutions. Emergency services. The data flowing through its systems touched almost every aspect of how the nation functioned — patterns of behaviour, movement, communication, consumption, need.

The scale was not abstract. It was one of the largest and most consequential data environments in the country.

We ran a structured process across every major part of the business — working with data directors, mapping what existed, understanding what was usable, identifying where value could be created. It was rigorous work. We selected a platform capable of handling the full complexity of what we had. We built the architecture to support it. And then we identified the use cases.

Cost savings. Cost reduction. Cost avoidance. Revenue generation. Every one of them pointing in the same direction — inward. Toward the organisation’s own commercial interests. Toward the brief as it had been written.

We found significant value. Enough to justify the investment many times over.

And I was satisfied. Because we had answered the question we had been asked.

The moment the frame cracked

Some time into the programme the pandemic arrived.

I was briefed on a request that came in from government and public health bodies. The ask was for data that could inform the national response. Mobility patterns. Population movement. The kind of signals that, properly anonymised and aggregated, could help understand how a virus was spreading and where interventions might be most effective.

The capability to respond to that request existed. It had always existed. We had spent considerable time and resource making it more sophisticated, more integrated, more powerful.

But the response was reactive. The request arrived from outside. Government asked. The organisation responded.

Nobody inside the organisation had looked at that data capability and asked — before the pandemic, before the crisis, before the urgent external request — what could this see that nobody else can see? What could it enable beyond our own commercial interest?

I hadn’t asked those questions either.

Standing in the briefing, understanding what was being requested and why, I felt something shift. Not dramatically. More as a quiet recognition that the boundary I had been working inside had edges I’d never looked for.

The slow realisation

I’ve thought about this a great deal since leaving. Not with guilt, that would be self-indulgent and beside the point. But with a genuine attempt to understand how it happened.

The answer I keep arriving at is this.

The brief was complete. Not in the sense of being comprehensive, in the sense of being self-contained. It defined the problem, specified the scope, described the measures of success, and created a working environment in which all of those things felt like the whole picture. The boundary wasn’t visible because the boundary was everything. There was no outside to it from where I was standing.

The work itself reinforced this. Good, rigorous, demanding work has a way of absorbing attention entirely. When you’re solving hard problems inside a complex organisation, with real constraints and real accountability, the question of what lies beyond the brief doesn’t naturally surface. It requires a deliberate act — a specific moment, owned by someone, built into the process — to surface it.

That moment didn’t exist. Nobody had designed it in. And so it didn’t happen.

What this costs

The pandemic data request was answered. People were served who might not have been. That matters.

But it was answered reactively. Because a crisis arrived and forced the question. Not because anyone inside the organisation had looked at what they had and asked — before the crisis, before the urgency — what could this do for people beyond our immediate purpose?

The problem is that the system produces this automatically, reliably, and invisibly even when the people inside it are capable of something more. Even when the capability to see further exists. Even when the data, the infrastructure, and the intelligence are all present.

The question I’m trying to answer in the book I’m writing is how you change that before the crisis does it for you.

More on that soon.

Leave a comment

*This is the fourth entry in the Predictive Purpose journal — a book being built in public. If you’re reading this for the first time, start at the beginning. Subscribe at neilcatton.substack.com.

Share

Neil Catton is the author of The Next Evolution, The Cognitive Crucible and The Shadow System - available on Amazon, and writes at the intersection of technology, ethics, and human purpose.

I remember looking at the plans and seeing two things simultaneously.

The first was what everyone else in the room was seeing. A healthcare infrastructure of extraordinary ambition — medical cities designed to deliver world-class treatment to people who had never had reliable access to it. Thousands of beds. Thousands of doctors and nurses. Outreach programmes reaching into rural communities. Digital health initiatives connecting patients to specialists across vast distances. A tiered system designed so that nobody would be turned away regardless of what they could pay.

It was, by any measure, a remarkable thing to be part of.

The second thing I saw was everything else.

Not because I was looking for it. But because thirty years of working across public sector programmes — education, justice, social services, community infrastructure — had given me a particular kind of peripheral vision. When you’ve spent long enough watching what happens to people when systems fail them, you develop a sensitivity to what those same people might do if the conditions were right. What becomes possible when capability, location, and intent converge in the same place.

And what I could see, looking at those plans, was that the conditions were extraordinary.

What the plans actually contained

The medical cities were designed around a core set of capabilities. Healthcare delivery at the centre — but surrounding it, and essential to it, a ring of complementary functions. Education and training facilities. Manufacturing capability. Research and development infrastructure. Commercial and administrative zones. Community services.

All of it in one place. All of it connected. All of it built around the premise that healthcare doesn’t happen in isolation from the rest of life.

That premise was right. But it didn’t go far enough.

The education and training infrastructure wasn’t just a pipeline for nurses and doctors. It was a learning capability that could be extended to agricultural practice, to business skills, to the kind of foundational education that gives people the tools to improve their own circumstances. The manufacturing capability wasn’t just a supply chain for medical equipment. It was a platform for local production, for small business development, for the kind of economic activity that generates employment and keeps value inside a community. The research and development function wasn’t just a support system for clinical innovation. It was a mechanism for understanding hyper-local need.

And the physical presence itself — the fact of a medical city in a specific location, with infrastructure, with footfall, with the trust of a community that had watched it being built — that was perhaps the most undervalued asset of all.

The pattern was familiar from UK programmes. A community hub that started as a health centre and became the anchor for everything else a neighbourhood needed. A digital infrastructure built for one purpose that became the foundation for ten things nobody had planned.

The scale was not.

The conversation that didn’t happen

I raised it. Not formally — there was no formal process for raising it, which was itself part of the problem. But in the conversations that happen around the edges of large programmes.

The response was not hostile. It was something more difficult to work with than hostility.

It was a kind of polite incomprehension. We’re building healthcare infrastructure. That’s what the programme is. That’s what the investment is for. The suggestion that the same infrastructure could deliver wider outcomes wasn’t rejected after consideration. It simply didn’t connect. It was answering a question nobody had asked.

And that was the end of it. Not a decision. Not a refusal. A non-conversation. The kind that leaves no record and costs nothing visible and forecloses an enormous amount of possibility without anyone being aware that a decision has been made.

What it taught me

The wider potential wasn’t hidden. It was visible to anyone who looked at the plans with a different question in mind. It didn’t require additional investment to identify, just a different question asked earlier, by someone whose job it was to ask it.

But nobody had that job. The brief defined the boundary. The boundary defined the conversation. And the conversation found exactly what it was designed to find.

The programme built what it was designed to build. People are being served who weren’t before. That matters enormously.

The missing piece is a conversation that could have happened when the plans were being drawn — the one about what else this could be for.

That conversation didn’t happen because nothing in the programme was designed to make it happen.

That’s the problem I’m writing about.

Leave a comment

*This is the third entry in the Predictive Purpose journal — a book being built in public. If you’re reading this for the first time, start at the beginning. Subscribe at neilcatton.substack.com.

Share

Neil Catton is the author of The Next Evolution, The Cognitive Crucible and The Shadow System - available on Amazon, and writes at the intersection of technology, ethics, and human purpose.

There’s a question that almost never gets asked in the room where it would matter most.

Not what do you do. Not what problem are you solving. Not what does success look like by the end of the financial year.

Something simpler and more unsettling than any of those.

What are you actually for?

I’ve spent thirty years inside organisations of every kind — public sector, private enterprise, global programmes, early stage ventures. I’ve sat in the rooms where large decisions get made. I’ve watched investment cases get built, briefs get written, programmes get scoped and launched and measured and closed.

And I can count on one hand the number of times I heard anyone ask that question seriously. Not as a values exercise. Not as a branding conversation. As a genuine interrogation of whether the organisation was operating at the full extent of what it could be.

Most of the time nobody asked it at all. Not because the people in the room lacked intelligence or ambition. But because the system they were operating in wasn’t designed to surface it. The brief defined the problem. The problem defined the scope. The scope defined the investment. And everything that followed was optimised against that original definition — efficiently, professionally, and entirely inside a boundary that nobody had thought to question.

The result is a gap. A consistent, structural, almost invisible gap between what organisations deliver and what they could deliver. Between the problem they solved and the problems they could have addressed with the same capability, the same investment, the same infrastructure.

I’ve seen this gap in a healthcare programme designed to serve hundreds of millions of people, where the technology and infrastructure being built had the potential to address needs far beyond the original brief — education, local economic development, community resilience — and nobody in a position to act on that potential was ever asked to look for it.

I’ve seen it in a national data programme where the capability being built could have informed public health, urban planning, and economic inclusion at a scale no other organisation could have matched — and the entire exercise was pointed inward, at commercial returns, because that’s what the brief asked for.

I’ve seen it in a bid for a global organisation that had already done the hard work of connecting its business to wider societal outcomes — and watched the response team default to selling services, because that’s what bid teams do, because that’s what the internal incentive structure rewarded, because nobody had built the habit of asking what the client was actually for before deciding what to offer them.

In each case the people involved were capable. The intentions were good. The work was competent. And the gap remained, because nothing in the process was designed to close it.

The question my new book is trying to answer is what it would take for organisations to develop the alternative. Not just to ask the wider question once, in the right moment, with the right person in the room. But to build the habit of asking it consistently, structurally, before the brief gets written and the frame gets set.

I’m building that answer in public, in part because testing the argument as it develops feels more honest than presenting a finished version I’ve already decided is right. So if something here resonates — or doesn’t — I’d genuinely like to know.

Have you been in that room? Have you watched the wider question go unasked? Have you been the person who tried to ask it and couldn’t get it taken seriously?

I’ll be sharing the stories that shaped this argument over the coming weeks. They’re drawn from programmes I was part of, decisions I watched get made, and a few moments where I got it wrong myself. No company names. But every detail that matters.

Leave a comment

*This is the second entry in the Predictive Purpose journal — a book being built in public. If you’re reading this for the first time, start at the beginning. Subscribe at neilcatton.substack.com.

Share

Neil Catton is the author of The Next Evolution, The Cognitive Crucible and The Shadow System - available on Amazon, and writes at the intersection of technology, ethics, and human purpose.