Why work doesn't happen at work

Escaping the Office's M&M Trap

Picture a software developer logging into her laptop from a sunlit corner of her apartment at 9 a.m., coffee in hand and no one else around. She blocks three uninterrupted hours to solve a complex coding problem, her only sounds the hum of the refrigerator and occasional birds outside. By midday she has made real progress, something that rarely happened when she sat in an open-plan office.

Jason Fried's central claim is that work doesn't happen at work. He argues the office is simply not a good place to do it because the two main offenders—managers and meetings, which he calls the M&Ms—turn the day into an interruption hub filled with distractions that prevent deep focus. Fried underscores this with the observation that the office during the day is the last place you'd want to be if you really want to get work done.

Applied to the developer's morning, Fried's thinking explains why her remote setup succeeds where the traditional office failed. Without managers popping by her desk or meetings scheduled back-to-back, she can protect long stretches of concentration. Remote arrangements directly address the central question of minimizing those M&Ms: workers gain the freedom to design environments free of the very interruptions Fried identifies as productivity killers.

Fried notes that offices create these problems systematically, yet he also points out that three practical suggestions can make the workplace actually work. In a remote context, those same ideas translate into intentional boundaries—such as asynchronous updates instead of meetings and clear availability rules instead of constant manager check-ins—allowing the kind of focused effort the developer enjoyed.

The lasting question is whether we will keep treating the office as the default setting or finally build work around the conditions that let real thinking happen.