Research
The case against unnecessary meetings is not just philosophical. The data is clear: developers spend too much time in meetings, most of those meetings do not produce proportional value, and the context-switching cost is far higher than the meeting duration alone suggests.
We compiled the most cited research on developer meeting time, standup effectiveness, and the cost of interruptions. These are the numbers that informed how we built Paperwork.
31 hours / month
The average employee spends 31 hours per month in unproductive meetings. For developers, whose work requires sustained concentration, the cost per hour is disproportionately high.
Source: Atlassian, "You Waste a Lot of Time at Work" (workplace survey)
252% increase
Weekly meeting time has increased 252% since February 2020. The shift to remote work did not reduce meetings; it multiplied them. Teams replaced hallway conversations with scheduled calls and never removed them.
Source: Microsoft Work Trend Index (2022)
70% of meetings
70% of all meetings keep employees from doing productive work. Not 70% of bad meetings. 70% of all meetings.
Source: Harvard Business Review, "Stop the Meeting Madness" (2017)
Only 53% find standups valuable
Nearly half of agile practitioners do not find standups valuable. The ceremony persists not because it works, but because it is the default. Teams keep doing it because stopping feels like giving up on coordination.
Source: State of Agile Report (VersionOne / Digital.ai)
15 minutes → 32 minutes
Standups that are designed to take 15 minutes routinely expand to over 30. Without structural pressure, every synchronous meeting drifts toward filling its container and beyond.
Source: Scrum Alliance survey data; corroborated by multiple agile coaching reports
23 minutes
It takes an average of 23 minutes and 15 seconds to fully refocus after an interruption. A 15-minute standup does not cost 15 minutes. It costs 38 minutes: the meeting itself plus the recovery time to get back into flow.
Source: Gloria Mark, University of California, Irvine, "The Cost of Interrupted Work" (2008)
40% productivity loss
Multitasking and context switching can reduce productivity by up to 40%. For developers who need deep focus to solve complex problems, fragmented days are not just annoying. They are structurally incompatible with the work.
Source: American Psychological Association, "Multitasking: Switching Costs" (2001)
58% prefer async
The majority of knowledge workers prefer asynchronous communication for status updates and coordination. Synchronous meetings are preferred only for brainstorming, decision-making, and relationship building — not for reporting what you did yesterday.
Source: Buffer, "State of Remote Work" report (2023)
No-meeting days: +73% productive output
Companies that implemented no-meeting days reported a 73% increase in productive output on those days. The finding is not that meetings are bad. It is that uninterrupted time is disproportionately valuable for engineering work.
Source: MIT Sloan Management Review, "The Surprising Impact of Meeting-Free Days" (2022)
What we built based on this data
Paperwork replaces synchronous ceremonies with a shared feed, personal focus discipline, and automatic expiration. The goal is not "better meetings." It is fewer meetings, replaced by visible work. Read the Visible Work Method or calculate what your standups cost.