Learning How to Learn

Yesterday, I sat down for my first coffee chat of the year as a returning mentor for the New Asia College Mentorship Programme at The Chinese University of Hong Kong. Entering my second year as a mentor, I was eager to meet my mentees, who are bright minds on the cusp of graduating in Financial Technology. Listening to their questions, I could feel the weight of the current graduate market. Shrinking headcounts, fierce competition from returning overseas graduates, and the omnipresent shadow of artificial intelligence have left many students wondering where they actually fit. Yet, as we unpacked their concerns one by one, it became clear that the best antidote to market anxiety is not chasing the latest technical buzzword, but stepping back and thinking from first principles.

Management is often misunderstood as the art of getting people to do what we want. We build organizational structures, establish performance indicators, introduce reporting mechanisms, and hold meetings to ensure that work progresses according to plan. Yet despite these efforts, many organizations continue to struggle with disengagement, misalignment, and inconsistent performance. Perhaps the fundamental problem is not that managers lack sufficient control, but that they have confused control with leadership. Effective management is not about making people work harder. It is about creating the conditions in which people understand what success looks like, recognize when they are making progress, and have the confidence to correct their course when they fall short.

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.