The Thread

People sometimes ask how someone who trained as an architect ends up working on community resilience, artificial intelligence, energy systems, health, education, governance and rural development. From the outside it can look like a series of unrelated interests. At times I have wondered that myself.

The truth is that I have never experienced them as separate things.

What I have come to realise, particularly over the last ten or fifteen years, is that I am less interested in things than I am in relationships. That may sound obvious, but it has taken me a long time to understand. When I was younger I thought I was interested in architecture. Then I thought I was interested in cities. Later I became fascinated by energy systems, innovation, technology, governance, healthcare and education. Looking back, I can see that I was mistaking the vehicle for the destination. The subjects kept changing because the subjects were never really the point.

The point was always understanding how things fit together.

I grew up in North Wales, a place where communities were still visible enough to understand. People knew each other. Skills, trades, businesses, schools, clubs and families were interconnected in ways that often go unnoticed until they begin to disappear. At the time I did not have the language for it, but I think I was learning something about systems long before I knew the word. I was seeing how places functioned not because of individual buildings or organisations but because of the relationships between them.

Architecture gave me a formal way to explore that instinct. Most people see architecture as the design of buildings. I never really saw it that way. The interesting part was never the building itself. It was understanding how people, movement, technology, culture, economics and environment came together to create a place. A building was simply the point at which all those forces became visible.

Over thirty years at Foster + Partners I was fortunate enough to work on projects at every scale imaginable. Yet the lesson was always remarkably similar. The success of a project rarely depended on the brilliance of any single element. It depended on how well the pieces connected. The architect's role was often less about invention and more about synthesis — bringing together specialists, clients, engineers, planners, users and communities, and creating enough shared understanding that something larger could emerge.

When I left architecture, people often assumed I was changing direction. It never felt like that to me. The subjects changed, but the questions remained the same. How do complex systems work? Why do some places thrive while others struggle? How do ideas move from possibility into reality? How do people become capable together?

The longer I have worked, the less convinced I have become that the answers sit within any single discipline. Many of the most interesting problems exist precisely because they fall between disciplines — in the gaps between professional boundaries, organisational structures and areas of expertise. Most institutions are designed around specialisation. We create experts in healthcare, experts in planning, experts in technology, experts in education. That is entirely sensible and necessary. Yet life does not arrive neatly packaged in that way. Real people experience all of those things simultaneously. Communities experience all of those things simultaneously.

The older I get, the more I find myself drawn towards those intersections.

Perhaps that is why I increasingly think of myself less as a consultant and more as a connector. Not in the networking sense of introducing people to one another, but in the deeper sense of helping people recognise patterns and relationships that may already exist around them. Often the answer to a problem is not the creation of something entirely new. It is seeing an existing connection that nobody has noticed before. A university looking for real-world application. A community looking for expertise. A technology looking for a meaningful use case. A young person looking for confidence. A business looking for purpose. An institution looking for trust.

The individual pieces already exist. The challenge is creating the conditions under which they can reinforce one another.

I think that is one of the reasons I have become so interested in place. There is a tendency, particularly in the technology sector, to view place as becoming less important. We can work anywhere, collaborate globally and access knowledge instantly. All of that is true. Yet my experience has led me to almost the opposite conclusion. Place matters because it is where consequences happen. It is where abstract ideas collide with reality. A national policy becomes a local experience. An AI system becomes a conversation between two people. An energy strategy becomes a household trying to stay warm. A healthcare innovation becomes a patient sitting in a consulting room.

For all our fascination with scale, human beings still experience the world locally.

That realisation has profoundly influenced the work I have become involved with in Dolgellau. Returning felt less like a relocation and more like a return to first principles. Small towns make systems visible. In a large city it is easy to miss the relationships that hold a place together. In a town, you can often see them directly — how schools connect to employers, how voluntary groups support public services, how local businesses influence community confidence, how energy, housing, transport and health all interact. You can also see what happens when those connections weaken.

People occasionally look at Arloesi Dolgellau and see a collection of disconnected projects. There is a makerspace. There is work around energy. There are conversations about healthcare, education, AI, drones, entrepreneurship, storytelling and community development. From a distance it can look slightly chaotic. From the inside it feels remarkably coherent. What we are really exploring is a single question.

What would it take to make a small town more capable?

Not richer necessarily. Not larger. Not more efficient. More capable. Capable of learning. Capable of adapting. Capable of creating opportunity. Capable of supporting its people. Capable of responding to change. The projects themselves are almost secondary. They are experiments through which that larger question can be explored.

In some respects, I think that is why artificial intelligence has become so interesting to me. Many of the current discussions about AI focus on what machines can do — capability, performance, automation. Those are important questions, but I often find myself wondering whether they are the most important ones. The question that interests me is what happens to human capability in response. Does AI make us more curious or less curious? Does it encourage participation or passivity? Does it strengthen communities or weaken them? Does it help us understand one another better, or does it simply allow us to avoid one another more efficiently?

I do not think the answers are predetermined. Technology has never been neutral. Every technology carries assumptions about how people should behave and what society should value. The challenge is not merely building intelligent systems. It is ensuring they support the kind of society we wish to become.

That thought brings me, somewhat unexpectedly, back to where I started. Architecture taught me that successful buildings are rarely about the building itself. They are about what the building makes possible. A good building creates opportunities for interaction, learning, work, reflection, creativity or belonging. Its success is measured not by the object but by the life that unfolds around it. Increasingly I think the same is true of almost everything. Technology. Institutions. Organisations. Even communities.

The real question is not what they are. The real question is what they enable.

And perhaps that is why the idea of the Thread has become so important to me. What began as a visual idea for a logo has gradually become a way of understanding my own work. A thread is a connection between things. It can carry knowledge, memory, relationships and stories. A single thread appears insignificant, yet enough threads woven together create something strong enough to endure. They create fabric. They create structure. They create continuity.

When I look back across architecture, innovation, community development, energy, governance, storytelling and technology, I no longer see a collection of separate careers or projects. I see a continuing attempt to understand how threads are formed, how they are strengthened and how they can be woven together into something useful.

Everything on these pages sits somewhere along that thread. Some ideas are still being explored. Others are already being delivered. Some belong in a notebook of experiments and conversations. Others have become structured programmes, organisations and practical outcomes.

That distinction explains the two expressions of this work. iHuw is where ideas are discovered, explored and shared. It is an invitation to think together. with a W is where those ideas are applied to real-world challenges. It is an offer to work together. They are not separate identities so much as different stages of the same conversation — connected by the same belief: that meaningful progress comes not from isolated expertise, but from creating better connections between people, knowledge, technology and place.

Perhaps that is all I have ever really been doing. Helping people, ideas, places and technologies find better ways to connect.

Everything else seems to have grown from there.