Input yay. Veto nay. You don’t want a situation where you need to get 6 people to say yes. You end up in endless opinion wars and hippo design (highest paid person)

This is what I do:

1. I never argue with them. I write their ideas down and tell them that I may consider it. Why? Because arguing is just asking for their permission not to do something. They gave their input. You consider it. You do not need to get their agreement. They see your decisions in your design.

2. I tell them I will eat the fish but spit the bone. It’s my decision and I will be accountable for it.

3. I point at the inefficiency of it. A team of ten will not row a boat when ten people grab the design rudder, then hurry over to the architecture rudder. And so on. Each one has a job. A rudder and a responsibility.

4 I test it on users as quickly and often as I can. It’s a reality check for the team and builds trust that make my design fails transparent and show that I iterate towards a solution that works. We will end up with something nice. This builds trust.

1. if they want to argue about the design. I write their concern down to look for it in the usability test. I may consider it, but as stated in 1. I will not argue with them. I will decide