We've been hanging out at the collaboration bar for a bit of time now, which means that we've seen a few different customers take stools, saying *theirs* is the only drink to order. They down a few and poof! they're gone.
Some have stuck. For at least a decade and a half, communities of practice have held their seat. Ever since Etienne Wenger (hello, old friend) coined the phrase in his and Jean Lave's 1991 book, Situated Learning, savvy organizations have been promoting their use. Among the first was Bob Buckman, then CEO of Buckman Labs, the specialty chemical company, who turned his entire organization into one gigantic global community of practice years before most reading here even had email accounts. We documented Bob's story in Virtual Teams--and, perhaps more importantly, he documented it himself in Building the Knowledge-Driven Organization.
Not long after people in the collaboration community (which will have to be a subject of another post someday) started to use the term "communities of practice" came its partner-in-crime, knowledge management, whose history Karl-Erik Sveiby, the Swedish writer and consultant, has been tracking for years.
Comes then a whole sector of the tech industry focused on making it easier for people to "manage" their knowledge, a concept that bears reflecting upon elsewhere (is knowledge manageable as, say, people are? - I'll let that one go for now). Also comes then all manner of upstart efforts within organizations to swap learning as fast as possible, often without their employers' imprimaturs.
Among these were two majors in the US Army, Nate Allen and Tony Burgess, who, without sanction or budget or business plan, started Companycommand.com. There soldiers could exchange, well, war stories. A good summary of their experience is documented in the Government Executive article, "Managing Technology Linked in the Fight," which was laid out in detail in the 2005 book, CompanyCommand: Unleashing the Power of the Army Professional, which the two majors along with two others co-authored with Professor Nancy Dixon.
All of which is a windy introduction to the fact that the US Army has a long, rich history in communities of practice with now probably tens of thousands of online forums where soldiers of every rank can exchange information in a timely way.
So it was that the Army held its 3rd Annual Knowledge Management Conference last week, where we, along with Dr. Dixon and others, gave talks, ours titled The Transformational Power of Networks, Teamnets and Virtual Teams. Lots of discussion about communities of practice, knowledge sharing, semantic webs, and all the other topics that IT professionals, learning experts, and the top brass, whether those with stars on their shoulders or big paychecks, worry about.
OK. What's next? Jeff and I came away thinking about this: perhaps the era of the community of practice needs to morph a bit. Aren't we now in the time when teams, not just amorphous communities or lone-ranger individuals, need to share practices? And isn't the technology up to the task, what with virtual (or, if you prefer, global) teams exploding everywhere and wikis for teams going up on the web faster than their IT departments can track them? Teams, we think, are the way to work (without diminishing the genius and creativity of the individual), the hope for solving the seemingly intractable problems that sometimes make it hard to get up in the morning.
Thus, we invite a new customer to the collaboration bar: Teams of Practice, the title of this post.
