Great Expectations

Photo by Andrea Piacquadio

When nobody names an expectation, everyone invents their own and the loudest one wins. Response time expectations decide how your day feels. The result is typically fast replies, constant checking, and feeling like you’re always on call. If your workplace doesn’t have an organization-wide response time policy, then you can make your own.

What Response Time Expectations Are

Response time expectations are a shared understanding about two things: Which channel to use for which kind of message and when someone can expect a reply. That’s it. Uncertainty creates extra work. People double-message, escalate too early, and assume silence means neglect. Clarity removes a lot of that.

Why You Care

Setting response time expectations reduces your overwhelm. It helps limit context switching. It reduces relationship tension by aligning assumptions. When people know what to expect, they stop guessing and you stop feeling pulled in five different directions. A few minutes of distraction on repeat all day manifests as catch-up work, missed details, and sharper conversations than you intended. You need to make two decisions: What counts as urgent and which channel handles urgent messages. Once you decide those, the rest becomes easier.

When It’s Urgent

When you receive an urgent message, look for words describing impact and deadlines. For example, it should be about something like a customer is blocked, a system issue is affecting delivery, or a deadline happens today with an unpleasant consequence. When you send an urgent message, include the impact and the deadline. Prevent the panic urgency can cause with information your team can use.

Where to Send Urgent Messages

Urgency needs a direct route. Pick one path and use it consistently. For example: 

  • Slack for coordination and time-sensitive questions
  • Email for external communication and longer context
  • Project management tool for work requests that require tracking
  • Phone call or text for urgent issues

Your Personal Response Time Policy (PRTP)

Slack

  • Respond during working hours within 1 to 2 hours
  • Respond to tagged urgent messages within 30 to 60 minutes when possible
  • Check messages at set time windows you can commit to

Email

  • Respond within 1 business day

Work requests

  • Requests that require work go into the project management tool.  Messages should include context and the request gets tracked

How to Implement Your PRTP

Pick two to four check-in windows that fit your schedule. Put them on your calendar as short blocks, like fifteen to twenty minutes. For example, if your workday is 8:00am – 5:00pm then 10:00am, 1:30pm, and 4:30pm may work for you. Keep notifications off during deep work. During check-in windows, reply, prioritize, and assign next steps. This keeps you responsive and protects your attention.

How do you create a calmer day while addressing urgent issues? Please share in the comments.

For the extended article including Scripts that Deescalate, and A Copy and Paste Template sent right to your inbox, subscribe to my Substack.

Leave a Reply

Your email address will not be published. Required fields are marked *