For years, I’ve watched the “shiny” version of digital transformation from the C-suite - the one with the slick slide decks and the promises of seamless integration. But behind that veneer, there is almost always a Shadow System. It’s a parallel, multi-trillion economy built on our structural failures, operating with the ruthless precision of a global corporation.

I wrote my third book, “The Shadow System,” because the prevailing narrative - that we’re engaged in an unwinnable war of endless, defensive patching - is a lie. We aren’t failing because of a lack of effort; we are failing because of a structural conflict of interest where profit and political control depend on insecurity.

Here is how the first chapter sets the stage for what I call the Unbearable Asymmetry.

From Reactive Victim to Active Builder

This isn’t just a technical problem; it’s a strategic mandate for systemic change. For too long, we have relied on a reactive mindset and a “fortress model” of security, chasing the impossible ideal of total prevention.

The success of the Shadow System isn’t due to the adversary’s brilliance, but rather our own Unbearable Asymmetry: our technical systems operate at the speed of light, yet they are defended by human processes moving at the speed of bureaucracy.

The Question: Does your organisation operate at the speed of the threat, or at the speed of bureaucracy? Is your “official” system actually just a series of shadows and workarounds?

I’d love to hear your thoughts in the comments. We can’t fix the architecture until we acknowledge the gaps.

If you’re ready to move beyond defensive patching and embrace a Moral Architecture, Book 3: The Shadow System is available now.

Buy on Amazon

I wrote my first book, “The Next Evolution,” because I’m tired of seeing us treat the future like something that just happens to us. We’ve become passive users of systems we don’t understand, guided by “Whispering Systems” that nudge our behaviour in ways we haven’t consented to.

If we want to reclaim our agency, we have to move from being system users to being System Shapers.

Here is a look at the “Manifesto” that started it all in Chapter 1.

Excerpt: The Next Evolution Manifesto

We are no longer transforming technology; it is transforming us. The question is no longer can we?, but should we? Not what is possible?, but what is right?

In a world of disappearing interfaces, algorithmic judgment, and systemic inequality, we choose:

• To build systems that serve people, not just users, but citizens, families, futures.

• To reject digital paternalism and embrace dignity by design.

• To prioritise ethics, responsibility, and sustainability as the operating system of progress. Not constraints, but foundations.

This is a call to shape technology with a human centre, not a corporate one, to resist narratives that reduce us to users, profiles, or data points, and to move from admiration of change to stewardship of its direction.”

The “System Shaper” Mindset

This manifesto was the catalyst for the entire series. It’s why I’m so vocal about the “Ethical CTO” role. As leaders, we aren’t just managing servers or code; we are managing the “Trust Infrastructure” of society.

When I talk about “Designing the Future,” I’m talking about taking a beat to look at the moral boundaries of our innovations. Are we building something that adds to the “planetary cost,” or are we building something that allows for genuine human flourishing?

The Question: In your world, do you feel like a System User or a System Shaper? Have we reached a point where the world has outrun its builders?

Drop a comment below. I’d love to hear if this manifesto resonates with the challenges you’re facing in your own “Three-Foot World.”

If you’re ready to stop reacting and start designing, you can find the full version of The Next Evolution available on Amazon.

Buy on Amazon

When I sat down to write The Cognitive Crucible, I wanted to move beyond the surface-level complaints about “distraction.” We aren’t just distracted; we are operating within an environment that pushes our biological hardware past its breaking point.

In Chapter 1, I explore the fundamental architecture of our minds to uncover why our “always-on” world is so debilitating. It isn’t a personal failing of willpower, it is a conflict between our ancient wiring and modern design.

Below is an excerpt from the opening chapter.

Excerpt: The Bustling Control Centre

“Imagine your brain as a bustling control centre, constantly bombarded by a dizzying flood of information. Sounds from the street, the hum of your computer, the feel of your clothes, and countless thoughts swirl in your head – an overwhelming amount of data that you could never consciously process at once.

This is where attention, or “spotlight”, comes in, your brain’s remarkable, yet inherently limited superpower. At any given moment, this spotlight can only illuminate a few things brightly.

Too much input can cause our ability to think clearly, remember, or make sound decisions to falter – a phenomenon known as “cognitive load”. In our always-on world, it’s a deeply counterintuitive idea that our brains weren’t built for constant, fragmented stimulation.

We’ll examine the phenomenon of cognitive load and see how every stray notification, open tab, and unfinished thought exacts a measurable toll on our mental energy. By understanding the fragility of our focus, we begin to grasp the true cost of a distracted world.”

Why this matters for the “Ethical CTO”

This foundational concept of Cognitive Load is the missing link in how we design systems and lead teams. As technical leaders, we often focus on the “throughput” of our software, but we ignore the throughput of the humans operating it.

If we build systems that treat human attention as an infinite resource, we are designing for failure. We are creating “Cognitive Debt” that eventually leads to burnout, errors, and a total erosion of agency.

The Discussion: I mention in the chapter that the “feeling of mental exhaustion at the end of a long, distracted day isn’t a sign of hard work; it’s the feeling of a finite system being pushed past its limits”.

As a leader or a creator, have you noticed your team’s “Cognitive Load” reaching a breaking point? How much of that is due to the tools we’ve asked them to use?

I’ll be in the comments all day to discuss the “Architecture of Choice” and how we can start designing for sovereignty rather than submission.

If you want to dive deeper into the neurological consequences of attention fatigue, my book The Cognitive Crucible is available now on Amazon.

Buy on Amazon