The StandIn Blog
Guides and ideas on time off and coverage, async handoffs, standups and status, and how AI should answer for a team.
- Hours and Boundaries
Right to Disconnect by Country: An Employer's Guide
Law in several European countries and Australia. No enacted right in the US as of 2026. Most regimes require a written policy rather than a ban on contact.
- Handoffs
Handing Over a Candidate Pipeline: What Was Said on the Last Call
The ATS holds the stage, not what the candidate said about why they might move. Three things transfer, and the middle one saves placements.
- AI at Work
AI Tools for Distributed Teams: Summaries Versus Who Owns the Decision
Four categories, and only one stands in for a colleague. Most rollouts stall because the output cannot be checked. Here is the one test to run.
- Distributed Teams
The Client Asks at 9am in New York and the Person Who Knows Is Finishing Their Evening
The client asks at 9am in New York and the person who knows is finishing their evening in India. Separate status, decisions and escalations, then state the pattern.
- Role Playbooks
Code Review Across Time Zones: Write the Description So Nobody Has to Ask
Every clarifying question costs a day. Four things a description must carry, including what you already rejected, plus the size rule for distributed teams.
- Hours and Boundaries
An After Hours Communication Policy You Can Write in an Afternoon
One page, five clauses, an afternoon. Sending is fine, replying is not expected, and the clause that makes it real says what to do when nobody replies.
- Handoffs
The Sales to Customer Success Handoff: Start With the Buyer's Own Words
The cost is the customer repeating themselves. Put the buyer's own words at the top, then the promises that are not in the contract.
- Async and Meetings
Where Written Communication Breaks: The Question That Sits Until Its Owner Is Back
The failure is not the writing. It is the question that sits until its owner is back. Two rules: what must be written, and what may wait for a person.
- Ops Operating System
The Hard Part Is Finding the Person, Not the Document
Org charts answer reporting lines, which is not what you needed. Build a who knows what list from questions people actually asked, with a second name per row.
- Async and Meetings
The Async Standup, and Why Written Updates Drift Into Theatre
The three classic prompts ask what you did, which nobody needs. Keep two lines: what changed, and what is waiting on whom.
- Ops Operating System
Most of That Searching Is Looking for a Person
Atlassian puts a quarter of the week into searching for information and answers. The answers half ends in asking a colleague, and then in waiting.
- Coverage
Coming Back From Leave: A 60 Minute Order of Operations
Do not start with the inbox. Decisions made in your absence, then open questions, then what is due this week. Inbox last, newest first, mostly archived.
- Handoffs
Account Handover Checklist: What Was Said, By Whom, and What Is Due
The CRM holds the deal, not what was said on the call. Six items, one page: commitments, what is due, who is who, sensitivities, why they bought, open questions.
- Across Time Zones
What Is the Follow the Sun Model, and Why It Strains Small Teams
Work passes between zones so it continues without night shifts. It lives or dies on the handoff, and small teams rarely have the redundancy it needs.
- Async and Meetings
Status, Decision or Discussion: A Rule for Every Recurring Meeting
Only discussion needs everyone live. Split the mixed meetings, run the written replacement for two weeks alongside, then cancel.
- Onboarding
Onboarding Across Time Zones: The New Hire Whose Buddy Is Asleep
A new hire stops every twenty minutes and the person who knows is nine hours away. Split the questions, front load the overlap, and write the defaults down.
- Across Time Zones
Rotating Meeting Times Is Fair. Having Fewer Meetings Is Better.
A rotation spreads the cost of a bad slot without reducing it. Classify each meeting, rotate only what needs live time, and write the rest down.
- Ops Operating System
How to Know Where the Work Stands Without Asking for Status Updates
You want one answer about one thing, not a dashboard. Let the person author the record, then read it when you need it instead of asking.
- 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.
- 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.
Older posts that fewer pages link to. Still the best answer we have on each topic.
- Decision Governance
Access Control vs Declaration
Access control governs what an AI can read; declaration governs what it can assert as true. Why you need both to deploy trustworthy, accountable AI.
- AI Agents
Accelerating Team Output With AI Without Replacing
Teams that replace human judgment with AI see a velocity gain followed by a quality cliff. Here's how to accelerate output by augmenting instead.
- Remote Leadership
Agency Client Communication: A Framework That Works
Most agencies lose clients not because the work is bad but because clients can't see what's happening. Here's a communication framework that fixes the opacity problem.
- Best Practices For Remote Teams
10 Essential Tips For Successful Remote Collaboration
Discover 10 essential remote collaboration tips to keep your distributed team productive and aligned across every time zone.
- Technology Solutions For Global Collaboration
10 Must Have Technologies For Cross Timezone Collaboration
The collaboration stack distributed engineering teams actually rely on. What closes timezone gaps, what creates new ones, and the one tool category most teams overlook.
Your team’s week, answered from the work.
See this on your team’s questions, not ours.