Reorg and communities

Once in a while usually after a re-org exercise I get to be part of discussions around forming a community. Depending on who gets what after a reorg, suddenly the idea of forming a new community pops up. A new name, new objectives, new branding, new enthusiasts etc…

Shawn’s test http://www.anecdote.com.au/archives/2006/02/will_the_commun.html on the sort of identity that reverberates within at least a set of people is crisp and possibly can stop forming of those mushroom communities that will die down before the next re org.

Why dont people get it!!! your dominant identity is not your new org structure bucket?

Brain Drain ++

Dr Dan http://it.toolbox.com/blogs/dr-dan/lets-all-play-the-brain-drain-game-24159 here notes about brain drain, the “process” and the act of “capturing knowledge” with a luxury of time.
The real problems in a “typical” software services company where you do not have much future visibility on either people or the knowledge need are
the above plus
a time compression
and key people leaving repeats itself before the close of a contract (not so often if you are a lucky PM)
This is in addition to trying to optimize a firm for the one $$$ variable (reduce costs) when “billability” is given the most priority over all other parameters (suitability, contextual continuity, quality …) and further brain drain is orchestrated deliberately as well.
Any strategies, suggestions???

Phone Chord

The length of phone chord in enabling support engineers to work knowledge effectively has to be applied to AMS projects or in cases where continuity between dev to support teams. So the seating arrangement has to be designed to decrease barriers in face to face communication

From The Social Life of Information