[IxDA Discuss] design by committee??

[Wilson, Russell]

Thanks Robert.
 
Always, always, always explain the *why* behind design
decisions/suggestions you make, and be able to make design decisions on
a  
 
I agree, but sometimes given workload, it is tedious and possibly even
impossible to justify every little decision.  To be honest, I don't
want to add another meeting to my already full calendar to explain why
the button has to be orange versus blue, and why the font should be
Trebuchet instead of Arial.  
 
What we're trying to push/enforce in my company is having development
only give input about feasibility of designs (time to develop,
difficulty in implementing,
impact to existing code, etc.).  No data on how successful this will
ultimately be.
 
 
 
When I started with my current employer, there was one developer in
particular that debated everything. *Everything*. So I always  
 
Why is there always one (or more) of these?  why, why, why... :-)
 
 
made my case, tried to keep him focused on the dev side of things by
discussing how the design could be implemented, how the code could be
reused, etc. Basically, if I kept his mind on development and why my
idea was good for him, he lost interest in debating me and got more
interested in implementation. Eventually, he stopped debating me. He
still does on occasion, to a much less extreme degree, but for the most
part, he's learned that I know what I'm doing and has started accepting
my decisions verbatim. Now, he comes to me about almost everything.