No ?
please don't override a teammate's priority by pointing at the clock
Imagine a manager calls something urgent, the dev jumps on it, and another manager replies with just the day and time to silently say "no"... 🤦♀️
❌ Don't do this
Monica Hall didn't write "this isn't urgent" or "let's push it to Monday". She just dropped a timestamp. "Friday 16:15" isn't a status update, it's a power move dressed up as one.
It's a sentence with no verb and no opinion, so there's nothing to argue with. But everyone reads it the same way: "we shouldn't be doing this right now", with the bonus of making the other manager look unreasonable for calling it urgent in the first place.
Most people who do this wouldn't say the same thing out loud in a meeting. In chat it feels light, almost neutral. But it isn't. It does three things at once:
- Overrides a peer's prioritization without actually proposing anything
- Puts the dev in the middle of a turf moment they didn't sign up for
- Makes any reply ("it's fine, let's ship it") sound defensive
The same goes for:
- "EOD on a Friday 👀"
- "interesting timing"
- "this couldn't wait until Monday?"
- Pinning the clock instead of the decision
- Quoting work-life balance to win a scope argument
If you disagree with the priority, say so. Don't weaponize the timestamp.
✅ Instead, try this
Backing a peer's call costs nothing and turns a tense moment into a team moving in the same direction.
If you actually think the priority is wrong, that's a real conversation — have it. Don't fire a timestamp into the channel and let the dev sort out the politics.
Instead of dropping the clock, try:
- "go for it, ping me if you need a hand"
- "I can pair with you on the infra side"
- "DM me if you hit anything blocking, I'll unblock"
- "if you want, I can take the customer comms while you focus"
- "I disagree on priority, let's sync 5 min before you start" (privately, not in the channel)
Support in public, debate in private. Disagreements between managers belong in a quick DM or a call, not as a passive-aggressive timestamp dropped on the engineer who's already opening their editor.
When done right, the team feels covered, not caught in the middle. 🎉