[dataflow]

No, not every conversation is a "collaboration". Do you dial into Zoom during lunch and coffee too? When you grab a coworker passing by do you start a Zoom call to make sure the whole team can spectate your random conversation?

[dd82]

No, but you also make sure to bring it up in slack or whatever to fill in your other teammates when the material is relevant and useful. Or just because?

[dataflow]

That's... not how it works for any human being. The whole point of a conversation is that you can engage in it while it's happening. You make a point in the middle when it's relevant, and someone replies with something else they feel is relevant. When you've already had a 30+-minute conversation over lunch, no human is going to remember it and copy to Slack, no remote worker is going to go through and respond point-by-point as if they'd been there in person, and no human who has already invested that time and energy in the conversation is going to re-start the conversation at every juncture just to explore alternative directions it could've gone in person.

What actually happens in the best case is you give a few sentences of summary if you believe it might impact your coworkers' work, and then schedule a meeting if there's more to discuss. Which (ignoring the fact that even the best people don't always do this) is great, except you could be entirely wrong about whether there was anything beneficial for any coworker to hear. That junior engineer on the team might've been able to overhear how you fixed a problem that was second-nature to you, but now they don't. That dude who just returned to work might've been able to tell you they were interested in picking up the work you were overloaded with, but now they don't. That team lead on the adjacent team you would've grabbed during lunch with might've told you they were planning to handle the larger problem next quarter, but now they don't. etc...

[dd82]

that's where communication and collaboration strategies and procedures exist. It can be really easy to have them be mindless things, rather than mindful things. You can use your medium of communication, whether text, ad-hoc calls, or so on. No need to schedule meetings unless both parties are booked for ad-hoc chats

With some examples

* Hey, I was chatting with X a bit ago, couple things came up about service A and B. Got some time for a quick call?

* Hey, I can use a sanity check with this brainstorming session, got any time free? Oh, is Junior X available too?

Not saying your points aren't valid. But the same things would also happen if I were at my desk and you were off talking somewhere. How would you get me into the conversation?

The big difference is mindfulness, I think. Remote communication requires more mindfulness about team and communication, whereas in office you can be really lazy about that.

At the end of the day, its about communication and collaboration, and making sure loops are closed. Reasons for unclosed loops exist, regardless which environment you're in

[dataflow]

> the same things would also happen if I were at my desk and you were off talking somewhere.

Nobody claimed otherwise. The point here is they wouldn't happen when not "off talking somewhere". Like, you know, when there are more than 2 people grabbing coffee/lunch.

> How would you get me into the conversation?

This is indeed no different than when everyone is at the office and you decline to grab lunch with the rest of your team. You miss out in a similar fashion. And just like how nobody is going to replay the entire conversation to you over Slack and restart it at every juncture, nobody is going to do that for you in person... that's just how humans are. The fact that you are capable of missing out in-person in a similar fashion is not an argument for anything.