Remote work is an arrangement in which employees work from locations outside a central office — from home, from co-working spaces, or from any other location with connectivity. The term describes geography, not method.
Remote work is often conflated with async work, but they are different. Remote describes where the work happens. Async describes how decisions and handoffs travel. A team can be fully remote and still operate synchronously, with constant calls and real-time interruptions.
Most remote teams do not benefit fully from their remote arrangement until they also adopt async governance. Otherwise, they recreate the in-office coordination model over video, with all of its costs and none of its incidental benefits.
Why Remote work Matters for Distributed Teams
Remote work without async governance is a worse version of office work. The constant interruptions remain. The meetings multiply. The coordination overhead grows. The only thing that changes is the commute.
The teams that thrive remotely treat the location change as a forcing function to redesign their operating model around declared state, written decisions, and structured handoffs.
Frequently Asked Questions
What is remote work?
Remote work is an arrangement in which employees work from outside a central office. It describes location only — not how the team coordinates. A remote team can still operate synchronously, with constant real-time meetings.
Related Terms
Distributed team
A distributed team is a team whose members work from multiple locations and, typically, multiple timezones. The defining...
Read definitionHybrid work
Hybrid work is an arrangement that combines in-office and remote workdays. The mix varies — some organizations require t...
Read definitionAsync work
Async work is a mode of operating in which progress does not depend on people being online at the same time. Tasks move ...
Read definitionGet the vocabulary that makes distributed teams work
One email per week on async governance. No spam.
See remote work in action.
StandIn is built around these concepts. Engineers publish declared state before going offline. The next shift starts with full context.