Sounds like a recipe for very slow development to me.

If you have a medium-sized system, and if in order to work on that system everyone needs to understand everything, then your architecture is a complete failure.

The idea that people can sit there in a two hour meeting and hear people talk about issues, and remember that and use it operatively and effectively: this idea is not convincing. Listening to two other people talk about some problem you don't understand yet, in a situation where you aren't being asked to do anything, does not actually teach you any new information at all.

And how then do you onboard new people? Show them videos of your meetings?

I have a prodigious memory, and yet I try to avoid using it in production projects: I rely on reading the code, and documentation.

The key to having different people work together on a medium or large project is NOT to have everyone have to know everything all the time, but to have decent documentation, and for people to learn the new material from that documentation when they need it.

And yes, this means sometimes you have to stop before you assign a new person to write a new feature, and write that documentation. That's a good thing, and it means as further people come on board, you can simply show them the documentation for the area they need to work on and they can go.