login
Blurts on the Art of Software Development

Today | RSS | RDF | Atom | Other Tags
Categories : All | All | CI | .NET | General | Humour | Java | Personal | Reviews | Ruby | SW Eng

This part of Brad Appleton's post in the Crystal Clear Yahoo! group grabbed my attention:

I've seen many teams that claim to be driven by "consensus", but they really aren't. They instead do a "majority rule" where, as long as say 75% or more agree, then the proposal is accepted. The minority gets silenced and their issues don't get discussed.

At first, it may seem like a good idea to follow the democratic vote -- after all, democracy is a Good Thing™, right? However, thinking about it further, going with the majority vote might not be the best way to go. Next time when you're voting on something among your team, spare a moment to think about whether a majority vote decision is your best option. It might be, or might not be. Your call.

The worst case? You might end up realizing later that it was indeed a step to the wrong direction when you've already eroded your team into a group of politicians.

Well, not really. But she did use the word "tablespace" yesterday while we were walking home from downtown (not all the way home -- too cold...), which kind of freaked me out.

She's a marketing manager. She's not supposed to say "tablespace".

Ok. You got me. She didn't really use the word "tablespace" but the Finnish translation, "taulualue". And she used it to refer to an area (alue) of paintings (taulu) on the wall...