The Zoom face and the DM truth almost never match.
On the call, nine heads nod. The PM closes with "great, everyone aligned?" and the gallery view answers "yep, sounds good." The call ends three minutes early. Productivity!
Then the DMs start. "Did we actually agree to that timeline?" "I don't think she heard my point." "We're going to regret that vendor." Within an hour, the version of the plan circulating in side channels is a different plan from the one anyone agreed to on camera.
This is standup theatre. The on-camera meeting is a performance of alignment. The real meeting happens after, in fragments, across DMs and one-on-ones and side Slack threads. Distributed teams generate enormous quantities of this hidden conversation, and most of it never gets back to the people who needed to hear it.
The Meeting After the Meeting
Meinecke and Handke coined a useful frame: the post-meeting talk. In their 2023 model, formal meetings are only part of the sensemaking process. After the meeting ends, participants debrief in hallway conversations, one-on-ones, and increasingly in DMs (Meinecke & Handke, Organizational Psychology Review, 2023). That is where dissent gets voiced and where the real decisions about how the team will act often crystallize.
In an office, those debriefs were lossy but visible. You could walk past two teammates by the coffee machine and pick up that the engineering lead was furious about the roadmap. Distributed teams lost that signal entirely. The post-meeting talk did not disappear. It moved into private channels, where the people who needed to act on it cannot see it.
Why the Performance Happens
Four forces stack to produce standup theatre. None of them are about bad people. They are structural pressures that show up reliably in remote and hybrid work.
1. Hierarchy fear and the MUM effect
Rosen and Tesser coined "MUM" (minimize unpleasant messages) in the 1970s. Decades of research confirm that subordinates systematically delay, distort, or delegate bad news upward (Lee, 1993). In-person, MUM is bad enough. On camera, with a recording running and your name on screen, it gets worse.
Irving Janis's groupthink work named the related symptom: self-censorship. People in cohesive groups silence their own doubts and then assume the silence around them means everyone else agrees (Harvey's Abilene Paradox is the cousin: groups take actions no individual member actually wants). The "yep, sounds good" chorus on a Zoom call is the textbook form.
2. Video makes everything performative
Jeremy Bailenson's Stanford VHIL group identified four mechanisms that make video calls cognitively and socially exhausting: hyper-gaze (everyone seems to be staring at you), mirror anxiety (watching your own face), physical constraint, and the cognitive load of monitoring nonverbal cues you can barely see (Bailenson, Technology, Mind & Behavior, 2021). Video conversation is performance by default. Disagreement, which already costs more than agreement, costs more on camera.
3. Time pressure and the superfluous-meeting tax
Atlassian's 2024 State of Teams research found that distributed knowledge workers spend roughly 50% more time in meetings they consider unnecessary than they did pre-pandemic. In a parallel internal experiment, Atlassians who replaced standups with Loom videos freed about 5,000 hours of focus time over two weeks (Atlassian, 2024). Most distributed meetings are running tight, with too much to cover and too little time to handle dissent. People take the shortcut: nod, close the call, debrief in DMs.
4. Async/sync mismatch
Long-range research on remote work found that distributed work shrank cross-group collaboration time by about 25%, weak-tie connections by 32%, and the bridging-tie collaboration that surfaces dissent across silos by 41% (Yang et al., Nature Human Behaviour, 2022). Slack's Fall 2024 Workforce Index added that 48% of desk workers were uncomfortable telling their manager about even routine AI use (Slack, 2024). When the easiest thing to share upward is good news, you get theater.
Then there is the productivity-paranoia gap. Microsoft's 2022 WTI found 85% of leaders struggling to trust hybrid employees were productive, while 87% of employees said they were. Trust gaps were sharper for managers of hybrid teams (49% versus 36% for in-person managers) (Microsoft WTI, 2022). When trust is low, meetings become auditions, and auditions reward visible confidence over honest disagreement.
Rituals That Surface Real Disagreement
More meetings and more cameras will not fix this. Rituals that make dissent legible inside the meeting itself will. Five worth borrowing.
Pre-reads, with silent review
Amazon's six-pager is the canonical version. Jeff Bezos described the reasoning bluntly: "You can hide a lot of sloppy thinking behind bullet points." Meetings start with twenty minutes of silent reading. By the time anyone speaks, everyone has metabolized the same material at their own pace (CNBC, 2018). The discussion can skip context and go straight to disagreement.
Distributed teams can scale this down. A two-page brief, shared 24 hours before the meeting, with a comment thread for written objections. The meeting is for resolving what could not be resolved in writing.
Written dissent prompts
GitLab's all-remote handbook treats written communication as the default and chat as a fallback. Standups happen in a dedicated channel, async, with a template that explicitly invites blockers and disagreement (GitLab Handbook). Automattic does something similar with its P2 internal blogs, which carry roughly a thousand posts and comments a day across a company of thousands (Automattic, 2020). Dissent has a venue, a format, and a record.
You can read more on how to structure this without drowning the team in async-first communication guides for remote teams.
Rotating devil's advocate
Schweiger and Schwenk's 1989 work in the Academy of Management Journal compared devil's advocacy and dialectical inquiry against simple consensus discussion. Both adversarial methods produced measurably higher-quality decisions, and also lower satisfaction with the process (Schweiger, Sandberg, & Ragan, AMJ, 1989). The tradeoff is real. Rotate the role explicitly. The point is to make dissent role-based, not person-based, so nobody pays the social cost of being the team's permanent dissenter.
Pre-mortems
Gary Klein's pre-mortem: before launch, imagine the project has already failed and write out why. Kahneman called it one of the most valuable decision techniques he had encountered (Klein, HBR, 2007). Pre-mortems work well in distributed contexts because the writing happens async. People put failure modes in a doc instead of voicing them on camera, and the doc becomes a shared register of concerns the team agreed to track.
Structured anonymous concerns
Useful, with a caveat. Goffman's frontstage/backstage frame is worth carrying: written async channels give people more editing power, not less. Anonymous concerns surface things people would not say on camera, but they can become another backstage that displaces the conversation rather than feeding it forward. They work when they have a clear cadence, an owner, and a public follow-up. They fail when they are a venting box leadership reads occasionally.
The Counter-Arguments
Three are worth taking seriously.
"Async standups break closely coupled teams." The argument from Range, LogRocket, and others is that the synchronous touchpoint is the morale glue: if your standup can be async, it was already ineffective, and writing it down just buries it. There is something to this. Closely coupled teams in active incident response or tight integration work benefit from a daily sync. The compromise most distributed teams land on: async by default, sync once or twice a week, dissent explicitly invited. Activity in async channels is not the same as alignment, and pretending otherwise creates its own theater.
"Devil's advocacy lowers satisfaction." Schweiger's data is real. Better decisions, lower acceptance. The mitigation is twofold: rotate the role so no one person owns it, and pair adversarial process with explicit relational repair afterward. Naming what just happened ("Jess pushed hard on that, by design, here's what changed because of it") goes a long way.
"Written dissent doesn't replace conflict, it relocates it." True. The backstage moves, it does not disappear. Anonymous channels and async docs can become the new place where the real conversation happens, while the meetings remain theater. The only durable fix is making it psychologically safer to say the hard thing in the room. Rituals help. They are not a substitute for the underlying skill.
The Real Problem: Psychological Safety in Hybrid Is Structurally Harder
Amy Edmondson's psychological safety research originally found that the best hospital teams reported more errors, not fewer, because reporting was safe (Edmondson, ASQ, 1999). Her later work with Mark Mortensen made a sharp point about hybrid: the conditions for psychological safety shift in remote and hybrid work, and the team has to rebuild them on purpose (Edmondson & Mortensen, HBR, 2021). The cues that signaled safety in person got stripped out. Distributed teams have to build deliberately what in-person teams got for free.
This is why psychological safety is a perishable skill for distributed teams in particular. The hallway is gone. Rituals are the new hallway. If your team does not have practiced ways to surface dissent in the moment, the dissent does not disappear. It just routes around the people who need to hear it.
Gallup's 2024 engagement data suggests the cost is climbing. Global engagement dropped from 23% to 21% in 2024, the second decline since 2009. Manager engagement fell from 30% to 27%, with Gallup pegging the lost productivity at $438 billion (Gallup, 2024). When managers can't read the room and people can't say what they actually think, both numbers move in the same direction.
Reps Beat Posture
Saying the hard thing on a call is a learned skill. It takes reps. The teams that do it well got there by doing it in lower-stakes moments first.
This is the condition QuestWorks tries to build, on its own platform with Slack and Microsoft Teams as the integration layer. Twenty-five-minute AI-facilitated team simulations, two to five players, weekly. Teams work through scenarios where the easy move is the polite move and the right move is the one that surfaces the disagreement out loud. HeroGPT coaching stays private. HeroTypes are visible across the team, giving people a shared vocabulary for how each other shows up under pressure.
If a team practices, every week, saying what they actually think in a low-stakes context, they get faster at doing it in the high-stakes one. The post-meeting DM gets shorter because more of it happened in the meeting. Standup theatre gets defeated by the one thing actors are good at: rehearsal.
Distributed teams will keep having post-meeting talks. The question is whether that talk is filling a gap the meeting left or replacing the meeting altogether. If your real decisions are being made in DMs, your meetings have already stopped being meetings. See also how engineering teams build peer-feedback cultures that make the hard conversation routine.
