Six years of rooms: what DevOpsDays Zürich taught me about networks
I co-founded Switzerland's first DevOpsDays and ran it for three years. The lasting asset wasn't the event — it was learning how a room turns into a network.
event: DevOpsDays Zürich
Before I founded a company, I helped found a conference. People usually read that backwards: they assume the company came first and the community work was marketing. It was the other way around.
Switzerland’s first DevOpsDays started as a conversation about why there wasn’t one. A few of us had been to the format elsewhere — the open-space model where the agenda gets built on the morning of the day, by the people in the room — and it was obvious that Zürich, with its density of banks, insurers, pharma and a fast-growing cloud scene, should have had one years earlier.
So we built it. Over three years we scaled it past 200 attendees, built the sponsor network from scratch, and held the finances together. Then I stepped back to run my agency instead.
What actually stayed
The obvious output is the event. The real output is three things I still use in every client room.
1. Open space is a scoping technique, not a conference gimmick. Handing the agenda to the room forces you to find out what people actually care about instead of what the organisers assumed. I do the same thing in a discovery workshop now: get the real problems on the wall in the first hour, sequence them with the people who have them, and the project scope writes itself. Most scoping failures are agenda failures — somebody decided in advance what the interesting question was.
2. The sponsor network is a lesson in value exchange. Nobody sponsors a conference because they like you. They sponsor because they’ve calculated that this specific room contains their next customers, hires or partners. Once you understand that, you stop pitching sponsors and start matching them: here is who is in the room, here is why it matters to you, here is what a meaningful presence looks like. That’s identical to how partner and co-sell conversations work today. Vendors don’t buy your platform. They buy access to a room they can’t otherwise enter.
3. Reputation compounds in public, slowly, and then suddenly. For the first year, being one of the DevOpsDays organisers was a curiosity. By the third, it was the reason strangers came to find me at KubeCon. Nobody tracks this while it’s happening. It’s the single highest-leverage thing I did in that decade and it never appeared on a balance sheet.
The part people get wrong
The mistake is treating community as a funnel. If you show up to a meetup with a hiring problem or a pipeline problem, the room can tell, and you get exactly one conversation. The people who actually get value out of these rooms are the ones who arrive with something to give — a connection, a specific answer, a warning about a trap they’ve already walked into.
Six years on, the thing I’m genuinely interested in is how much of the 2015 cloud-native conversation is repeating itself around agents. Same energy, same confusion about what “production-ready” means, same small set of people in every room who actually know. That’s what this site is for — writing down what I hear in those rooms before it evaporates.
If you’re in Zürich and any of that overlaps with your world, the coffee is on me.