Personally I doubt that having face–to–face meetings is ever truly necessary. Once everyone in the group has thought of several ideas, they can write a page or two description of it and why they think it is a good idea. Then the decision makers (which obviously might be the same group) can read those papers and decide between them. Mozilla used to work something like this specifically to allow contributions by volunteers outside the company (no idea if they still do though). The Rust programming language is developed in a similar way: anyone can write an RFC to propose making a change to the language (or the associated tooling, the standard library, etc).
Keep in mind that I never mentioned face-to-face, I just asked for synchronous time.
That being said, I'm open to explore the idea, I think I already do this for a certain subset of problems using Slack threads
> And it overlooks the fact that people might build on top of each other,
In the research that I read, the researchers came to the conclusion that most of the meeting time went to building consensus instead of actually thinking of new ideas. Some subset of the people in the meeting would be charismatic enough to dominate the discussion, and everyone else would contribute less than they otherwise would have.
Links to any research on this? Anecdotally (about a decade working across different sized orgs in various roles from IC to Staff Engineer), this simply does not pass the smell test for me.
I love the idea of async, but there are just some sessions that are incredibly valuable and develop on others thoughts, evolving in a final solution.
At the company I work at, we compromise with a specific 4 hours overlap so that meetings can be scheduled only during those times