Running an innovation workshop with a distributed team

Remote workshops don't fail because of Zoom. They fail because someone took an in-person format, moved it online, and called it remote-ready. The result: two hours of everyone staring at a screen, someone's mic cutting out, and a Miro board nobody uses after the call.

What's actually different online

In person, energy is contagious. Someone has a breakthrough and the room feels it. Online, that energy doesn't travel. Engagement is invisible until it collapses. This changes how you need to design the session.

• Shorter sessions with more breaks — 90 minutes max before a pause.
• Smaller breakout groups — four to five people, not eight.
• Tools that force participation, not just whiteboards people can ignore.
• More aggressive time-boxing — without physical cues, groups lose track of pace.
• A stronger pre-session brief — remote participants need more context before the day, not during it.

What doesn't change

The fundamentals of good facilitation don't change online — they just require more intentional design. A clear problem statement. Cross-functional teams. Time pressure. A structured output. These work in any medium.

Hybrid is the hardest format

Pure remote is manageable. Pure in-person is ideal. Hybrid — some people in a room, some on a screen — is genuinely difficult. The in-room group has a natural advantage: shared energy, casual asides, visual cues. If you're running hybrid, design explicitly for it: breakout groups should be fully remote or fully in-person, never split.

When to go in-person anyway

“Some conversations are technically possible remote. They're just substantially worse.”

Anything that requires emotional honesty — culture conversations, conflict resolution, leadership alignment — is better in person. The friction of travel pays for itself in depth of conversation. Save the remote format for structured sprints on well-defined problems where the output is a deliverable, not a breakthrough.

Making it work

Test the tech the day before. Assign a dedicated technical host who isn't also facilitating. Use polls or async tools the evening before to surface context. Keep breakout groups small and time-boxed. End with every participant sharing one concrete commitment out loud.