---
title: "Managing remote teams a crash course"
tags:
  - wiki
  - sources
sources:
  - "[[Managing remote teams a crash course]]"
domains: [career]
date: "2026-07-17T06:23:07.439Z"
created: "2026-07-17T06:23:07.439Z"
includeInRss: false
---

# Managing remote teams a crash course

## Takeaways

- Remote setups differ: **satellite offices**, **remote employees** (minority remote), **fully distributed**, and **remote-first** (distributed + optional non-critical office) — only the last two count as truly remote.
- Hybrid setups (most in office, few remote) create asymmetric communication failures — remote-first process design matters more than "allowing WFH."
- Remote teams need **async-first communication**, explicit documentation, and intentional overlap windows — not accidental office habits stretched globally.
- Management load shifts toward **clarity of goals, written culture, and trust**; "did you see my message?" is a process failure signal.
- Useful for deciding **when remote works** (autonomous work, strong writers) vs when co-location still wins (high ambiguity, early team formation).
- Andreas Klinger's Product Hunt experience is the anchor example — fully distributed at scale.

## Notes

Classic remote-management primer for Ben's engineering leadership context — pairs with ObsidianOS `/meeting` and `/recap` skills that assume distributed async work.

## Open questions

- Which remote-first practices from this vault (Daily captures, meeting notes, recaps) close the biggest gaps for a distributed team?