Asynchronous Collaboration Norms Audit

Welcome to the Asynchronous Collaboration Norms Audit. This survey explores how your team communicates and collaborates asynchronously — including tools, expectations, and challenges. Your responses will help us identify what's working well and where we can improve. This survey takes approximately 6–8 minutes. Your participation is voluntary, and you may stop at any time. There are no right or wrong answers — we're interested in your honest experience. All responses are confidential and will be reported in aggregate only. Please click 'Next' to begin.

Does your current team have written norms for asynchronous collaboration (e.g., response windows, preferred channels, tagging conventions)?

• Yes, clearly documented
• Partially documented
• No, not documented
• Not sure

In the past 4 weeks, how clear were expectations for response times when working asynchronously?

Which tools does your team primarily use for asynchronous updates and decisions? Select all that apply.

• Email
• Slack, Teams, or similar chat
• Project boards (e.g., Jira, Trello, Asana)
• Docs/Wikis (e.g., Google Docs, Confluence, Notion)
• Video messages (e.g., Loom)
• Internal forums or Q&A
• Other

Does your team have agreed-upon focus or "do-not-disturb" hours to protect asynchronous work time?

• Yes, and they are generally followed
• Yes, but applied inconsistently
• No, but it would be helpful
• No, and it's not needed
• Not sure

What is the typical expected response window your team sets for asynchronous messages?

• Within 1 hour
• 2–4 hours
• Same business day
• 24–48 hours
• 3–5 business days
• No defined window

In the past 4 weeks, how overwhelmed did you feel by the volume of notifications and messages in your asynchronous channels?

Thinking about the past 4 weeks, how would you rate the overall quality of asynchronous updates you received from your team (e.g., clarity, completeness, actionability)?

How satisfied are you with your team's current asynchronous collaboration practices overall?

Rank the following asynchronous collaboration pain points by their impact on your work (1 = highest impact).

1. Unclear ownership or next steps
2. Too many channels to monitor
3. Missing context or documents
4. Slow response times
5. Notification overload
6. Duplicate or conflicting work

Briefly name one channel, tool, or practice that works well for asynchronous collaboration on your team.

What one change would most improve asynchronous collaboration on your team?

Based on your responses, we'd like to explore your experience with asynchronous collaboration in a bit more depth. An AI moderator will ask you a couple of brief follow-up questions.

What is your primary team or function?

• Engineering
• Product
• Design
• Data/Analytics
• Customer Support/Success
• Sales/Marketing
• Operations/Finance
• HR/People
• IT/Security
• Other/Multiple

Are you a people manager?

• Yes
• No
• Prefer not to say

How long have you been with the company?

• Less than 6 months
• 6–12 months
• 1–2 years
• 3–5 years
• More than 5 years
• Prefer not to say

What is your primary work region or time zone?

• Americas
• EMEA
• APAC
• Multiple/Rotate
• Prefer not to say

Approximately how many people are on the team you collaborate with most asynchronously?

• 1–5
• 6–10
• 11–20
• 21–50
• 51+
• Not sure

Thank you for sharing your feedback! Your responses will be analyzed in aggregate to help improve our team's asynchronous collaboration practices. Results will be shared with team leads within the coming weeks.