Mariusz Gil's wroclove.rb 2022 talk. Not an introduction to EventStorming itself but a reflection on moving the technique online after the March 2020 lockdown. Briefly defines EventStorming as a way to discuss software by identifying domain events, triggers, consequences, conditions, and all-or-nothing islands, and shows how combined with DDD it leads to aggregates, acceptance criteria, and even object design. Recounts the first pandemic workshop as a disaster: people muted, no body language, no group switching, no engagement, and the 'remote EventStorming' chapter of Brandolini's book is 'intentionally left blank'. Frames constraints as learning opportunities (forget ORM, forget state, avoid if) and surveys remote improvements: the 'online whiteboard' trend (Miro), new features making tools usable, unlimited visual expression, inviting remote domain experts, iterative plan–work–rethink cycles, and adding fun/visual metaphors. Offers advice: master your tools (Miro + Zoom is his go-to set), keep the toolset small to avoid overwhelming non-technical people, have backup plans for everything (network, audio, power, data-location constraints), plan the split/merge structure carefully, and expect the unexpected. Concludes that remote is both good and bad — online can beat offline for detailed convergent modeling but not for large (30-person) exploratory sessions.