The Internal Paradigm Shift
Edition 5 of this newsletter looked outward. Twenty five years of technology paradigm shifts, from mainframe to AI, and what it felt like to live through them as a practitioner. That was an external arc. The world changing and the work changing with it.
Edition 10 looks inward.
This is a personal reflection. Not a framework, not a set of observations about the industry or the organisation. Just an honest account of how the internal landscape has shifted across the same twenty five years. Specifically, how the shape of professional identity and personal satisfaction has changed, and is still changing.
Early in my career, satisfaction was not complicated.
I was a mainframe developer. COBOL. The work was precise, bounded, and honest. You wrote a program, you ran it, you knew immediately whether it worked. There was a craft to it that went beyond correctness. Structure mattered. Efficiency mattered. The way the code was organised mattered. A well-written program looked a certain way, and you knew it when you saw it. That knowledge gave you something to stand on.
The feedback loop was short and the signal was clear. Nobody had to tell you it was good. You could see it yourself.
Moving into design work changed the shape of the satisfaction but not its nature. Early in my consulting years, I worked on a complex integration programme across a large organisation. Payments infrastructure. Multiple systems, multiple stakeholders, a five month window from inception to delivery. We got it live. Troubleshot it, stabilised it, handed it over. That was more than a decade ago and it is still running. Still doing what it was designed to do.
Later, working on product delivery at scale, a product I had helped design and architect went live. Hundreds of thousands of people use it. I could show my son something tangible and explain that what I do manifests in the world. That it is real. That connection between the work and something visible and usable mattered to me in a way that internal milestones never quite did.
Across all of it, the logic was the same. You did the work. You could see what the work produced. The two things were connected and the connection was visible. That clarity produced something specific: satisfaction in the doing, and pride in what remained.
The feedback loop was never static. It was always getting longer.
As a developer, it was hours. Write the program, run it, see it work. The signal came back the same day. Sometimes the same hour.
As a designer, it stretched to weeks and months. Problem defined, solution agreed, delivery landed. Longer to wait for, but when it arrived it was proportionate. The product still running a decade later. The thing in the world I could show someone and say: that came from this work.
As an architect, it extended further. Months of shaping, influencing, holding coherence across a programme before anything was visible. But the outcome, when it came, carried more weight. Broader reach. More people affected. The architecture operating at scale, delivering something that mattered at a level individual designs rarely do.
Each stage stretched the loop and raised the stakes. More responsibility, longer horizon, bigger impact.
And with each stage, the sphere expanded. As an individual contributor, the work was my own. As a designer, I was shaping the direction for a small team or a bounded project. As an architect, I was influencing across larger programmes, bringing coherence to work that spanned multiple teams and multiple timelines. The role shifted from doing to shaping to enabling. From being the one who produced the output to being the one who created the conditions for others to produce it.
The move into leading people takes that expansion further still. The outcomes are now almost entirely mediated through others. Judgment, experience, navigation of the organisation, all of it flows through the people I lead before it reaches any result. The work I do is no longer the work that appears. It is the condition that makes other people’s work possible.
But it changes something fundamental about how achievement feels, and whether it arrives at all. The feedback loop is longer than it has ever been. The outcomes are less direct, more diffused. The connection between effort and visible result is harder to hold than at any previous point in my career. And the question of whether the old signals are still available in any recognisable form is one I am still figuring out.
The end of the year has a particular quality now.
The reflection is part of it. Looking back over twelve months, taking stock of what happened and what did not. But there is something else that sits alongside it. A moment of reckoning that goes beyond review. What did this year amount to. What does the next one need to be. That combination creates a moment of unusual honesty.
And in that moment, a question surfaces that goes beyond what I achieved. It reaches further than that. It asks what I actually am now.
For most of my career that question had a self-evident answer. I was the person who could hold the technical picture. Who could design the solution, shape the architecture, bring coherence to complexity. That was not just a skill. It was an anchor. Something I could stand on when everything else was ambiguous.
That anchor has not gone. The technical depth is still there. The experience is still there. But it is no longer the primary surface of what I do, and the role I occupy now does not have the same legibility. Strategy. Navigation. Enabling. Influencing. These are real. But they do not produce the same clarity of self that a well-designed system or a delivered programme once did.
I help lead a large team. I support with shaping direction and strategy for platforms and programmes that extend well beyond any individual delivery. And as I wrote in an earlier edition, people have become a central dimension of the role. Not a supporting element. A central one. A critical part of what I do now is creating the conditions for my team to do their work, feel their own satisfaction, and achieve their goals.
That is meaningful work. I know it is. But it is also the reason the personal sense of accomplishment becomes harder to locate. It has not disappeared. It has been redistributed. Their wins are real. Their growth is visible. Their sense of achievement is something I can see and take genuine satisfaction in.
What sits alongside all of that is the work that belongs entirely to me but rarely shows up anywhere. Reading the room. Understanding what is actually being asked beneath what is being said. Manoeuvring to get the important things through while letting go of the things that cannot survive the organisation in that moment. Knowing what the right answer is and working out what version of it is actually achievable.
It is not glamorous and it does not produce anything you can point to, but without it little else moves. Learning to count that as work, and to find some measure of satisfaction in doing it well, is something I am still figuring out.
What I am realising at year end is not just the difficulty of articulating achievement. The year was full. The work was real. But what it added up to is harder to hold than it once was. And that is a harder thing to resolve than any technical problem I have faced.
The new sources of satisfaction and identity are there. Finding them requires a different kind of looking.
In a visit to a team based overseas, during a strategy engagement, I noticed someone in the room. Quiet, but not quiet enough to stay invisible. Every time a hard technical question surfaced, the answer came from that person. Not loudly. Just accurately. I pulled them forward. Gave them responsibility for key deliverables. Created the conditions for what was already there to become visible to others.
They grew. Into a technical leader. Delivering outcomes that the organisation continues to benefit from. They would have found their way regardless. What I may have done is shortened the distance.
That moment only becomes visible in reflection. It does not announce itself. But what it points to is something I am only beginning to name. The ability to see people clearly, to read what is there beneath the surface, and to intervene in ways that change the trajectory of a career, of a person, within the microcosm of a large organisation. That is not the same as designing a system or delivering a programme. But it is a form of influence that is entirely my own. And it matters in ways that outlast any architecture.
The second kind is harder still to locate. On a major platform rearchitecture, my role has been to read across the organisation. Understanding the different agendas in play, anticipating what stakeholders need before they articulate it, distilling complexity down to something the team can translate into ground level deliverables that connect to the bigger strategic goal.
The work is real and consequential. Without it the pieces do not connect. But it does not leave a clear residue. What it does leave is something subtler. The realisation that I can hold that kind of complexity, navigate it, and shape it toward an outcome, without it being visible as mine, is itself a form of knowing. A different kind of certainty. Not about systems. About organisations and the people inside them.
Twenty five years in, I am still becoming something.
What I am learning is that the question does not close. The identity keeps moving because the work keeps moving. Each stage asked me to let go of something I had built my sense of self around and find the next thing. It happened with every transition. It is happening now.
I can feel the old anchors loosening and the new ones forming, slowly, in the examples I have described, in the moments of influence that do not announce themselves, in the realisation that what I can see and what I do with what I see is itself a form of expertise.
That is where this sits. Still in the middle of it. Growth does not look the way it used to. It is quieter. Less legible. Harder to point to.
But it is still growth. And I am still moving.
