Teamwork
April 5th, 2007 | by Sean |I thought of these today. They probably need refinement.
Sean’s three rules on teamwork:
- Announce success. Listen to other’s successes.
- Announce failure. Listen to other’s failures.
- In the absence of clear direction, set your own direction and go. Announce. Listen.
(False) modesty creates tribal knowledge. At the risk of sounding immodest, tell your team members what cool thing you’ve done. You don’t need to scream it from the rafters, just make the knowledge available. Likewise for failures. Do not wait; share your findings. I call this “continual process improvement.” Similarly, if you run out of things to do, feel free to push the ball of progress forward and be sure to tell everyone what you’re doing.
Here’s my fourth rule if you’re a team lead (I’m not one — yet):
- Set a goal. Lay down a challenge to your staff to meet or exceed this goal.
Software Developer, Consultant, and Geek.
One Response to “Teamwork”
By ECH on Apr 7, 2007 | Reply
What I have learned so far as a Project Manager is that you need to allow your staff to come up with solutions to a problem but your have the altimate decision which helps push the team foward. Also I agree the most with your 4th rule.