2 ms·
Recently read a breakdown of the three main stages of team formation and the subsequent management styles needed - Survival (Crazy deadlines, lack domain knowl
by lifeisstillgood 13y ago
Recently read a breakdown of the three main stages of team formation and the subsequent management styles needed
- Survival (Crazy deadlines, lack domain knowledge.under resourced). Style : command and control, with aim to clear enough time to get to
- Growth ( Adequate time, domain knowledge) Suitable for learning and experimenting with new methods and tech. Style:
Coaching: needs structure and encouragement to reach new skills and potential
- Self-directed: individual team skills top notch, good domain knowledge and sufficient time to experiment. Style: facilitation - check in from time to time, discuss whys of strategy etc
It seems pretty clear GitHub is in the third category - but they did not get there by having a crazy management structure - they got there by being a skilled team, that then was able to attract and hire equally skilled people. They never found them selves with dumb coders who needed to learn something other than Java and don't know why source control is useful. So because of that they did not grow layers of management as a form of duct tape holding it together, and because of that they found no need to add in those layers once management stuff needed to happen.
The problem is of course that most in house software departments are thus massively over staffed if the coders are good enough to be self directing, and if not the coders are bad enough that you need to stop and skill up, but which managers are going to say "these guys and this environment is pants, hire some good coders and you won't need me, please can I print out a CV?"