Sync-heavy rituals in a typical sprint can consume over 20% of an engineer's time, leading to meeting fatigue and constant context switching.
Applying a manager's fragmented schedule to makers who need long, uninterrupted blocks of time for deep work significantly harms productivity and flow state.
Before transitioning to async, evaluate if your company culture is flexible, if the team is educated on the right tools, and if the squad profile is suitable for the change.
To maximize the maker schedule, an experiment was conducted to completely eliminate all synchronous sprint rituals and force an async-first mindset.
The new async system relied on specific tools for messaging and task management, redesigned rituals like async dailies, and behavioral changes like prioritizing public communication.
The extreme async experiment boosted focus and productivity but also created negative side effects like endless message threads, team isolation, and superficial retrospectives.
A middle path was found by being intentional with sync time, introducing a five-message rule to trigger a call, and using hybrid models for peer reviews and retrospectives.
To implement async practices successfully, start by assessing your foundations, coordinating the rules of engagement with the team, and documenting key processes.
Track the success of an async transition by monitoring key metrics like ENPS, ticket velocity, and "boomerang work," while gathering qualitative feedback in one-on-ones.
Asynchronous models are most effective for internal teams across different time zones but require ongoing managerial oversight to maintain productivity and address issues.
Jobs that call for the skills explored in this talk.