Two weeks ago, my team was in the office. Now we’re fully remote, and so is everyone else.

The speed of this shift is hard to overstate. Companies that had “2021 digital transformation roadmaps” are compressing those plans into days. I’ve watched three different vendor threads blow up in my network this week alone — each one pitching some variation of “we’ll get you remote-ready in 48 hours.”

That’s not transformation. That’s panic.

The Scramble #

A Fortune/Deloitte survey found 77% of CEOs said the pandemic accelerated their digital transformation timelines. I believe it. At TaskRabbit, we were already remote-friendly before COVID hit (distributed team, cloud infrastructure, async communication baked into how we work). The transition wasn’t painless, but it wasn’t existential either.

Not every company has that luxury. I’ve talked to engineering managers at places where deploying code still requires VPN access to an on-prem build server. Where the ticketing system runs on an internal network. Where “remote work” means someone emails you a spreadsheet.

For those companies, the last two weeks haven’t been a transformation. They’ve been a crisis.

FOMO Makes It Worse #

The fear of missing out is driving terrible decisions right now. I’ve seen teams adopt Slack, Microsoft Teams, and Zoom in the same week because different departments picked different tools. Nobody coordinated. Now they’ve got three communication platforms, none of them integrated — and engineers are context-switching between all three.

This is what happens when urgency replaces strategy. You end up with a fragmented stack that creates more friction than the problem it was supposed to solve.

Real digital transformation isn’t about buying tools. It’s about rethinking how work flows through an organization — and that takes months (usually years). No amount of FOMO changes the timeline.

What Actually Helped #

The companies handling this best aren’t the ones that moved fastest. They’re the ones that already had remote-friendly infrastructure, even if they never called it “digital transformation.”

Cloud-native deployments. Async communication norms. Documentation habits that don’t require being in the same room. Code review processes that don’t need you sitting next to someone to work. These aren’t flashy; no one puts them in a press release. But they’re the difference between “we shifted to remote and kept shipping” and “we’re still trying to figure out how to deploy.”

At TaskRabbit, our CI/CD pipelines and A/B testing infrastructure didn’t care where engineers sat. The deploy process was the same from a home office as from our San Francisco HQ. That’s not because we planned for a pandemic — it’s because distributed teams need those things regardless. It’s table stakes.

The Uncomfortable Truth #

The companies struggling most right now aren’t struggling because they lack tools. They’re struggling because their processes assumed physical proximity.

Standups that only work in person. Decisions made in hallway conversations that never get documented. Onboarding that depends on a new hire sitting next to a senior engineer for two weeks. Those are cultural problems, not technology problems. And you can’t fix a cultural problem by buying a Zoom license.

I don’t know how long this lasts. Nobody does. But I think the organizations that come out of this strongest will be the ones that used the crisis to actually fix their processes — not just their tool stack.

The ones treating this as a forcing function for the org changes they’d been putting off. Not the ones that bought three collaboration tools in a panic and called it transformation.