I do this as a developer, although not because I have an extrovert bias (I think). I'd generally rather not, but when there are so many disparate stakeholders f

I do this as a developer, although not because I have an extrovert bias (I think). I'd generally rather not, but when there are so many disparate stakeholders for a particular issue then asynchronous planning and decision making just gets drawn out and stalls. The process keeps getting blocked by someone or other who is not responding or isn't available. This problem of actually having too many stakeholders for different problems I think tends to crop up because the organization or its systems are tightly coupled - 'spaghetti organizations' and 'spaghetti systems architecture'. If you don't have this you're lucky, I guess. Small startups obviously won't, some big orgs with talented and ruthless architects will stop it (Amazon seems pretty good at this). If you do, well, you need to deal with the problem somehow or you'll keep stalling. I've long suspected that Google, in spite of their reputation for having the creme de la creme of engineers, has a massive spaghetti code and spaghetti organizational problem, but this is just based upon bits and pieces I overhear. It's hard to know for sure.