[ganeshsridharan]

I learnt a technique from my previous managers that I follow to make decisions. It is called "Tenets".

Tenets are neither wrong nor right. They are laid out so that everyone knows what are some of the non-negotiables.

In your case, for example, you could come up with the following tenets 1. All of the code should follow consistent patterns 2. Speed of creating a new component should be less

etc.

Now once this is done, you can share these tenets to the group of the participants and ask them to rate their proposal on the tenets. Finally you can take an approach based on the ratings.

IMPORTANT NOTE in decision making: 1) Decision making is not a democratic process. So make it clear that who is the owner who is going to decide on the final solution. Everyone can share their opinion but there should be only decision maker 2) Based on the tenets you come up with, there could be cases where some of the points (like dash-case vs. camelCase vs snake_case) does not matter. In those cases, do not spend time on going back and forth. Just take a decision and mark it as final 3) Make it clear to the audience how you are going to decide (like the tenets framework), who is the decision maker even before going to the meeting and make sure they agree to those. 4) After a decision is made, send a summary email (or write a document) on how you took the decision and if there is a time to revisit it.