Remote Agile Teams Fail at the Informal Layer, Not the Ceremony Layer
When agile teams moved to remote work, the common concern was whether the ceremonies would survive the transition. Would sprint planning work over video? Could retrospectives produce candor without physical presence? Would the daily standup maintain its discipline when the team was distributed across time zones?
These concerns were largely misplaced. The ceremonies adapted. Video-based sprint planning, while less fluid than in-person, functions well enough with the right tools and facilitation. Retrospectives can produce genuine reflection in a distributed format when psychological safety exists. The ceremonies are the visible, scheduled, facilitated parts of team collaboration, and they proved more portable than expected.
What remote teams consistently struggle with is the informal layer — the conversations that happen between ceremonies and that, in office environments, happen without coordination. The question asked in passing at someone’s desk. The quick alignment between two developers before a decision gets made. The ambient awareness of what the rest of the team is working on, absorbed through proximity rather than through any formal communication channel. These interactions are the connective tissue of a functioning team, and they do not migrate to video calls naturally.
Teams that have built effective remote collaboration have done so by deliberately creating substitute structures for the informal layer. Short asynchronous video updates that preserve tone and context better than text. Dedicated channels for in-progress work where team members share blockers and progress without waiting for the standup. Pair programming sessions that create the incidental communication that colocation provided. None of these perfectly replicate the informal collaboration of shared physical space. They approximate it well enough to maintain team cohesion.
The underlying principle is that remote work does not make the informal layer less important — it makes it invisible unless you deliberately design for it. Teams that run the ceremonies and treat everything else as the team’s personal responsibility to manage tend to develop the coordination failures that give distributed teams a bad reputation. The ceremonies are necessary but not sufficient. The informal layer is where the team actually operates.