Thread: team hierarchy
View Single Post
  #4   Spotlight this post!  
Unread 15-07-2003, 23:14
Woodie Flowers Award
Ken Patton Ken Patton is offline
purple
FRC #0051 (Wings of Fire)
Team Role: Engineer
 
Join Date: Jul 2001
Rookie Year: 1997
Location: Pontiac, MI
Posts: 338
Ken Patton has a reputation beyond reputeKen Patton has a reputation beyond reputeKen Patton has a reputation beyond reputeKen Patton has a reputation beyond reputeKen Patton has a reputation beyond reputeKen Patton has a reputation beyond reputeKen Patton has a reputation beyond reputeKen Patton has a reputation beyond reputeKen Patton has a reputation beyond reputeKen Patton has a reputation beyond reputeKen Patton has a reputation beyond repute
define responsibilities

Foley-

Jeff is right, there is such a thing as too much organization. My opinion is that you should build the organization around the goals that your team has set - don't build the organization before setting the goals.

If people are getting hung up on their job title it can sometimes be a problem - maybe "responsibility" is a better way to think of it than "title."

One idea that I think is very important is to CLEARLY define what responsibilities people have, and DON'T make two people jointly responsible for something. If one person is responsible, they don't need to have a meeting/discussion/argument to make a decision (unless, of course, they are schizophrenic, but thats an entirely different problem ).

hth,
Ken
Reply With Quote