Skip to content

Blog /Teamwork /

Turning back the clock

Async work is here, no matter where you are.

September 17th, 2024

by Henry Poydar

in Teamwork

Amazon wants to set its corporate clock back to before the pandemic.

The fundamental problem with trying to “turn back the corporate clock” to five years ago is this: We. Work. Differently.

The pandemic forever altered the way we collaborate and communicate to create value, especially for those of us building software products or leading teams of people who do that.

The big difference? We let the async genie out of the bottle.

Instead of picking up the phone or tapping some physically or virtually on the shoulder for a sync discussion, we default to async.

We text. We message. We email. We post comments. We send voice and video memos. We write stuff out in docs, wiki pages, issues, and pull requests.

This is mainstream work behavior now. It’s the way it is.

So. The challenge of modern work is figuring out how to get async right.

Lots of orgs are fumbling with this, mistaking unlimited async communication for async coordination and the alignment of people and goals.

Instead of a plan for modern work, they fall back to endless meetings or office mandates, and in the process create for themselves productivity, quality, and retention problems.

This is why we created Continuous Coordination (and built Steady to support it).

Continuous Coordination is a set of principles for people and teams to happily and efficiently build great quality software together, no matter where they are on any given day—in office, home office, or otherwise.

Continuous Coordination turns async chaos into progress.

More in Teamwork

Subscribe to The Steady Beat

A weekly-ish round-up of hand-picked articles and resources for people who make software products: designers, engineers, product managers, and organizational leaders.

Subscribe now