Enable javascript in your browser for better experience. Need to know to enable it? Go here.
radar blip
radar blip

Satellite workers without "remote native"

Published : Oct 26, 2022
Not on the current edition
This blip is not on the current edition of the Radar. If it was on one of the last few editions it is likely that it is still relevant. If the blip is older it might no longer be relevant and our assessment might be different today. Unfortunately, we simply don't have the bandwidth to continuously review blips from previous editions of the Radar Understand more
Oct 2022
Hold ?

The term "remote team setup" does not just describe one setup; it encompasses multiple patterns and flavors. And many teams have been changing patterns recently. They're coming out of the "everybody always remote" mode that was forced on them by a pandemic and moving into a pattern of (often rotating) satellite workers, where part of the team is co-located and part of the team is remote. We see many of them failing to properly consider what this means for their ways of working. Satellite workers without "remote native" ways of working is a slip back into privileging co-located practices. In a setup with satellite workers, it's important to still use "remote native" processes and approaches by default. For example, if the co-located part of the team joins a meeting together, they should still all be on their individual laptops to participate in digital collaboration or meeting chat. Teams need to be aware of the risk of excluding their satellite workers and creating silos and feelings of exclusion. If you know that you'll always have at least one satellite team member, the default ways of working should assume remoteness.

Download the PDF



English | Español | Português | 中文

Sign up for the Technology Radar newsletter


Subscribe now

Visit our archive to read previous volumes