Response-Time Norms and Subject-Line Signals
Encode urgency into shared acronyms and subject lines so people prioritize thoughtfully, not hastily.
- Difficulty
- Starter
- Time to result
- ~days to results
- Steps
- 3
- Confidence
- 80%
Dhawan offers concrete conventions that encode urgency into text so colleagues can prioritize thoughtfully instead of hastily. Because people can't read a raised eyebrow that says 'this is urgent,' teams invent shared acronyms — ROM ('respond on Monday') to protect weekends, NNTR ('no need to respond') to kill unnecessary reply chains — and embed response times directly in subject lines, like '2H' for 'I need this in two hours' or '4D' for 'due in four days.' These small conventions counter the tendency, worsened by message overload, to equate doing work with responding fast rather than being thoughtful and substantive, and they protect people from ruining evenings and weekends over false urgency.
Origin
Dhawan collected these conventions from client teams solving a shared pain: people felt compelled to answer a boss's 9PM email at 9PM, exhausting themselves, so teams engineered explicit signals for what actually needed a response and when.
Core principles
- 01People can't read a raised eyebrow, so encode urgency explicitly.
- 02Shared acronyms tell people when they truly need to respond — and when they don't.
- 03Putting response times in subject lines lets people prioritize at a glance.
- 04Reducing false urgency prevents burnout and ruined weekends.
How to run it
- 1
Adopt shared response acronyms
Introduce team-wide acronyms that signal response expectations: ROM for 'respond on Monday' so a Friday-afternoon message doesn't ruin a weekend, and NNTR for 'no need to respond' to eliminate reflexive thank-you replies.
Pro tip NNTR alone can save 15 unnecessary 'okay' and 'thank you' emails on an internal thread.
- 2
Encode urgency in subject lines
Put required response times in the subject line — '2H' meaning needed in two hours and urgent, '4D' meaning due in four days — so people can prioritize by scanning.
- 3
Reset what 'working' means
Use the conventions to shift the culture from prizing fast responses to prizing thoughtful, substantive ones, so people don't feel that doing work just means answering email.
Watch out Under message overload it's easy to prioritize hastiness over thoughtfulness because responding feels like working.
In the wild
A team created response-time norms in their subject lines: '2H' meant 'I need this in two hours, it's urgent' and '4D' meant 'this is due in four days.' Anyone could read the subject line and immediately know the priority.
→ People prioritized accurately at a glance and stopped treating every message as equally urgent, reducing overload and stress.
Common mistakes
Leaving urgency ambiguous
When people can't tell what's truly urgent, a boss's late-night email triggers a late-night reply and exhaustion, or a non-urgent item gets rushed while substance suffers.
Is it for you?
Best for
Teams drowning in messages who need lightweight conventions to signal true priority and protect off-hours.
Not ideal for
Very small or informal teams where shared acronyms would add ceremony without benefit.
From the transcript
“One leader started using an acronym called ROM, which meant respond on Monday. So if you send something on Friday afternoon, like you don't need…”
From the episode
Erica Dhawan: Digital Body Language, Effective Communication Strategies for the Digital Age
Erica Dhawan