What's one remote work habit your team adopted that would sound completely weird in a physical office?
I'll start.
I've talked to teams that:
Schedule a meeting just to ask a 2-minute question.
Wait hours to send a simple Slack message because they don't know if someone is busy.
Write long messages instead of just talking because they don't want to interrupt.
Spend 10 minutes figuring out who's available before asking for help.
None of these happen because people communicate poorly.
They happen because remote work removed something we take for granted in an office: awareness.
When you can see the people around you, hundreds of tiny decisions become effortless.
Without that context, every interaction has friction.
I'm building RovaSpace because I think bringing back that shared awareness is more valuable than adding another communication tool.
I'm curious...
What's the strangest remote-work habit your team has developed that would never happen in the same office?
right
The one that stuck with me: people start narrating their own status like they're a live stream. "Just stepping away for 10, back by 3" in a channel nobody asked about. In an office, you'd just see the empty chair. Remote, we've turned presence into something you have to announce, which is its own kind of tax on everyone's attention.
The meeting-for-a-2-minute-question thing is real too, but I think it's actually a trust problem wearing an awareness costume. People schedule the meeting because a Slack message with no context feels like it's demanding an instant response, and nobody wants to be "that person" pinging at the wrong moment. Bring back the ambient signal (busy/free/heads-down) and a lot of that anxiety disappears on its own.
Following this closely.
That “status narration” behavior is a great observation. It’s basically a workaround for missing context signals—people recreating the ambient visibility that exists naturally in an office.
The trust angle is underrated. It’s not just async vs sync—it’s uncertainty about availability, which pushes people either to over-explain or default to meetings as the “safe” communication path.
If teams had lightweight, reliable signals for focus and availability, a lot of that friction would disappear without increasing messaging load.
Do you think teams would actually adopt something like that again, or has chat culture already normalized explicit status updates as the default?