I think theory isnt enough; Testing (and tweaking) in real life is needed.
Even if those tests are done with limited functionality and scope.
Not sure what you have up your sleeve for such. I would think: Lower barriers as much as possible. Perhaps not include a token to be part of such setup.
Anekdote: earlier this year I met someone who is totally into Eigenlayer. He with 10 others did setup some art project. They shared the keys between the 11 founders. 7 keyholders need to agree to make changes to whatever they have secured with a key. When I understood this, I made the statement: "You likely need considerable time to get an ok, days if not weeks". His response: "Yea, we need to change things since we need weeks to get at least 7 peeps to act, and mostly we need to hunt them down to act". Why this little story? Because this is what needs to be taken into account: Most people wont be there when you need them. That is why I dont think for most decisions you can bank on a hour or few days A to Z, from debate to decision.
Above anekdote is perhaps the most important reason for me to suggest in field testing is required. And for that, some interesting (niche) project is to be created. Something that appeals to those participating. This can be anything. Could even be an small investment fund. Could be about decisions around HP of some account. Can be anything.
I wonder why 8? In law and finance and technology, always an uneven number is recommended.