How to Write Async Updates That Actually Get Read
Most async updates fail before they're read. Here's how to write async updates that actually get actioned — a 4-part template for ICs on distributed teams. (155 characters)
read more →Thinking on distributed work, async coordination, and the systems problems hiding inside your calendar.
Most async updates fail before they're read. Here's how to write async updates that actually get actioned — a 4-part template for ICs on distributed teams. (155 characters)
read more →Why do meetings keep coming back even after you cut them? This analysis names the structural causes of meeting default behaviour.
read more →How much does timezone math actually cost your team? A concrete breakdown of conversion overhead, scheduling round-trips, and bad-slot attention loss — with the arithmetic.
read more →Cross-timezone meeting fatigue has five structural causes. Understanding them explains why cutting meetings alone doesn't solve it — and what actually does.
read more →When async breaks down, it follows predictable patterns. Five failure modes, each with a structural cause — so you can stop treating five problems as one.
read more →Why treating coordination as a calendar problem has been holding distributed teams back — and what happens when you think about it differently.
read more →A set of operating principles for teams that have accepted that synchronous coordination is a special case, not the default.
read more →Drift is not just a problem for spacecraft. Every distributed team accumulates it — in the form of desynchronised context, diverging assumptions, and meetings that no longer reflect reality.
read more →