{"id":250239,"date":"2026-05-26T16:42:53","date_gmt":"2026-05-26T20:42:53","guid":{"rendered":"https:\/\/rmcls.com\/learn\/?p=250239"},"modified":"2026-05-26T16:42:57","modified_gmt":"2026-05-26T20:42:57","slug":"the-rto-isnt-fixing-what-you-think-its-fixing","status":"publish","type":"post","link":"https:\/\/rmcls.com\/learn\/blog\/the-rto-isnt-fixing-what-you-think-its-fixing\/","title":{"rendered":"The RTO isn’t fixing what you think it’s fixing"},"content":{"rendered":"\n

Why experienced project managers need a sharper async strategy – regardless of where their teams sit.<\/strong><\/h3>\n\n\n\n

Let’s start with something a little uncomfortable.<\/p>\n\n\n\n

<\/div>\n\n\n\n

When a company announces a return-to-office mandate, the stated reason is almost never the real reason. “Collaboration,” “culture,” and “innovation” are the words that show up in the press release. What’s actually behind it is usually some combination of: real estate commitments that look embarrassing on the balance sheet, executive discomfort with what they can’t see, and a genuine – if sometimes misplaced – belief that physical proximity solves coordination problems.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Here’s what experienced project managers know that a lot of C-suite announcements don’t acknowledge: the coordination problems were there before COVID too.<\/strong> The office was just a more expensive way of papering over them.<\/p>\n\n\n\n

<\/div>\n\n\n\n

The teams you’re managing in 2026 are distributed whether you like it or not. Maybe not geographically – but across time zones, across hybrid schedules, across the cognitive fragmentation of constant partial attention. If your project management approach still depends on everyone being in the same room at the same time, you have a structural problem and mandating badge swipes won’t solve it. Here’s what might.<\/p>\n\n\n\n

<\/div>\n\n\n\n

The data on where we actually are<\/h2>\n\n\n\n

Despite the noise around RTO, the workforce reality is stubbornly hybrid. Gallup’s 2024 State of the American Workplace<\/em> report found that 53% of remote-capable workers remain in hybrid or fully remote arrangements<\/strong> \u2014 and that number has held relatively stable through successive waves of return-to-office mandates.<\/p>\n\n\n\n

<\/div>\n\n\n\n

More telling: among knowledge workers \u2014 the population most project managers are leading \u2014 fully in-office work dropped from 60% pre-pandemic to around 20% by 2024<\/strong>, and hasn’t bounced back. Stanford economist Nicholas Bloom’s ongoing research found that hybrid arrangements, when well-structured, show no productivity loss compared to fully in-office work<\/strong>, and in some knowledge work categories, a modest productivity gain.<\/p>\n\n\n\n

<\/div>\n\n\n\n

PMI’s research consistently shows that the majority of project teams today include members working from different locations \u2014 not just different homes, but different cities, time zones, and in many cases different countries. That’s the default project context for most PMs today.<\/p>\n\n\n\n

<\/div>\n\n\n\n

The question isn’t whether you’re managing a distributed team. The question is whether you’re managing it well.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Where most PM approaches break down on distributed teams<\/h2>\n\n\n\n

The failure mode is almost always the same: a synchronous-first project structure that was designed for a co-located world, bolted onto a distributed reality. You can spot it by looking at a few symptoms:<\/p>\n\n\n\n

<\/div>\n\n\n\n

Status updates that require a meeting to deliver.<\/strong> If the only time your team’s status gets captured is when everyone is on a call together, you have a synchronous dependency baked into your process. The moment someone can’t make the call \u2014 or is in a different time zone and the call time is unreasonable \u2014 your visibility disappears.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Decisions that wait for the right people to be available at the same time.<\/strong> Synchronous decision-making is expensive. It works when the stakes justify it. When it’s the default for all decisions, it becomes a bottleneck that slows everything.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Documentation that exists in people’s heads.<\/strong> In an office, you can walk over and ask. In a distributed team, if it’s not written down, it doesn’t exist for the people who weren’t in that hallway conversation. The institutional knowledge gap compounds over time.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Collaboration that only happens in meetings.<\/strong> Asana’s Anatomy of Work<\/em> research found that knowledge workers spend the majority of their day on coordination work \u2014 emails, status meetings, check-ins \u2014 rather than the skilled work they were actually hired to do. For distributed teams without a deliberate async structure, that proportion only climbs.<\/p>\n\n\n\n

<\/div>\n\n\n\n

What “async-first” actually means for a project manager<\/h2>\n\n\n\n

Async-first doesn’t mean no meetings. It means meetings are reserved for what they’re actually good at: relationship-building, complex problem-solving that genuinely benefits from real-time iteration, and high-stakes decisions that need collective buy-in in the moment.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Everything else \u2014 status, updates, reviews, approvals, information sharing \u2014 gets done in writing, asynchronously, with clear expectations about response times.<\/p>\n\n\n\n

<\/div>\n\n\n\n

In practice, this means the PM’s job shifts toward deliberate information architecture<\/strong>. You’re not just running a project; you’re building a system that keeps people informed and unblocked without requiring them to be in the same virtual room.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Some of the structural shifts that experienced PMs are finding most effective:<\/p>\n\n\n\n

<\/div>\n\n\n\n

Written standup culture.<\/strong> Replacing daily sync standups with a structured written format (What did I complete? What am I working on? What’s blocking me?) that gets posted in a channel at a consistent time. The PM reviews async, flags blockers, and only calls a synchronous conversation when a blocker genuinely needs one.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Decision logs, not just decision outputs.<\/strong> Documenting not just what was decided but why, what alternatives were considered, and who was consulted. This matters enormously for distributed teams because context that seems obvious in the moment becomes opaque six weeks later to someone who joined after the decision was made.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Explicit working agreements.<\/strong> The most functional distributed teams have a team charter that covers: when do we respond to messages (by the end of the business day in your timezone, not within the hour), what channels are for what purposes, how do we signal when we need a synchronous conversation versus an async response.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Camera-off is okay.<\/strong> This is worth saying explicitly because a lot of PMs still feel like they need to police this. Forcing cameras on in every call is a choice that communicates distrust and adds cognitive load. Reserve the expectation for the meetings where connection matters.<\/p>\n\n\n\n

<\/div>\n\n\n\n

The RTO tension that PMs are still stuck in the middle of<\/h2>\n\n\n\n

Here’s the uncomfortable position many project managers are in: you may personally believe hybrid-async approaches work well for your team. Your data \u2014 velocity, delivery quality, team satisfaction \u2014 may support that. And your organization’s leadership may still be pushing a return-to-office agenda that undermines the approach.<\/p>\n\n\n\n

<\/div>\n\n\n\n

This is a real tension and there’s no clean answer to it. But a few things are worth keeping in mind:<\/p>\n\n\n\n

<\/div>\n\n\n\n

Lead with outcomes, not preferences.<\/strong> If you’re making the case for distributed flexibility, the argument needs to be grounded in project data, not comfort. What’s your delivery rate? What’s your team’s retention? What does your stakeholder satisfaction look like? Opinions about hybrid work are everywhere. Data from your specific team is rare and valuable.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Don’t fight the policy; optimize within it.<\/strong> If your organization mandates three days in-office, the answer isn’t to resist \u2014 it’s to make the in-office days genuinely valuable for the kinds of collaboration that benefit from physical presence, and to run the async infrastructure well enough that the remote days aren’t a coordination disaster.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Build your async muscle before you need it.<\/strong> The teams that handle hybrid schedules, sick days, parental leave, or team member travel best are the ones that built async habits as a default rather than a contingency. If your project only functions when everyone shows up every day, you have a fragility problem.<\/p>\n\n\n\n

<\/div>\n\n\n\n

The stakeholder management piece people underestimate<\/h2>\n\n\n\n

Managing up in a distributed context is its own skill set and one that deserves more attention than it gets.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Executives who aren’t close to the work tend to experience distributed teams as opaque. The project feels invisible to them because the signal they previously got \u2014 seeing people at their desks, overhearing hallway conversations \u2014 is gone. Their anxiety about this is real even when it’s not rational.<\/p>\n\n\n\n

<\/div>\n\n\n\n

The experienced PM’s job in this context is to engineer visibility without engineering bureaucracy. That means:<\/p>\n\n\n\n

<\/div>\n\n\n\n