<aside> 💡 To set the stage, it might help to read about why we are Avo is remote-first and async-first [public]

</aside>

Tiers of urgency

<aside> 💡 For added context on how to use our Tiers of Urgency it might be helpful to read Our tools of communication [public] after this page.

</aside>

In general, if when folks break this protocol:

Don't assume malice, but make sure to give them feedback and offer to help. The feedback should include the impact of their failure to meet your expectations, and an offer to help move this forward.

SHARE INFORMATION (ASANA):

Desired acknowledgement time: The next day or so.

Impact on recipient: Processing the information takes >30 seconds and potentially requires task switching. Response isn't needed, but it's fun to get the general "yay" or "hoorah" or "wowsa, thanks for sharing"

ASK (ASANA):

Desired acknowledgement time: Within 24h (excl. weekends and holidays).

Impact on recipient: Processing the ask may take >30 seconds. Responding may require task switching.

TIME-SENSITIVE ASK (SLACK @-MENTION WITH 🐢 PREFIX):

Applies to both @channel and @[person].

Desired acknowledgement time: Within 3 working hours

Impact on recipient: Processing the urgency of the ask can be done in the message notification preview. Processing the ask takes <30 seconds. First response can be completed in a 5 min break between focus sessions or meetings.

URGENT ASK (SLACK @-MENTION):

Applies to both @channel and @[person].

Desired acknowledgement time: Within 30 minutes during working hours.

Impact on recipient: Processing the urgency of the ask can be done in a push notification preview. Processing the ask takes <30 seconds. First response can be done in minutes.

ASK FOR RESPONSE OUTSIDE WORKING HOURS (TEXT OR WHATSAPP)

Desired acknowledgement time: Same day, preferably same hour.

Impact on recipient: Responds even if outside work hours.

DROP-EVERYTHING-ASK (CALL WITHOUT WARNING)

Desired acknowledgement time: Seconds.

Impact on recipient: Responds even if outside work hours.