The “joys” of design by committee. Trying to please everyone stinks. It’s frustrating and probably impossible. It often ends in a too-many-cooks-spoil-the-soup story. Designing by committee usually ends in lackluster results that no one really wants. Often, a committee is made for the sole purpose of blaming and finger-pointing after the fact. Ugh!
What happens in committees? Some people are no help at all. They just want to argue or make sure something they suggest gets included. Comments such as, “I don’t like the green,” won’t help anyone.
Talking can only take you so far. Sometimes during the design process, your committee will run into disagreements. How can you stay away from committee members personal opinions and biases?
Keep egos and politics in check. In meetings, someone is always dominating the conversation. We like to call them Bullies. They love to challenge every decision that has already been made, and feel a need to jump in and stir things up. The designer may end up making design changes on-the-fly. Bad changes.
“I’m not stubborn. It’s just my way is best.” How can you avoid the Bully having too great of an influence? How can you get back in control of the project? You can nip the pushing and pulling of personal opinions in the bud. There is no need for arguments. You can keep things moving along. What is the secret?
Never show the design and ask stakeholders, “What do you think?”
That’s the kiss of death.
They need to become aware that it’s not about them. It’s about how their web audience feels about the design. The market is not the web owner’s clone.
Conflict prevention for web development. You can anticipate and spot stakeholder problems before they occur and resolve them quickly when they do. You can mediate before the conflict even begins.
Good design leadership can prevent disputes before they happen. Arguments are inevitable, necessary, and even desirable in web development work. Conflict can be a turning point. Disagreements are productive, as long as teams avoid personal and emotional aspects.
The way to handle team conflict is with skill and confidence. You can encourage people to be open, exchange ideas, look for alternatives, and check out differences. Keep the team focused on solving the web problem, not on the personality problem. Decisions get made by entertaining different viewpoints without the pressure of stakeholder blackmail.
Frequently, web team members or stakeholders who voice a negative opinion simply can’t explain why. You need to hear more than, “I don’t like it.” There are ways to reduce unproductive or wasteful debates. You can keep your web project on track and on time.
Final results everyone can live with. Consensus means overwhelming agreement. It’s an honest effort to meet the interests of all stakeholders. Consensus is when everyone agrees they can live with the final results.