All articles
727 articles on async work, handoffs and coverage. Page 4 of 31.
- Coverage
Keeping Delivery Moving When the Delivery Lead Is Out
The plan does not stop existing when the lead is away, it stops being retrievable. Cover the project rather than the person.
- Async and Meetings
Sync or Async: a Two-Question Test
Question one: does the outcome depend on real-time exchange? Question two: does the answer already exist in someone's work?
- Across Time Zones
Rotating Meetings Across Time Zones Treats the Symptom
Rotation spreads an unkind meeting hour evenly instead of removing it. Most rotated meetings are status meetings.
- Interruptions and Context
Bus Factor of One: the Person Who Can Never Take a Holiday
Bus factor is not a catastrophe risk, it is an annual cost: one holiday, a fortnight of lost momentum. Why documentation misses it and what actually reduces it.
- Interruptions and Context
Knowledge Silos on a Distributed Team: the Fix Is Not Another Wiki
A silo is a routing problem, not a storage problem. Wikis fail because they ask the reader to know what the answer is called.
- Coverage
Taking a Real Holiday as a Manager (the Team Survives)
Managers check messages because they are the decision route, and checking is what causes the messages.
- Async and Meetings
Making Decisions Async Without Them Getting Reopened
Async decisions get reopened because they were never closed. Four lines close one: what was decided, by whom, what was rejected, and who can change it.
- Across Time Zones
US and European Teams: Keeping Their Morning From Becoming Your Evening
The Europe to US overlap lands at the end of the European day, so their morning becomes your evening.
- Ops Operating System
Making Decisions Stick Across Time Zones
Across zones a decision is made in one place and received secondhand in another. The reasoning and the authority are what get lost.
- Onboarding
Handing Over a Project Mid-Flight
The deck covers the shape. The questions are the other sixty percent. A six-item handover checklist, and how to keep the successor from depending on one person.
- Interruptions and Context
Answering the Same Question for the Fourth Time Is a System Failure
The fourth time you answer something, the problem is not the asker. The answer exists and is not reachable.
- Hours and Boundaries
Fixing Always-On on Your Own Team, Before HR Writes a Policy
Nobody asked them to be online at 23:00. Being unavailable has a visible cost and being available does not.
- Coverage
Parental Leave Handover for a Lead Role: Three Months of Context in One Place
Three months is not a long holiday. Name an interim owner eight weeks out, transfer judgement by doing, and keep the record answerable while the person is away.
- Async and Meetings
Replace the Status Meeting, Keep the Status
A status meeting solves an availability problem badly: it batches a continuous need into a weekly event.
- Across Time Zones
Working With a Team in Asia From Europe: What Actually Breaks
Europe and Asia share about two hours. What breaks is the question asked at the start of the Asian day that cannot be answered until Europe wakes up.
- Ops Operating System
The DRI Model in Distributed Teams: Who Answers When They Are Off
A single directly responsible individual works in one zone and bottlenecks across three. Separate decisions from context, and only the decisions wait for them.
- Interruptions and Context
Slack Norms a Team Actually Keeps (Template)
Six norms, not twenty: response time, channels over DMs, whole question, threads, scheduled send, and check what they wrote down before you ask.
- AI at Work
Why Most AI Pilots Do Not Reach Production
42 percent of companies scrapped most AI initiatives in 2025, up from 17 percent. Pilots fail on owner, measure, scope, and user, not on capability.
- Onboarding
Your New Hire Has Forty Questions and One Person to Ask
Forty questions at fifteen minutes each is a lost week for the buddy, and the new hire rations the rest into guesses.
- Coverage
A Coverage Plan for a Twelve-Person Team (Template)
Five columns on one screen: person, area, where questions go first, who decides, and their limit. Plus the column most plans miss.
- Async and Meetings
Cutting Meetings on a Distributed Team: Start With the Ones That Exist to Answer Questions
Do not cut meetings by percentage. Sort them by purpose: decide, argue, connect, or inform. The informing meetings are where the hours hide.
- Across Time Zones
Follow-the-Sun Without the 24-Hour Availability Expectation
Follow-the-sun moves work between zones. Most implementations drift into keeping people reachable in all of them.
- Interruptions and Context
Protecting Focus Time When Everyone Can See Your Calendar
A focus block is visible to everyone and defended by no one. It stops meetings and not messages. Here is why it fails, and what has to exist behind it.
- Ops Operating System
Who Owns What: Ownership Clarity for Distributed Teams (RACI and After)
Two people thinking the other has it is a missing boundary. RACI answers roles, not questions. Replace the matrix with one line per area.
Your team’s week, answered from the work.
If this is your team’s week, see what a StandIn does with it.