No ?
please don't reply with just "ok" to something that deserves more
Imagine spending five minutes writing a detailed plan, and the only response you get is "ok"... 🤦♀️
❌ Don't do this
Thomas Middleditch thought he was being efficient: short reply, message received. But "ok" to a multi-part message leaves the other person guessing what exactly was acknowledged and what was agreed to.
Most people who do this don't mean to be dismissive. It's a reflex: "I read it, so I'll confirm with the shortest possible reply."
But when someone writes a detailed plan, a dry "ok" feels like it wasn't read at all. It creates ambiguity, frustration, and often forces a follow-up message just to confirm what "ok" meant.
The same goes for:
- k
- got it
- noted
- sure
- 👍 (as the entire reply)
Match the effort of the message!
✅ Instead, try this
Echoing back the key points takes ten extra seconds — and it confirms that everyone is aligned, not just that someone saw the message.
Instead of a dry "ok", try:
- Confirm your part: "I'll handle X by Thursday"
- Acknowledge the plan: "Friday 2 PM works for me"
- Add something: "Sounds good, let's sync before the deploy"
- Ask if unclear: "Got it — one question: who's running QA?"
Effort in, effort out. When someone writes a thoughtful message, a thoughtful reply shows you actually read it. That builds trust.
When done right, everyone knows the plan. 🎉