Remote Working and Managing a Team
▶TLDR
- Remote teams run on written process, not on hoping people remember what you said.
- Record Looms for anything you do more than once, then bucket the work so it can be handed off.
- Hire against the most painful bucket first instead of looking for one person who does everything.
Work in Programming, hosted by Matthew Weeks, looks at what it is like working on a product team. So this conversation stayed on the ground: how you run a distributed team and the systems that keep it from falling apart.
Managing people you do not sit next to is a different skill. The teams that do it well lean hard on written process and clear ownership.
Systems beat memory on a remote team
When everyone is remote, the stuff living in your head is invisible to everyone else. So it has to come out of your head and into a process. I record Looms for anything I do more than once. A short video of the actual work beats a page of instructions almost every time.
Then I bucket the tasks by type. That gives everyone a clear map of what they own and where the edges are, which is what remote work needs to run smoothly.
Handing off work without the drop
Once the process is recorded, you can hand it off. Hire against the most painful bucket first. Do not go looking for one person who can do everything, because that person does not exist and you will wait forever for them.
The payoff is that you stop being the single point of failure. The work keeps moving when you step away. I talked through rebuilding a team on business infrastructure and curing back office blues, and the systems angle on Sproutworth.
Work in Programming
Work in Programming, hosted by Matthew Weeks, is a show about life on a tech product team. He talks with developers, product managers, and engineering managers about their day-to-day work, team practices, and what makes a team run well.