All articles
486 articles on async work, handoffs and coverage. Page 2 of 21.
- 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.
- 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
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.
- 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.
- Ops Operating System
Why Projects Slip on Distributed Teams: Waiting, Not Working
Work waits for people to be free, and across zones each wait has a floor of one night. Measure elapsed against active time on five items.
- AI at Work
AI Summaries Capture What Was Said, Not What Was Decided
Summaries get topics, tone, and action items right and miss the decision, because decisions in real meetings are implicit. A summary holds what a model heard.
- Coverage
Out-of-Office Messages That Answer Instead of Apologise
Four out-of-office examples you can copy, three rules for writing them, five mistakes to avoid, and the version that is not an auto-reply at all.
- Ops Operating System
Project Status Reports Executives Read, and Stop Asking About
Executives read for exceptions and decisions. Five lines: confidence, what changed, one risk, the decision you need, and next.
- Hours and Boundaries
Team Quiet Hours That Survive the First Urgent Question
Quiet hours die at the first undefined exception. Write the exceptions first, keep them to two, and note that most urgent evening messages are status questions.
- Coverage
Out-of-Office Replies Apologise. Here Is the Alternative.
An out-of-office is an automated apology for a delay. Better wording does not change the category.
- Async and Meetings
Building a Write-It-Down Culture, and Why People Stop
People stop writing because the cost is theirs and the benefit is someone else, later. Make writing save the writer a question and it needs no enforcement.
- Across Time Zones
A Communication Plan for a Team in Three Countries (Template)
One page: which channel, how fast, who decides, and where to look before you ask a person. A communication plan template for distributed teams.
- Onboarding
The Onboarding Buddy Is Doing Support Work. Give Them Their Day Back.
The buddy role is described as mentoring and performed as a help desk. Split it: retrieval to the record, mentoring to the human.
- Ops Operating System
Cross-Functional Alignment When the Functions Are in Different Countries
Sales promising what product never heard is a commitment made where the other function could not see it. Fix the commitment path, not the meeting cadence.
- Async and Meetings
No-Meeting Days Work Until Someone Needs an Answer
A no-meeting day removes the calendar entries and leaves the need, so it arrives as messages instead.
Your team’s week, answered from the work.
If this is your team’s week, see what a StandIn does with it.