Edition #2: Why Siloed Teams Build Slow

You’re working inside an organisation that’s not moving fast enough.

On paper, everything looks right. Strong talent. Clear roles. Defined KPIs. Everyone is busy. Everyone is delivering.

And yet, progress feels too slow.

Sales is optimising for revenue targets. Product is building against a roadmap that made sense months ago. Operations is focused on efficiency and cost control. Each team is doing its job well. Everyone is hitting their metrics, but the company is still underperforming.

For years, before I ever started building communities, I worked inside organisations going through this — corporates, scale-ups, early-stage startups. Different sizes, different industries, different levels of maturity, all falling into the same pitfall: talented teams with clear KPIs BUT with a lack of shared direction.

Watching this pattern repeat is what ultimately motivated me to focus on building ecosystems where alignment isn’t accidental, but intentional — and to start sharing the lessons behind that work more openly.

Where things start to break down

At first, this doesn’t look like a problem.

It looks like focus. Accountability. Ownership.

But over time, the gaps start to show. Teams solve different problems without a shared understanding of the customer, the company vision, or the trade-offs being made elsewhere. Budgets don’t align with priorities. Deliverables drift. Product–market fit becomes harder to reach, not easier.

What struck me most was how early this happens. Even in small startups — where alignment should be easiest — silos form quickly. Not because people don’t care, but because communication stops being intentional.

And that’s when it became clear: this wasn’t an execution issue.

It was structural.

Organisations were optimised for individual performance, not collective progress. Success was measured team by team, not across the system. Without mechanisms to connect perspectives, information didn’t flow. Learning slowed down. Momentum faded.

No amount of effort fixes that after the fact.

That realisation shaped my career more than any specific role I held. I didn’t want to spend my time patching misalignment later. I wanted to help build environments where alignment is the default.

Why this pattern repeats at ecosystem scale

I saw the same pattern play out not just across teams or companies, but across entire industries, and very clearly across the AI ecosystem in Germany. Joining Merantix felt like recognition: of the problem, and of the work required to move beyond it. Building the Campus became our way of addressing that at ecosystem scale.

The researchers were disconnected from commercialisation, the founders were struggling to navigate regulation, the corporates were unsure how to work with startups, the policymakers lacking real-world feedback…

The same silos, just at ecosystem scale.

In the age of AI, high-quality collaboration is what enables scalable knowledge exchange, faster learning, and real-world impact.

Community-building, for me, became the lever to address that. Not as a social layer, but as infrastructure: creating shared context, shared language, and incentives for collaboration across boundaries.

With the Campus, the last five years have shown that progress is possible. But alignment at ecosystem level requires constant, deliberate effort. The next five years will be just as important.

Why this matters, and what actually helps

Siloed teams don’t just slow execution. They slow learning, and in fast-moving fields like AI, that’s the real bottleneck.

Speed doesn’t come from working harder or shipping faster. It comes from shortening feedback loops: between teams, between disciplines, and between stakeholders. The organisations and ecosystems that move fastest aren’t the most talented ones, they’re the ones where alignment is designed early, communication is structural, and collaboration isn’t left to chance.

This series is my attempt to make those lessons visible, not as theory, but as a practical playbook for how ecosystems, not just teams, can work better. Because when alignment is designed into the system, momentum stops being accidental and progress starts to compound.