> Markdown version of [/videos/2089-the-async-revolution-balancing-focus-alignment-and-agility](https://www.wearedevelopers.com/videos/2089-the-async-revolution-balancing-focus-alignment-and-agility). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # The Async Revolution: Balancing Focus, Alignment, and Agility Gabriel Cazals reveals why cancelling all meetings won't fix your engineering velocity. Learn how RocketChat found the perfect async-first middle path to protect deep work and team alignment. - **Speakers:** [Gabriel Casals](https://www.wearedevelopers.com/@gabriel-casals) - **Event:** World Congress 2026 Europe - Virtual Stage - **Published:** July 2, 2026 - **Duration:** 35:16 - **URL:** https://www.wearedevelopers.com/videos/2089-the-async-revolution-balancing-focus-alignment-and-agility ## Summary In many remote and hybrid environments, companies unintentionally impose a highly fragmented "manager's schedule" onto engineers and creatives who desperately need continuous blocks of "maker's time." Synchronous-heavy Agile rituals—planning, daily standups, and retrospectives—often consume up to 20% of a sprint, forcing constant context-switching that destroys focus. Recognizing this massive drain on productivity and morale, Gabriel Cazals details an experiment at RocketChat to radically shift engineering squads from synchronous dependency to an asynchronous-first mindset, prioritizing deep work and continuous value delivery. The initial approach involved an extreme pivot: eliminating all synchronous meetings to force asynchronous collaboration through tools like Jira, digital documentation, and messaging. While this boosted overall delivery and improved team satisfaction, it also triggered new problems—endless chat threads, feelings of isolation among remote developers, and superficial retrospective feedback. To correct these outcomes, the team developed a "middle path" that balanced deep individual work with intentional syncing. Strategies included synchronous peer reviews to combat junior developer isolation, hybrid retrospectives where feedback was gathered asynchronously but discussed live, and shifting weekly planning check-ins from rote task-reporting to defining broader success criteria for the sprint. Successfully transitioning to this async-first model requires careful cultural assessment and explicit alignment—a concept of "coordinate before you cooperate." A crucial mechanism introduced was the "five-message rule": if a text thread requires more than five exchanges to resolve an issue, the team immediately jumps on a brief live call to prevent messaging fatigue. Leaders mapping this transition should avoid sudden, extreme mandates and instead focus on incremental adjustments. By monitoring key metrics like ticket closure rates, boomerang work (endless review cycles), and eNPS, teams can continuously fine-tune their team rituals to protect flow states and prioritize high-value problem-solving. **Keywords:** maker versus manager schedule, asynchronous collaboration strategies, remote-first team productivity, context switching costs, sync-heavy agile rituals, async daily standups, hybrid agile retrospectives, five-message communication rule, developer flow state, async peer reviews, meeting fatigue reduction, boomerang work items, cross-time zone collaboration, enps tracking, jira task management ## Chapters 1. **Time cost of standard agile meetings** (00:03) — How default sync-heavy rituals consume an outsized portion of sprint capacity. 1. **Friction in maker versus manager scheduling systems** (03:48) — The productivity loss caused when fragmented manager schedules are imposed on creative problem solvers. 1. **The hidden productivity toll of context switching** (06:01) — How a single scheduled meeting disrupts deep analysis workflows and forces engineers to spend hours regaining their flow states. 1. **Cultural and technical prerequisites for asynchronous work** (08:58) — Gauging company readiness, team maturity, and tool familiarity before overhauling communication protocols. 1. **Radical experiments wiping out all synchronous team rituals** (10:46) — Replacing all live sprint interactions with message threads and collaborative documents to maximize maker time. 1. **Evaluating the impact of an extreme asynchronous experiment** (15:53) — Identifying the productivity gains alongside the pitfalls of employee isolation, thread bloat, and overly prescriptive planning. 1. **Establishing a middle path with intentional hybrid rituals** (20:05) — Implementing protocols like a five-message limit and synchronous peer reviews to balance deep work with team connection. 1. **Step-by-step implementation framework for asynchronous rituals** (25:18) — Executing team trial runs using cross-functional kickoffs, documented expectations, and continuous metric tracking. 1. **Identifying optimal environments for asynchronous communication rollout** (29:18) — Why internal workflows and distributed time zones adapt much faster to async routines than client-facing teams do. ## Related Moments - [Evaluating remote collaboration styles and deep work preferences](https://www.wearedevelopers.com/videos/1804-neuroinclusion-the-future-of-work-starts-in-your-meeting-room) (from "Neuroinclusion: The Future of Work Starts in Your Meeting Room") - [Fostering a culture of flexible communication and collaboration](https://www.wearedevelopers.com/videos/508-how-to-make-a-4-day-week-work-for-everyone) (from "How to make a 4 day week work for everyone") - [Shifting management focus from physical presence to performance outcomes](https://www.wearedevelopers.com/videos/1808-the-future-of-employee-wellbeing-benefits-trust-performance) (from "The Future of Employee Wellbeing: Benefits, Trust & Performance") - [Structuring daily synchronous cycles for remote engineering teams](https://www.wearedevelopers.com/videos/200-agile-work-at-cariad-creating-a-customer-web-application-for-controlling-the-vehicle) (from "Agile work at CARIAD – Creating a customer web application for controlling the vehicle ") - [Managing flexible routines and asynchronous communication](https://www.wearedevelopers.com/videos/551-fireside-chat-with-lea) (from "Fireside Chat with Lea") - [Wasting sprint capacity on overarching team synchronization and alignment](https://www.wearedevelopers.com/videos/1648-how-to-sabotage-your-software-development-with-agile-10-pro-tips-for-guaranteed-success) (from "How to sabotage your software development with agile? – 10 pro tips for guaranteed success ") ## Related Articles - [Remote, Hybrid, or In-Office: What’s Really Best for Developers?](https://www.wearedevelopers.com/magazine/638-remote-hybrid-or-in-office-what-s-really-best-for-developers) - [Mastering Remote Work: Tips for Developers](https://www.wearedevelopers.com/magazine/558-mastering-remote-work-tips-for-developers) - [Stop Wasting Time: How to Lead a Stand-Up Meeting & Get Results](https://www.wearedevelopers.com/magazine/414-stop-wasting-time-how-to-lead-a-stand-up-meeting-get-results) - [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding) ## Related Jobs - [Agile Full Stack Engineer](https://www.wearedevelopers.com/jobs/48325-agile-full-stack-engineer) at **synava GmbH** - [Mid/Senior Full-Stack Engineer (Web-first)](https://www.wearedevelopers.com/jobs/ext/1210833-mid-senior-full-stack-engineer-web-first) at **SMG Swiss Marketplace Group** - [Engineering Manager (Fusion Experience)](https://www.wearedevelopers.com/jobs/ext/1669281-engineering-manager-fusion-experience) at **Bitpanda** - [Principal Product Manager, Agent Platform](https://www.wearedevelopers.com/jobs/ext/277541-principal-product-manager-agent-platform) at **GitHub** - [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx** - [Manager, Technical Support](https://www.wearedevelopers.com/jobs/ext/116302-manager-technical-support) at **Twilio**