Software Company Team Rules 
September 19th, 2007
There is a company in Toronto that makes some pretty sweet microscopes and they have a sizable software development and manufacturing team. A few months ago I was visiting the company (I used to work there) and I noticed their new Team Rules poster next to the developers’ cubicles. I guess this is an attempt to foster a particular sort of team culture. What culture would this represent to you?
VisualSonics Team Rules
- We have open honest communication; no held punches.
- Discussions are about issues and ideas, not about personalities.
- We challenge each others ideas, we never take it personally.
- If a challenge becomes personal, we apologize, we accept the apology, and we move on.
- We challenge ideas openly, debate passionately, then we get the best decisions.
- We value the exposure of problems, it allows us to find solutions.
- We always support the group decision unanimously; one decision out of the room.
- 100% buy in = no unresolved issues = no politics.
- This is not a democracy.
- Issues, their action plans, time lines, and persons accountable must be documented.
I thought it was interesting that a lot of these rules are about consensus-building and decision making, but hidden away near the bottom (item 9) is a clear indicator that in fact they are not really that interested in consensus at all. Are these the seeds of a poisonous work environment, or the building blocks for a cohesive team? You decide. Are there team rules at your company? If so, what are they?
| 
Del.icio.us
This entry was posted on Wednesday, September 19th, 2007 at 7:26 pm and is filed under business, culture. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
Entries (RSS)
and
September 19th, 2007 at 8:46 pm
“This is not a democracy” just indicates to me that many ideas are put in the air, debated and then one decision is _made_ and not voted. Or rather all votes are not equal…which is necessary based on people’s experience, aptitudes and responsibilities. I think these rules are there so that everyone on the team understands what’s going and why, also everyone gets a voice but not everyone’s is counted equally. If these ruled are followed it would certainly avoid confusion and mixed goals in a team.
September 20th, 2007 at 12:27 pm
I think it goes without saying that a team of employees is not a democracy. I disagree that it clarifies how one should actually act in a team situation. If I’m in a position of authority, should I be dictatorial when I’ve made a decision or should I do as point 8 suggests and wait for 100% buy in?
September 20th, 2007 at 11:22 pm
I guess not being a democracy means that #8 is more like you will give 100% buy in when the dictator tells you to. I think that 100% can also be bad though since it makes people put on the old blinders.
I think one of the most important ones is “We challenge each others ideas, we never take it personally.” I like that one.
September 26th, 2007 at 1:53 pm
I like that point too, Dave. It builds characters and adds fire to the belly. Which is exactly where you want it.
October 16th, 2007 at 7:50 pm
It’s funny, since every group that uses consensus based decision making says that they are not a democracy. Democracy also equals Dictatorship of the Masses. In a democracy you won’t get 100% buy-in because someone will be against it. With consensus, it forces people to make decisions to be more rigorous than in a Democracy, when everyone just wants to get out of long meetings and will vote just to move on.
October 17th, 2007 at 1:20 pm
Good point, Joe.. I prefer to make decisions from an ivory tower myself.. which I am currently planning for construction across from the woodwards building, and will be pre-selling condos in beginning in January.