# Asynchronous collaboration survey

Make handoffs clearer across different working hours.

If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.

## 1. Which update needed a live explanation?

Answer: ____________________

## 2. Where do written requests lack context?

Answer: ____________________

## 3. What response window would help?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. An update requiring live explanation reveals what a written handoff failed to communicate. Preserve the missing context rather than judging the sender.
2. Missing written context identifies what recipients need to interpret a request without an immediate conversation. Include the relevant purpose, constraints or next step, rather than equating more documentation with effective collaboration.
3. A helpful response window identifies timing expectations for work across different hours. Agree appropriate urgency exceptions instead of assuming everyone can respond immediately.

Interpretation caution: Slow replies may reflect agreed working hours.


## Illustrative finding and follow-up

Observation: Requests omit deadlines across time zones.

Action to test: Add context and deadlines to handoff notes.

Follow-up: After trying the change, repeat “Which update needed a live explanation?” with people who experienced it. Check whether they still describe the original issue: requests omit deadlines across time zones. Compare explanations and sample context, rather than claiming the change caused an improvement.