< Speaker / Facilitator >
Vihar Parikh
Miro, Omnicom, ShipBob, MIT
Connect in LinkedIn
Vihar has spent more than a decade working on systems that stay coherent while everything around them changes. Document and file systems, then vision and OCR, then big data, now AI. At Miro he leads Custom Solutions and the core navigation experience, Home, Spaces, and Custom Widgets, which is where that tension lives: enough structure to trust the work, enough flexibility to shape it around how you actually work. He lives in Berlin, via NYC and Paris, and runs much of his own week through agents he built himself.
From AI Assisted to AI Native: Rewiring how your teams innovate
17.09
CIC Berlin
< About >
AI made everyone on your team faster. It did not make your team faster.
Productivity went up, but so did the pile of decisions to make and alignment to reach. Individual speed doesn't automatically add up to team speed. The gap shows up in consistent problems: critical context locked up in 1:1 agent chats, misalignment growing with the speed of execution, and decisions that are hard to understand or steer.
Joe and Vihar have lived this at Miro, on two levels: as product leaders running teams, and as builders of AI collaboration tools. They'll share what changed as Miro went agentic, the new problems that emerged, and how they've been tackling the new team bottlenecks: aligned people, shared context, and decisions that move as fast as the agents do.
< Key learnings >
Individual speed doesn't equal team speed. AI can make every person faster and still leave the team stuck — the bottleneck was never how fast one person could move, it's how decisions and context move between people (and now, agents).
The gap shows up in three specific places: context, alignment, and reasoning. Context already didn't always transfer well between individuals; with agents the problem accelerates, since more output means more decisions and decision processes haven't scaled as fast.
"AI-native" isn't about tools, it's a team operating model. Team productivity is locked behind process design: aligning individual acceleration in a shared direction, scaling decision-making and context sharing, and keeping execution legible.
< Tickets >
![](data:image/svg+xml,<svg display="block" role="presentation" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M 0 17.25 L 8.941 23 L 8.941 0 L 0 5.75 Z" fill="rgba(255, 255, 255, 0.65)" height="23px" id="E3vXMlFqc" transform="translate(3 1)" width="8.9412px"/><path d="M 9.5 11.5 L 19 5.75 L 9.5 0 L 0 5.75 Z" fill="rgba(255, 255, 255, 0.65)" height="11.5px" id="ubKUIjrpD" transform="translate(3 12.5)" width="19px"/></svg>)
![](data:image/svg+xml,<svg display="block" role="presentation" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><g d="M 0 24 L 0 0 L 24 0 L 24 24 Z M 4 2 L 21 2 L 21 4.456 L 4 4.456 Z M 4 10.958 L 21 10.958 L 21 22 L 12.498 17.086 L 4 22 Z M 4 6.479 L 21 6.479 L 21 8.935 L 4 8.935 Z" fill="transparent" height="24px" id="kThX1iq6q" width="24px"><path d="M 0 24 L 0 0 L 24 0 L 24 24 Z" fill="transparent" height="24px" id="GNyBoqnEA" width="24px"/><path d="M 0 0 L 17 0 L 17 2.456 L 0 2.456 Z M 0 8.958 L 17 8.958 L 17 20 L 8.498 15.086 L 0 20 Z M 0 4.479 L 17 4.479 L 17 6.935 L 0 6.935 Z" fill="rgb(255, 255, 255)" height="20px" id="eMN6AGLsh" transform="translate(4 2)" width="17px"/></g></svg>)
