I supervised an entire PhD remotely many years back. We made it work, and learned as we went. Over time we got better as expressing confusion, double checking understanding, and all those sort of things where we use non-verbal clues in face-to-face meetings. It worked, but it wasn't an easy path at first. But there was an unexpected plus side - I'd learned to vocalize my doubts and confusion better, and to double-check we're on the same page. And so ever since I've found I'm more effective in face-to-face meetings.
That's funny but it reminds me of my relationship in the beginning. We didn't speak each other's native language fluently. Unexpectedly, harder communication had the effect of being clearer when expressing ourselves, and double-checking assumptions before reacting. It ended up very healthy.
Personally, while I agree that the bandwidth is higher locally, I don't agree you are prevented from expressing what you wish by communicating remotely; it just takes a bit longer, which is more than compensated by the time saved on other things.
Having an easily accessibly video conference software, committing to getting employees good headsets, and enforcing videos on/1 person per screen makes collaboration very easy.
----
The only thing that's missing is whiteboarding sessions (which seem to be more about fun than actual productivity). Instead, we typically ask a single engineer to write up a proposal doc then have everybody comment on that.
It requires a bit more lead time - write up, feedback, then finalization. However, the actual developer time is significantly less. One developer doing most of the work, with others chiming in periodically.
But I'm not a huge fan of whiteboards in general. Of course one problem with offline whiteboards is that the information tends to get wiped away (unless someone's snapping and uploading photos), the other is that they tend to be messy and unsearchable and hard to edit & update afterwards.
IMO it's generally better to flesh out ideas in text. It's just that sometimes a figure or two, maybe a flow chart, would get the point across quicker. I haven't found software I like enough to consider it better than hand, but hand sucks too. I often brainstorm on paper, and run out of paper or end up having to squeeze stuff because I didn't start with things in the right place. A software solution would help.
The main problem is the price, we can hardly afford one for each person, especially since it's not exactly something we use daily. Plus, even if we did, I'm not sure there's anyway to sync them in real-time.
IME unless your a particularly good teacher then your whiteboard isn't as high bandwidth as you think anyway. In face to face meetings everyone will just smile and nod because you have to go away and dig into the details to find issues. Put it in a graphviz drawing with the accompanying text and you'll get better results.
For example, if you are designing a very complex system requiring multiple participants then it's very very hard to communicate your ideas over video conferences - even when tech worked flawlessly. It's not because people are not able to articulate the ideas but there is a lot goes on in body language, facial expressions and quick back-and-forth exchanges over whiteboard. The high bandwidth of occupying same physical 3D space permits speedy iterations while low bandwidth constraints what you must express in given slot you are expected to express.
So, remote work doesn't work for all scenarios. It works well when everyone knows things fair bit, number of iterations during communications needed are small and number of ideas don't need huge bandwidth. It doesn't work as well otherwise. For example, early days of startup where the product is in embryonic state, everybody working remotely would not work out well. However, if product is mature and roadmap is well under control then remote team might work great.