All articles
486 articles on async work, handoffs and coverage. Page 4 of 21.
- Across Time Zones
How Much Overlap Does a Distributed Team Actually Need?
Most distributed teams need two to three hours of overlap per seam per week, not per day. Here is what overlap is genuinely for.
- Interruptions and Context
Context Switching: the Cost Is in the Questions, Not the Tickets
Work-in-progress limits fix the switches you planned. The expensive ones are involuntary: someone asks where a thing is and you drop what you were holding.
- AI at Work
AI Tools Added to the Workload. The Teams That Noticed First.
Productivity falls past four AI tools, and an hour of checking follows every hour saved. Production was never the bottleneck. The waiting was.
- Hours and Boundaries
Your Engineer Logged Off at 18:00. Here Is What to Do With the Question at 22:00.
Three bad options at 22:00: message them, guess, or lose the morning. Almost every night question is retrieval.
- Onboarding
Remote Engineering Onboarding: the First 30 Days of Questions
Remote onboarding is a question-asking problem, not an information problem. A four-week plan built around who answers what, week by week.
- Ops Operating System
The Operating Rhythm for a 200-Person Company in Three Countries
A cadence on paper describes a tenth of how a company coordinates. Design the meetings around decisions and the gaps between them around answers.
- Async and Meetings
Async Communication: The Practices That Survive Contact With a Deadline
Async practices collapse under deadline pressure, and that is information. Three survive, three do not.
- Across Time Zones
Managing a Team Across Three Time Zones Without Anyone Working Two Shifts
Three time zones has no shared hour, so the manager becomes the relay. Sort the cross-seam traffic into status, decisions, and escalations.
- Comparisons
One Question, Two Answers: A Twin and a StandIn
The same question, answered by an AI twin and by a StandIn. A conceptual side-by-side of how each behaves, and where the real difference shows.
- Comparisons
AI Twin, AI Assistant, or Stand In: A Plain Comparison
AI twin, AI assistant, and StandIn get lumped together. Here is a plain comparison of what each claims to do and how they actually differ.
- Interruptions and Context
What Interruptions Cost an Engineering Team, and Where They Come From
The cost of an interruption is the recovery, not the two minutes. Where interruptions come from, and why two people absorb most of them.
- Comparisons
Glean, Guru, and the Question Neither One Answers
Glean searches your tools, Guru organizes knowledge cards. A fair look at both, plus the question neither one answers while the owner is away.
- Async practice
Right to Disconnect Is a Policy. Coverage Is a System.
A right to disconnect protects your time on paper. Whether the work waits or gets covered is a separate problem, and only one of them is solved.
- Async practice
Async Standup Formats, and When Each One Fails
Three async standup formats for distributed teams, what each one is good at, and the exact point where each one quietly stops working.
- Async practice
Onboarding a Remote Engineer Who Cannot Ask Anyone
A practical guide to onboarding a remote engineer across time zones, when the answers they need are hours away and nobody is online to ask.
- Async practice
What Good Teams Do Differently at Shift Change
How distributed teams hand off clean at shift change: what to write, what to leave open, and how to keep work moving across time zones.
- Coverage
Finding the One Person Who Knows, in Under a Day
A step-by-step way to find the one subject matter expert who knows, in under a day, without interrupting half the company to get there.
- Coverage
Week One at a Big Company: Finding Who Answers What
Starting a new job at a big company? How to find who actually answers what, and why finding the right person is the real first-week blocker.
- Coverage
What a Quick Question Costs the Person You Asked
A quick question costs the coworker their focus, not just seconds. What interruptions really cost, and how to lower the bill without going silent.
- Coverage
The One Person Who Knows, and the Risk Nobody Names
When one person is the only one who knows, you carry a risk nobody names. What bus factor one really costs, and how to lower the number.
- Coverage
Finding the Owner When the Org Chart Is Stale
The org chart is stale and the owner moved on. A step-by-step way to find who really owns a project by following the work, not the chart.
- Coverage
The Wait Every Question Sits Through Overnight
One small question, two time zones, and most of a day lost. A short story about why answers wait overnight, and how to stop the delay.
- AI at work
Who Decides Whether AI Can Speak For You
Before an AI answers in your name, someone has to decide it can. Here is why that consent belongs to you and what real control looks like.
- AI at work
The Bot Attended the Meeting. Nobody Got an Answer
Meeting bots transcribe and summarize well, but they cannot answer the question that comes up after you leave. Here is the gap.
Your team’s week, answered from the work.
If this is your team’s week, see what a StandIn does with it.