Organization of the Future: Simulating the AI-Native Teams Workshop

Agent-Driven Meetup Prague

Hosted by Ataccama // Karlín, Prague 8

Agent-Driven Meetup Prague: Build Like a POD — Simulating the AI-Native Development Team

Your org chart is killing your agents. Join us to run a live simulation of POD-based teams making decisions with AI agents — not talking about it.

This Is Agent-Driven Meetup Prague.

If you've been here before, you know what this is: no bullshit theory, no vendor pitches, no "AI is going to change everything" presentations. We build things, we break things, we figure out what actually works when you put agents into production in real organizations.
This edition goes one level up from the code. Not how to build agents — how to build the teams that operate them.
Because here's the thing nobody is saying out loud at these meetups: the agents are fine. The organizational structure around them is broken.

The Real Problem We Keep Not Solving

Every team at every meetup we've run is using agents the same way. One developer has a Claude window open. Another has Cursor. Someone on Slack posted a prompt they found useful. There's no shared context, no shared role assignment, no way for the agents to be collectively accountable to the team's actual goals.
You're running 21st-century AI on a 20th-century org chart.
The org chart was designed for predictable, repeatable, decomposable work — industrial-era assumptions baked into every hierarchy, every feature team, every sprint board. It doesn't know what to do with agents because agents aren't tasks. They're capable entities. They need roles. They need context. They need to fit into a structure that was designed to hold them.
Dave Gray figured this out in 2012, before agents existed.

He called it the Connected Company. The core unit is a POD — a small, autonomous, cross-functional team with everything it needs to serve its customer independently, connecting to other PODs through explicit interfaces rather than management layers.

What Actually Happens at This Meetup

You walk in. You get assigned to a POD.
Each POD is a cross-functional unit inside NovaTech — a fictional (but uncomfortably familiar) Czech B2B SaaS company that is mid-transformation from a traditional hierarchy into a connected, POD-based structure. Product PODs. Revenue PODs. Infrastructure PODs. Customer Success PODs. Each with a challenge scoped to their function.
The company faces one decision: should NovaTech launch in Germany in Q3?
No POD has the full picture. The Product POD knows what the roadmap costs. The Revenue POD has deals on the table. The Infrastructure POD has a data residency timeline. The Customer Success POD knows what they can't support. The decision is genuinely hard. The PODs have to figure it out together — without a manager breaking the tie.
Your POD gets an AI agent. Not a tool. A team member with a role you define, a name you give it, a brief you write. Research Analyst. Technical Due Diligence Analyst. Revenue Strategist. You decide. You brief it. You work with what it gives you.
You have 45 minutes. Then all PODs assemble for the Company Council — the Connected Company's answer to a board meeting, except there's no board. Just PODs, with their recommendations, their conflicts, and the requirement to reach a collective position without anyone having authority to overrule anyone else.
That part is the hard part. It's supposed to be.
Afterwards, we debrief. What did the POD structure change about how you worked? What did you do with your agent that you hadn't done before? Where did the Company Council break down — and why? These aren't hypothetical questions after this exercise. They're questions you just lived the answer to.

Why This Is the Right Conversation for This Community

We've spent the last several meetups on the technical layer: orchestration, multi-agent coordination, memory and context manag