All articles
727 articles on async work, handoffs and coverage. Page 2 of 31.
- Interruptions and Context
Sort Your Interruptions Into Two Piles and Only One Should Reach You
Focus time fails because it blocks real questions and repeat questions alike. Log a week, sort them, and make the second pile never arrive.
- Across Time Zones
Working With Overseas Suppliers When the Factory Day Is Already Over
A question sent at 17:00 lands after the factory day is over. Send in your morning, ask closed questions with a default, and keep one record per order.
- Coverage
Parental Leave Handover: The Last Four Weeks and the First Two
Split the role rather than assigning it, run a swap week where cover works alone, and agree the contact rule in writing before leave starts.
- Handoffs
A Handover Document Template That Puts Open Questions First
Most handover templates are ordered backwards. Put the open questions at the top. Five sections, two pages, about ninety minutes to fill.
- Across Time Zones
Managing a Team Across Time Zones: Design the Work Around the Waiting
A bigger gap means less real time exchange. Manage the waiting instead: named owners, a written daily handoff, decisions with a home, answers without a person.
- Distributed Teams
A Blocker Is a Question With a Sleeping Owner
Most distributed blockers are questions waiting on a person. Add who it is blocked on and since when, then shorten the wait three ways.
- Distributed Teams
Managing an Offshore Development Team: Day Start and Day End Routines
Offshore delivery fails on the seam, not the skill. A day end writeup with open questions and a day start reply carry almost all of it.
- Across Time Zones
What a Time Zone Difference Actually Costs a Team
The research finding is narrow: a bigger gap means less real time exchange. The cost shows up as round trips. Here is a Tuesday between Tokyo and Amsterdam.
- Across Time Zones
Time Zone Overlap for Remote Teams: A Worked Table of City Pairs
Real overlap for common city pairs on a 09:00 to 17:00 day. Amsterdam and New York gives two hours. Here is what to do when it is under two.
- Coverage
Who Decides While You Are Away: The Decision List You Write Before Leaving
Sort every decision into what waits, what a named person decides, and what needs you. Write the limit and the fallback. It takes about forty minutes.
- Handoffs
Knowledge Transfer When an Employee Leaves: A Two Week Plan
Start from what people keep asking the leaver, not from what the leaver thinks they know. Week one collects questions, week two answers them.
- Coverage
How to Hand Off Your Work Before Vacation (Without Being Messaged Anyway)
Handover documents fail because they describe your work. Write the questions people will ask instead, name an owner per area, and say what has no cover.
- Interruptions and Context
An Internal FAQ That Stays Current (Most Do Not, Here Is Why)
FAQs go stale because they mix answers that never change with answers that change weekly. Split them, and cap the stable half at twenty entries.
- Ops Operating System
How to Stop Being the Bottleneck in Your Own Company
You are the bottleneck because you are the fastest route to an answer. Count the questions you answer twice, then make the other route cheaper than asking you.
- Coverage
Knowledge Transfer Before Someone Leaves Is Too Late by the Time It Starts
Two weeks cannot transfer two years. Triage the fortnight: reasoning, relationships, dead ends. What survives is what was written down along the way.
- Coverage
Key Person Dependency: How to Find It Before It Finds You
Key person dependency is about who gets asked, not who has the title. Find it with a one week question log, then three fixes in the order that pays back.
- Async and Meetings
Running Retros Async Across Time Zones
Split the retro: gathering is async and better that way, deciding is live and short. Two days to contribute, thirty minutes to decide, three actions.
- Across Time Zones
Working-Hours Agreements for Distributed Teams That Hold Up
Flexible hours without a written agreement becomes always available. Four parts make one hold, and most agreements are missing the fourth.
- Ops Operating System
Blocked on a Person: Measuring the Waiting in Your Delivery
Blocked usually means asked someone, no reply yet. Split the status in two, add who and since when, and the invisible cost becomes a number you can act on.
- Onboarding
Onboarding a Contractor for a Six-Week Engagement
A week of orientation is seventeen percent of a six-week contract. Access before day one, one named contact, and scope that fits the time.
- Interruptions and Context
Nobody Reads the Docs. Here Is What They Do Instead.
People message the person who wrote the doc, because asking takes eleven seconds and works. Better search and better structure do not fix it.
- Hours and Boundaries
Right to Disconnect for Distributed Teams: the Operational Guide
Disconnect policies assume one time zone. Anchor everything to declared personal hours, and answer the question every policy skips.
- Coverage
Reducing Dependency on the One Person Everyone Asks
The person everyone asks is a queue with one server and no hours. What it costs, and why they cannot fix it themselves.
- Async and Meetings
Project Updates Stakeholders Read, and Stop DMing You About
Stakeholders message you because the update answered your questions, not theirs. Five lines: status, change, risk, decision needed, next.
Your team’s week, answered from the work.
If this is your team’s week, see what a StandIn does with it.