All articles
486 articles on async work, handoffs and coverage. Page 3 of 21.
- Across Time Zones
Managing an Offshore Engineering Team You Cannot Be Online With
Offshore teams rarely fail on capability. They fail on the round trip: a question asked at 10:00 their time answered a day later.
- Hours and Boundaries
Response-Time Expectations: Put Them in Writing Before Someone Burns Out
Unwritten response times default to the fastest responder. Publish a table in the recipient working hours, and include the row that costs nobody anything.
- Ops Operating System
Reducing Escalations: Most of Them Are Questions That Had an Answer
An escalation is what a question becomes after 48 hours of silence. Classify a month of them and the information category dominates. Reduce latency, not triage.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Hours and Boundaries
The 22:00 Message: How to Write It Without the Team Reading It
Writing late is fine. Sending is not. Separate composing from delivering, and ask the record before you write to the person at all.
- Async and Meetings
Replacing the Daily Standup Without Losing the Information
A standup produces state, blockers, and incidental conversation. Only the third needs a call. Here is what to write instead.
- Interruptions and Context
Reducing Slack Interruptions on a Team of Twelve
On a twelve-person team the channel becomes a support desk with one unpaid operator. Four steps in order, ending with the one that works.
- Onboarding
Cutting New-Hire Ramp Time: the Questions They Are Afraid to Ask Twice
New hires do not ask twice. They guess, and you find out in review. Ramp time is set by how cheaply a question can be asked.
- Ops Operating System
A Weekly Ops Review That Is Not a Status Meeting
Two thirds of a typical ops review is updates read aloud. Move them to a pre-read, refuse to repeat them, and limit the agenda to off-plan items and decisions.
- Async and Meetings
Becoming Async-First in a Team That Runs on Slack
Slack is not the obstacle. The expectation of instant replies is. Three changes make async stick, and the third one decides the outcome.
Your team’s week, answered from the work.
If this is your team’s week, see what a StandIn does with it.