Daniel R. Team Projects

To give a person the responsibility to do something is reasonably simple, but to hold them accountable to complete that task is much more difficult. It sounds very simple, team members are assigned a task, and they are responsible to have it done to the best of their ability by the deadline. If you get to choose your team members, then it is important that you pick them wisely. This is important because you want people in your team to have good communication, responsibility, and accountability. I found five tips for effective team project accountability from an online source that I think is good to know when you are in charge of a team project.

#1 Define the team and each person’s responsibilities
This may sound obvious, but sometimes a person knows only their little corner of the world, and therefore doesn't realize how their role impacts other roles, project deadlines and the results.
#2 Assign tasks and make them visible among the team
The keyword here is VISIBLE. If nothing else, ego motivates! We're not talking about "big brother" or micro-management, but just a general awareness. For example, if the architect is holding up the job, the general contractor wants the client to know the architect has things on hold. And more importantly, the contractor wants the architect to know that everyone knows the architect is holding up the job! (follow that?).
#3 Use a defined communication mechanism
Documentation and communication are important, especially when deadlines are missed or the project is delayed. So put in place a "public" (to the team) place where team members can contribute current statuses, updates, or issues, and in doing so, inform other team members. Use a system that automatically updates other team members. By the way, this will also provide an "audit trail" if needed at a later time.
#4 Engage the end-user/client
Who is the project being implemented for? An outside client? An internal department? Make these people part of the team. Of course, no one wants the client to know everything! So put in place a way for the client to view only what you enable them to view in regards to project status, issue management, job completion, etc.
#5 Eliminate excuses!
No more "I didn't know that" or "You never told me"! In your communications, implement some form of "Acknowledgment" process, so no one can ever say they didn't get the message. By keeping a historical log of Acknowledgments, you'll eliminate excuses - well, the valid ones anyway!

Source: http://ravenyoung.spaces.live.com/blog/cns!17376F4C11A91E0E!3301.entry