Advertise on podcast: Continuous improvement

The greatest obstacle to successful technology strategy is rarely a lack of effort, resources, or execution. More often, it is our inability to question the assumptions and mental models that guide our decisions.

One day, I will become a father. Somewhere in the future, a little girl whom I have not yet met will enter my life and change it in ways I can barely imagine. I feel an extraordinary mixture of excitement, anticipation, responsibility, and quiet anxiety. I wonder what she will look like, whose smile she will inherit, and what kind of person she will eventually become. Yet, beneath all these questions lies one that occupies my thoughts more than any other: Will I be able to give her the emotional security she needs to grow into a confident, compassionate, and resilient human being?

The most consequential change in enterprise AI begins when a system stops suggesting what someone should do and starts doing it on their behalf. A flawed answer can mislead a reader. A flawed action can alter a customer record, disclose confidential information, or create a commitment the enterprise must honour. Moving from assistance to agency changes the architecture of responsibility.

An Enterprise Architect's perspective on six connected choices that turn technology investment into customer outcomes, stronger economics, and lasting capability.

We live in a world that celebrates knowledge, yet rarely questions how knowledge is acquired. From childhood, we are taught to accumulate information, memorize facts, pass examinations, and demonstrate competence. As professionals, we continue this pattern by attending training courses, collecting certifications, reading books, and mastering new technologies. We often measure our intellectual progress by how much we know rather than how effectively we learn. Yet there is a fundamental difference between acquiring knowledge and developing the capacity to learn. The former expands what we know today; the latter determines how well we can navigate what we do not yet know tomorrow.

My dear future child, I am writing this before I know who you will become. I do not yet know the sound of your voice, the things that will make you laugh, or the dreams you will one day carry quietly inside you. I do not know what you will be good at, what will frighten you, whom you will love, or where life will eventually take you.

Anger rarely asks for permission. A careless remark, a disrespectful colleague, an unreasonable demand, or a stranger who behaves as though no one else exists can alter our internal state in a matter of seconds. The event itself may be brief, but the mind is remarkably skilled at extending its life. We replay the conversation, reconstruct the tone, imagine what we should have said, and continue arguing long after the other person has moved on. What lasted a moment in reality can occupy hours in the mind.

Enterprise Architects are trained to think in systems. We map capabilities, applications, information flows, integrations, technology platforms, dependencies, risks, and target states. We learn to describe complexity and to design pathways from the current state toward a more intentional future. Yet some of the hardest architectural problems have surprisingly little to do with technology.

Enterprise Architecture is often described as the discipline of understanding an organisation from the inside out: its business capabilities, processes, applications, data, technology, governance, and operating models. We create architecture principles, reference architectures, roadmaps, standards, and technology strategies. We map the enterprise in increasingly sophisticated ways.

Enterprise Architecture has traditionally been associated with the internal structure of an organization. We map applications, rationalize technology portfolios, define data models, establish standards, and design target architectures. These activities are necessary. But they can also create a dangerous illusion: that if we understand the inside of the enterprise well enough, we understand the enterprise itself.

In asset management, we often talk about the “plumbing” of finance. As an Enterprise Architect, my role is to design, connect, and fortify that plumbing. For decades, investment firms have invested heavily in systems of record for transactions, portfolio accounting, market data, performance, and financial risk. Yet the transition toward a net-zero economy is exposing a new architectural challenge: climate data does not naturally fit into the traditional investment technology landscape.

In alternative investments, climate change is increasingly moving from the sustainability function into the investment committee. Private equity, private debt, real estate, and infrastructure investors are discovering that climate risk is not simply a reporting obligation or an ESG consideration. It can directly affect cash flows, capital expenditure, financing costs, debt capacity, terminal value, and ultimately investment returns.

The investment management industry is facing a fundamental architectural challenge. For years, environmental, social, and governance (ESG) factors have often been treated as overlays—separate datasets acquired from external vendors, stored in specialized platforms, and consulted by investment teams when required. But this architecture increasingly conflicts with the economic reality of climate change.

The early years of sustainable finance were largely defined by exclusion. If a company operated in a high-carbon sector, portfolio managers could apply a screening rule, remove the security from the investable universe, and move on. From an architecture perspective, this was relatively straightforward: define a rule, encode it into the compliance engine, and filter the portfolio.

The transition to a net-zero economy is no longer a peripheral ESG initiative. It is an economy-wide structural transformation that is changing the assumptions underpinning investment, risk management, valuation, and capital allocation. Climate change is increasingly moving from the sustainability function into the core architecture of financial institutions.