Edition #4: Designing for Autonomy

When we started building the Merantix AI Campus, we were a very small team (7 people in a Zoom call, to be exact). I was the first full-time employee, supported by a rotating intern, and together we were trying to bring a very ambitious vision to life.

In the early days, almost everything required direct involvement. We invested significant time in every new member joining the Campus, facilitated introductions, organised and executed events ourselves, and continuously surfaced what was happening across the community to encourage participation and make people feel part of something larger than themselves.

This work still exists today, however, what changed is that the ecosystem no longer depends exclusively on us to create momentum.

And none of this was accidental. We knew that ecosystems do not become active on their own. In the beginning, momentum has to be created deliberately and led by example.

But we also knew something else: if the ecosystem continued to depend on us for every introduction, every event, and every exchange of knowledge, it would never scale.

The challenge was never simply building a community. The challenge was designing a system that could eventually operate without us sitting at the centre of every interaction.

Ownership Before Scale

One of the principles we established very early was that the Campus should never feel like a service being delivered to its members.

From day one, we wanted residents to think of themselves as contributors rather than consumers. During onboarding, we talked about values, participation, and ownership just as much as we talked about practicalities.

We gave members unlimited access to our event spaces. We encouraged them to host workshops, invite experts, organise discussions, and share their knowledge with others. The message was always the same: this is your community as much as it is ours.

That mindset became incredibly important later. Before people can take ownership of a system, they first need to believe they have permission and a sense of ownership to shape it.

Why Participation Comes Before Optimisation

Looking back, some of the early activities we hosted would probably not pass today's quality threshold. But that was part of the process. In those early years, we needed to say yes to many ideas, experiment with different formats, and learn what actually created value for the community.

And that was okay.

We were never careless about curation. In fact, curation was one of the foundations of the Campus from the very beginning, as I explored in the first edition of this playbook. We were highly intentional about who joined the community and the values they brought with them.

What we were intentionally generous about was participation.

In the early stages, the goal was not to optimise every interaction. The goal was to create enough momentum for people to develop habits of contribution, knowledge sharing, and peer-to-peer engagement.

Only once that energy existed could we begin refining where it was most valuable.

The Shift From Activity to Signal

As the community matured, our role started to change.

The question was no longer how to create activity. Activity was already happening. The question became how to increase relevance.

Over time, we noticed certain patterns emerging naturally. Technical leaders wanted deeper conversations with peers facing similar challenges. Researchers wanted spaces to discuss developments at the frontier. Operators wanted trusted environments where they could exchange lessons learned without turning every interaction into a networking exercise.

That is when many of our subcommunities began to take shape.

Our CTO roundtables, research circles, technical workshops, and other highly curated formats were not created because we needed more programming. They were created because we could see where meaningful exchange was already happening and wanted to strengthen it.

Our role shifted from generating activity to designing infrastructure around it.

The Real Goal of Ecosystem Building

I often think the success of an ecosystem is measured using the wrong metrics.

People count events, memberships, partnerships, or visitors.

But the strongest signal is something much simpler: it is when valuable things happen without you.

A founder organises a workshop addressing problems that other residents are currently tackling. A researcher starts a paper reading group. An investor makes an introduction. A startup finds a client or a new hire. A community member creates value for someone else without needing permission, coordination, or intervention from the ecosystem team.

Those moments signal that the system is no longer relying on its operators to create momentum.

It is generating momentum on its own.

And ultimately, that is the goal. Not to sit at the centre of every connection, but to create an environment where the community becomes capable of carrying the ecosystem forward itself.