My aim was to contrast traditional KM of conscripting best practices, with a new approach based on sensemaking pkm and networks…more appropriate tools, design for emergence and ambient awareness, and amplifying how we get things done offline…basically a more cognitive science approach over management science.

A great deal of my visual concept is based on the work of Dave Snowden, who looks at KM from a more anthropological, human behaviour perspective…a lot of his work deals with the notion of “context”, and I guess this is coupled with “intrinsic” motivation or engagement.

I also borrowed from a model by Shell on the concept of a Global Network (CoP), shown to me by Mark Bennett from Learning Collaboration.

Basically, from another perspective, I’m trying to do in 2 slides what T Systems did in 26 out of the 51 slides of their brilliant slidedeck, The revolution of knowledge part1

KM as blood bank

I also really like Mark Bennett’s symbolic way of thinking about it like a blood bank (taking and giving blood)

• Sense-making and asking questions (taking blood)
• Blogging/Sharing/Peer Assist and reflective KM like AAR, Lessons (giving blood)

Sense-making KM and CoPs - Just-in-time vs Just-in-case

The following slides are a contrast to supply-side KM, or just-in-case KM.

Also note this is KM from a Community of Practice perspective, as that’s what’s relevant to my day job. I guess one day I can alter them to include other KM activities and a more network perspective.

Sensekmaking KM and CoPs - Just-in-time vs Just-in-case

Different ways of engaging knowledge

Related to this sense-making concept of people and context in the just-in-time KM model is Nancy Dixon’s model on the different types of knowledge needs or interactions, in relation to: the level of cognitive diversity required, the degree of relationship (tie/trust) with others to source that information, facilitation/support, and the social computing tools that can create conditions for sense-making.

Embedded KM

Another related post is on Embedded KM by Andrew Gent.

I think knowledge sharing can be done as it happens (blogs, wikis, etc..) but also as a reflection (anecdote circles, AAR, etc..), and it’s the latter that Andrew is thinking about…how best to share lessons and good practices from one project to the next. Since the project is over, people don’t put great emphasis or care on reviewing it, as they are busy moving on to the next project, so Andrew talks about embedding this so it doesn’t seem a chore.

But he also makes a very relevant point to the heart of KM and motivation. When capturing information it has to become usable, and this takes effort on the contributor to make it findable, otherwise it’s up to the user to find the content and make it relevant to them. To make it usable and relevant takes too much effort for return, it has low intrinsic motivation for the contributors.

The challenge is a sweetspot where it’s usable enough, and contributing is simple enough…and what do you know, this works best as conversation, as we get sharing and context. And Andrew has an embedded way to trigger this reflective conversation as a part of an organisational process.

Andrew says:

“Rather than trying to make all project knowledge available to anyone, what if we simply try to expand the current knowledge base incrementally over time? Rather than collecting the review documents, why not include at least one reviewer from an unrelated project to each review? This could be an architect, implementer, or project manager as long as that person can provide an objective, outside view of the project progress.”

“…the outside reviewer helps to keep the project team “honest”. It is easy for internal reviews to become formulaic rubber stamp events if those involved are all working on the project.They do not have enough distance to see hidden pitfalls and will resist calling foul on people they have to work with on a daily basis.”

“…including outsiders gives at least one person a much more indepth and personal knowledge than could ever be gained by reading a set of historical documents with no one to explain them. Another value from a KM perspective is the opportunity the reviewer and the project team have to exchange knowledge, hints, and tips on the fly and in context of the discussion.”

“…the program then becomes essentially self-managing from a KM perspective. The project management teams are responsible for ensuring outside reviewers are included and with each review, little by little, knowledge is shared across the organization.”

Competitive vs Collaborative culture

The micro intentions or local behaviour involved in the the Just-in-time vs Just-in-case concept actually emerge a macro picture…and that’s a change in the internal dynamics of an organisation from a competitive to collaborative organisation…perhaps from teams to crews.

Why?

We create the conditions for engagement, transparency, agility, trust and awareness…where knowledge sharing becomes a magical by-product….not creating a knowledge sharing culture, rather creating conditions for one to emerge.

I know it’s about the people, not the tools, but it’s important to understand the design thinking involved…these new tools are designed for the people, where we can now achieve the original aims of KM. The use of these tools can be a catalyst for change. For more on this see my posts, Has KM died, and resurrected as social computing?, Knowledge and its facilitators.

You could say social computing is a bottom-up strategy (and is has total effect when enterprise-wide), but I think we can also have a top-down strategy, because no matter how enabled workers can be to express and converse in the open, they will be hesitant, feel unsafe, uncomfortable and not confident if this new type of enterprise interaction is not promoted or pushed from the top.

NOTE: social computing is not just bottom-up, managers can seed crowdsourcing/opinion/reviews

A while back I posted, Is knowledge sharing all about your pay cheque? (which was amplified by Stewart Mader).

In this post I contrasted a picture where people are influenced to share or hoard depending on how their performance is viewed from senior management.
If you are appraised on your personal output, then you will hoard and not collaborate as much as you have an incentive to own all the output, forgoing a more quality or optimum deliverable, than if you were to leverage the talent of the organisation.
On the other hand if you are appraised on a group output (how much you collaborate, your effectiveness in networking with the optimum people for your tasks) then this will instill a less competitive culture due to more knowledge sharing and collaboration. This is a cleverly designed strategy as the the workers themselves will be pushing quality from others as they all hold each other accountable…a culture of interdependency.

I really like how Stewart put it:

“People are used to thinking of their workday activities as indirectly affecting the bottom-line because the competition model essentially keeps the average employee in the dark about how things really work, or how healthy the organization is. The sharing model makes it much clearer, so the average employee can see the impact of her or his work.”

Betrand Duperrin also parallels these thoughts:

“They would be more efficient if they helped each other? But in order to get a good evaluation and the related rewards and bonuses they have, in the best case, to ignore each other, in the worse case to play the one against another.”

Learned behaviour

Beyond performance appraisals, what about a top-down message about the importance of connection and collaboration, just like the way organisations drill the message of quality and safety.

When I attended Mark Bennett’s masterclass on CoPs, he mentioned that safety is a learned behaviour (people are irrational and do unsafe things like drink driving, etc), and quality is a learned behaviour (people take shortcuts and ignore procedures and processes like emailing a document to a client for review, rather than sending through a formal transmittal via document control), and so to, collaboration can be a learned behaviour.

But I don’t think the result of this would be as effective in a fundamental way.

• If you are unsafe, you risk getting sued, bad accidents cause a bad reputation with clients, contractors and workers.
• If you are of low quality, you cut corners for short term gain, long term loss, and perhaps risk litigation.
• If you have low collaboration, you risk a less optimum job, low awareness and transparency and communication leads to low cooperation and cohesiveness, and you are less agile to adapt to change.

All three have bad consequences if ignored

• The first two is a risk in reputation, but also a benchmark risk, and more importantly the consequences are very meaty-litigation, death.
• The last one also is a risk in reputation (losing or not winning deals because of bad information flow does effect reputation/attractiveness), the industry benchmark is still a young thing in relation to collaboration, BUT unlike the others the consequences are not as meaty, no-one dies, we don’t get sued.

So I think because the consequences of not being collaborative don’t show explicitly like someone being hurt, and losing face (as this is seen as a quality process issue rather than collaboration/information flow), then we tend to be more reactive, or it takes a back seat in our attention. You still get work done not being collaborative (you do suffer later in frustration as you can’t find stuff or you aren’t aware of something you should be aware of), it’s just all these micro interactions, lead to a big picture of not being agile, and attractive to a client…if they can’t get their s*!t together, how are they gonna service us.

Great cross-functional CoPs are emerging like Bulk Materials Handling, Sustainable Development, Software Architecture and Approaches, 3D Visualisation and Animation, Bauxite and Alumina, etc..

But there is something else that’s emerging that we didn’t quite expect.

And we know why?

It’s because our CoPs are just online spaces with a bunch of tools (blogs, forums, wikis, docs, and a homepage).

This package doesn’t make them a CoP, it’s just what we called them, as that’s what the vendor calls them…nothing wrong with this…

Basically, these online tools don’t define the group or how it operates…their just tools. This also hooks into how the Socialtext staff differentiate them from past tools (transactional vs Interactive)

Anyway…

So the unexpected emergence is that CoPs are being used for lots of different things that are cutting into products we already use…why again…because people want to be empowered and engaged which distributed power (less control) enables.

What has emerged?

Let’s start with the answer and it’s effect: blogs, forums, wikis need to be features of existing products, and when they are how’s that gonna effect what has currently happened.

We don’t just have cross-functional CoPs ie. people distributed in the organisation in different teams, projects, business units, and levels of authority who come together in a space to support and learn about a common topic…which makes for a more agile organisation…it’s looking in your own backyard and connecting the talent dots.

Here are the main online groups that have surfaced.

Ad-hoc tasks

I’ve blogged about this before.

People want to do temporary tasks in an online space rather than hidden in email.

Our CoPs are more portal like with permissions and the rest, they are not one click set-up, they need a bit of upfront design.
- your CoP or mine for this task, but your not a member of my CoP…these task spaces end up buried in a CoP somewhere, they have no homepage of their own, the hosting CoP members may not like that their CoP has a unrelated parasite group

They are not the best spaces or timely and simple enough for an ad-hoc task.

For this we would need something like the new OpenText Social Media product, or Jive SBS (both of these also include a social network).

Or perhaps something more on-the-fly like Activities on Lotus Connections, or a future version of Google Wave…see more.

And Traction seems like the most flexible product around, I hear BlueKiwi is in this space as well…see more.

Initatives/Pilots/Crowdsourcing/Events

We are finding these a sweetspot, just like cross-functional CoPs.

We are starting a review of our project lifecycle process, which is to be coordinated in the CoP, basically where the organisation comes together in a communal space.

Support

I’ve blogged about this before.

It’s one thing to have a CoP to troubleshoot within a team, but it’s another thing when internal customers start asking questions for support through a CoP.

Personally I think it’s great, as people have an open place to search for past answers or even offer answers, and if you subscribe you can learn along the way.

BUT, this is cutting into the organisations official Support database. We still need this official and sophisticated tool for support management, but CoPs as a support tool are definitely cutting into their lunch.

Teams/Business Units/Office unit

These groups have a section in our corporate Document Management System (DMS)…it’s basically a set of folders.

Why are they using CoPs?

Because in the process of creating documents we have conversations about review.
Because we like to discuss issues.
Because we like to broadcast news.
Because we like to share experiences.
And email just doesn’t cut it.
And the DMS just doesn’t have these conversational tools, or a homepage that represents the group (well, they do, it’s the Intranet, but see the next point)

Intranet

I’ve blogged about this before.

Someone came up to me the other day and said, they love that CoPs are two-way, and that they can update their homepage (that acts like a portal) whenever they like.

As a result of this empowerment they mentioned that their intention is to no longer have any of their pages hosted on the Intranet, but instead, when people click on their business practice link on the Intranet, it will just take them straight to the CoP.

What’s the next natural step, that the global CoP hompage becomes the Intranet itself.

Client Projects

We have a DMS on another server with a different look and feel and processes that suit the context of projects.

But again, just like Teams/Business Units they lack a homepage and conversation tools.

Project teams want a homepage as a jump off point (a bunch of folders doesn’t cut it).

They also want this homepage to display conversations that are currently happening at the moment in email silos, this way the mechanical guys can eaves drop on piping conversations and vice versa, so we are more aware. A blog for project updates and broadcast news gets people on the same page.

Organisations are not (well maybe) Complex Adaptive Systems, so we need to make them open and transparent as much as we can, so people can be ambiently aware, and therefore better cooperate amongst the parts, and ultimately adapt to changes or even be preventative.

I have not created online CoP spaces for these projects as this is the turf of DMS, and having two spaces for the one thing seems odd, but people will self-organise their way around any design.

Let’s sum this up

CoPs are a sweetspot for great emerging unofficial groups, but they are also cutting into the following existing products:

• Email (this was the intention)
• Offical support database
• Corporate DMS
• Project DMS
• Intranet

And it seems we need a product to handle ad-hoc tasks.

Summary, future ponderings, and a suggestion

The original idea for CoPs was cross-functional practices eg Bulk Materials Handling

But as we can see because email, the DMS, and the Intranet are not as enabling, people are using CoPs as an alternative for everything.

In a way this CoP experiment has surfaced all sorts of needs, which is a good low cost experiment (naturally emerging needs analysis).

Who needs a survey, needs analysis, or just implement and hope it works as it was a good top-down idea…when the emergence that has surfaced from the existence from CoPs has given you the answer to all this pondering for free.

What it has surfaced is a need for our DMS and the Intranet to become socialised…and also a way to do ad-hoc tasks.

I’m seeing all this happening, and perhaps need to suggest a taskforce so us people running all these products can converge.

This convergence will be interesting. If these tools do get socialised, what will then happen?

Will teams decide to export their CoPs to their revamped DMS?

And if the Intranet offers the same tools as our CoPs, but with an Intranet backdrop, will some groups then export their CoPs to the revamped Intranet?

So maybe one day we will come full-circle, and CoPs will be just for cross-functional groups…as wiki, blogs, forums will be features of all products.

What’s the food for thought for people wanting to socialise their organisation online!

Perhaps firstly revamp your existing systems with social tools. ie. Work on your in-the-flow before, or perhaps in parallel with your above-the-flow.

• Intranet and business units/teams (Confluence or Thoughfarmer)
• Client Projects (Basecamp)
• Communities and Social network (Jive SBS)
• Ad-hoc tasks (OpenText Social Media)
• And what about micro-blogging (Socialtext signals)

See what’s happening here, a lot of the tools above do the same things eg. Socialtext has a social network and workspaces, OpenText has a social network, etc…

Also our projects need sophisticated document cycle functionality which Basecamp will not do, so in this case our existing DMS needs to be revamped.

I’m thinking perhaps an Intranet tool like Thoughtfarmer or Confluence could handle them all…except for client projects (requires document lifecycle processes)

Here’s a snapshot of different CoPs that are emerging:

More Than Cops

More than CoPs

By examining the CoPs, or better put, “online groups” at my work, they seem to be:

1. Teams/BU (execute work)
- which shouldn’t be called a CoP even though it is…who cares in the end, I’m happy people are using the tools

2. Teams/BU (learning/support spaces)
- this type of CoP is usually combined with the CoP above (point 1)

3. Cross-functional (traditional learning CoPs)
- a classic example is our Software Architecture and Approaches CoP where people from various units/teams come together to share, learn, help…and to bring that intelligence back to their tasks
- when we need help at work we often look to Google, Twitter, etc…why not create an environment where we can look to each other within the organisation

4. Internal user support spaces (customer service CoP)
- I run a Facilitators CoP where I communicate and troubleshoot with people that run their own CoPs
- These types of CoPs can be at the general user level, or for the support people themselves

5. Teams communicating to the business (customer CoP)
- using a CoP, rather/complementary to an email newsletter
- sometimes this type of CoP is combined with the CoP above (point 4)

6. Role-based
- people on different projects and teams, but share the same role…eg Project Managers, Project Systems Managers

7. We also have others like: interest groups, crowdsourcing, events, new initiatives, office happenings, specific tasks (although this last one suits a more simple application like ad-hoc groups…ie a bunch of people from different teams/units coming together temporarily to execute a task)

We don’t yet have any Client/Customer-based (support/crowdsource CoP, or a CoP with suppliers)

“…before you leap into reinventing your processes for transformative value, step back. You can’t collaborate with your customers before you learn to collaborate with your employees. In the spectrum of risk taking, its best to deploy from the inside-out.”

Just realised I posted something similar a while back, Internal community types that get you viral exposure.

Why do I say this?

At work we have many active online Communities of Practice (CoPs), some are learning and sharing, and others are customer based information and support CoPs, or even both.

In my post Online Communities of Practice are a sweet spot! I highlighted how CoPs cut into email conversations and Intranet information.

That is, rather than using email for questions, communications, support, we use CoP tools.

Some CoPs also like the fact that the CoP can be responsive and agile compared to the Intranet. Some of our CoPs are going beyond conversations and using the CoP as a portal to profile all the information about the group and services the group offers, as you would do on an Intranet.

What they like about the CoP is that you can update it yourself daily, and you can get feedback and questions from internal customers, as well as communicate to them.

What happened the other day is a CoP facilitator mentioned that the CoP was quickly replacing their need for an Intranet page. They said soon, they wish to not host information on the Intranet, but instead just have a hyperlink for their practice that launches to the CoP.

Whoa…CoPs are cutting into the Intranet…it’s not gonna be pretty if people start ditching the Intranet.

See what’s happening, social tools are becoming a catalyst for change, but it’s not explicit, it’s just a by-product…you are not having a revolution, it’s just you start using the new thing, and the old thing becomes ignored.

What will happen if the Intranet loses control to CoPs…their worst case scenario to authoritativeness and all things official and vetted.

As global CoP facilitator I’m not being a traffic stealer, rather a few of my customers are choosing to do this themselves, and when they ditch the Intranet, people interested in their information will also be visiting the CoP, not the Intranet.

So not only are CoPs enablers for emerging groups that are not official or even mature enough to be on the Intranet, but they are starting to attract existing groups that live on the Intranet as perhaps a new place of residence.

What does this tell us? People want to be agile, they want to be more transparent and connect, they want to be close to real-time, they want to be empowered to sense-make and do it themselves…a distributed organisation…worker engagement.

The Intranet better notice this and do something about it?

If they do, where does that leave CoPs?

If the Intranet becomes a social network with group pages, will our CoPs then be absorbed into the Intranet?

This was my whole point of my past post.

You can have a “social network with groups” standalone internal website (which is promoted on the Intranet), or you can have the same thing designed as the Intranet itself.

Here are some excerpts from an email exchange I had with our global librarian at work.

LIBRARIAN: I’m really having difficulties finding the time to set up the Library CoP. Can you set it up?

ME: If you like I’d rather assist you guys rather than do it for you.
Do you have someone you can delegate to?
Would you like to start off with a telecon, as I need to know the purpose for your CoP, who the audience/s are

LIBRARIAN: Currently, we have no manpower to even start teleconferencing. But if you don’t have the time either, I understand.
Based on our list of projects, CoP is currently a nice to have tool.

ME: Why don’t you send me a blueprint for what you want to achieve, and someone in your team (preferable someone passionate) and I will do our best to help you out.

Why do you want a CoP?

1. A space to learn and share with your team?

2. A place to coordinate tasks and assist/support each other?

3. A place where general people from our work can visit and ask a question, and also subscribe to blogs about current awareness eg. new journals

It can be for all of these, if so, let’s just try one thing first, but we will keep future needs in mind when we design

Who will be the main facilitator?

- this is a person who has time and passion to drive this
- this is not you as you are too busy, but it could be you once it’s up and running

As you know a community is all about conversations in the open (rather than private in email)
- but it can also have a portal element or website feel where you list all your stuff and information
- but you seem to already have an Intranet page for this

If we slowly chip away at it we will get there.

Perhaps I’ll ask this question:

What’s your most pressing issue or process that the community can make better?

Is it 1. learning/sharing, or 2. coordinating/assisting each other, or 3. dealing with your customers

ME: I suggest using the CoP just for your team, so you guys get used to using it, but if your most pressing issue is to get info out to your customers then we can start with that

eg. If you send Journal Table of Contents emails you can publish that in a blog instead and then email the customers the link to the blog.

Even better is if people subscribe, then you don’t have to email some of those people the link to the blog post.

This way the blog will act as an archive, and people can visit it…email is just a private letter box, whereas a blog is an open house

Think of the different email exchanges you have with customers, and the ways you inform customers, and we can re-purpose that using CoP tools

This is a broad statement, and there can be many reasons for this, but in this post I want to focus on one particular reason.

This has happened on several CoPs where the team leader has appointed their personal assistant or a nominated team member to set up a CoP…or the team leader has borrowed a person from another team leader as they like how they designed their CoP.
NOTE: Personally I would be inspired by CoPs with active and frequent conversation, over a well designed website.

The reason for their approach is that the community leader is technically proficient at designing and using the CoPs. The problem is that this person is not a Subject Matter Expert (SME), and does not have the interest, passion or time to facilitate the community in a non-technical way.

Facilitation is not just technical design/support, part of it is monitoring how people use the community and encouraging things, and re-purposing others…I briefly listed Facilitator’s duties at the end of my post, Community of Practice for Facilitators : pilot, adoption and participation.

My point here, is that CoPs need a breadth of facilitator’s, the head facilitator being the Community Leader.

It’s important to have the technical facilitator to cover the technical parts, but most important is the SME. Or rather whoever the community leader is must have a group of facilitators that handle different aspects of a CoP…technical, SME, etc…

Really, if it was an offline CoP then you would not need the technical facilitator at all.

Pause

I have realised for a while that this has been happening, and as the global facilitator I have picked up the pieces, but now that we have lots of CoPs, I’m finding I don’t have time, and I should be “training the trainer” anyway. That’s why I’m currently working on a facilitators workshop, which I’ve always intended to do, but never got the time. I communicate and support to facilitators in the Facilitators CoP, but I need a good real-time focused presentation and conversation to make this stick.

What tipped me over to blog these thoughts?

As a global facilitator I subscribe to all blogs and forums in all CoPs, and I stress that this is important for facilitators to do in their CoPs. This way you have total awareness of the activity, and you can encourage and re-purpose behaviours.

As global facilitator I eaves drop on the activity in all CoPs, but I never interfere, instead I congratulate/assist/recommend to the facilitator of that CoP with some action to take, as it’s not my place to talk to their members.

Anyway…

In one particular CoP we crowdsourced ideas into one forum, and from those 500 ideas we created 10 forums to house them all.

I don’t really agree with the next step, but it was decided that the heavy contributors on a topic were then nominated to be in charge of that forum.
- liase with the lead on bringing some of those ideas into fruition
- keep the forum going as general conversations about that topic

To my surprise they are doing OK, but could be going better if each forum had a person who volunteered themselves, something Samuel Driessen agreed with, but I can’t remember where he left that comment.

Anyway, I have noticed that in one of the forums called “Collaboration”, the person put in charge of that forum was also the project manager for our Office Communicator deployment (instant messaging/conferencing). He posted a new forum topic called “Office Communicator Tip of the week”…which yes, sounds like a blog post.
And in the last couple of months he has posted replies to that forum topic to publish new tips. In essence, he’s using one forum thread as a blog, where each new post is a reply to the forum topic.

I’m glad he’s participating, but his enthusiasm can be channeled to the right tool for the job. In the future that forum thread will be a needle in a haystack, it will be a thread with 50 replies. Instead he could have his own place using a blog, where the whole blog is about his topic, rather than be buried as one of many topics in a forum. The blog will have more presence, it can be furnished around his topic, and he will be more recognised…he and his know-how become a destination.

My point though is that there is no-one to notice and harness this, as that CoP only has a technical facilitator who is not looking out for this sort of thing. The CoP instead needs a SME or a leader who cares about the CoP and it’s members.

Team working CoPs

Teams using CoPs to execute tasks, can carry on with their team dynamic of getting stuff done, manage and measure, produce outcomes/deliverables.

Team sharing/support CoPs

But more common are teams using CoPs for sharing/learning/communication/support (troubleshooting). And in this case it’s important that these team sharing type CoPs encourage facilitation rather than try run the community like a team.
As I mentioned in an earlier post, the team lead and sub-team leads are too busy to run the CoP space, so a team member is given the task to run the CoP, which is sometimes like pushing up a hill, as they don’t have influence and feel they are bugging people who might not care about the CoP to start with, as they are automatically a member by default of being in the team, rather than accepting an invite. And if the lead and sub-leads are not role-model contributors then this makes it a real hard chore.

Regular sharing and learning cross-functional CoPs

For more on this point about group dynamics see my post, Team-based CoPs compared to cross-functional CoPs.

Ad-hoc groups

Then we have people coming together from different parts of the organisation who request to use a CoP space for their ad-hoc group, to work on a task like fixing a process, etc… These spaces are often more short-lived. Again this really isn’t a traditional CoP…again the technology (CoP tools) do no define the group dynamic.

Anyway, these ad-hoc groups should really be self-serve, I really feel like a bottleneck, and most of the time people don’t bother and use email because their synchronous to asynchronous flow ain’t smooth and effortless.

Sponsor vs Self-serve

Betrand Dupperin picked up on this notion of self-serve creation online group spaces, and from reading his post it seems he was more clear in his explanation.

For traditional CoPs we ask that the requestor has a community sponsor…this is important as online CoPs take time to run, and that is time the manager is allowing for, that could be spent on execution.
If there was a notice from the very top that people can spend time away from or related to tasks (like Google’s 20% time), then self-serve would be OK, but at the moment we need the requestor to note that her immediate boss is ok with this.
NOTE: we have a side issue that the CoP tools we are using are complicated to set up for a regular user, so self-serve might still be an issue from a design perspective.

Now, for ad-hoc group work, this really doesn’t require a sponsor, as the time you spend in the ad-hoc group space is time doing the task itself anyway.
So what we have to do, is work with the vendor to make simple versions of our CoP tools, where there is just one stream, and simple permissions…as stripped down as possible so it’s close to the ease of using email. This way these ad-hoc groups can be self-serve.

I see Jive SBS takes this approach where they have community spaces and group spaces, where the group spaces are self-serve and more basic.

Would people use these ad-hoc groups as traditional CoPs, probably, but they wouldn’t look like flashy websites like our regular CoPs.

I guess that’s where we are, the solution might actually create an issue…personally I would not see it as an issue but see it as emergence, and perhaps this momentum as a catalyst for the allowance of work time spent sharing and learning…not explicitly like 20% of your time, but just embedded into your day.

So what do you think?

1. Teams or departments manage their own communities
   - we refuse CoPs that tread on the turf of an existing team or department
2. CoPs require a sponsor
   - Bottom-up request, Top down creation
3. Ad-hoc groups self-serve

And what do you do if ad-hoc group spaces are used as CoPs?

Would it matter, as the ad-hoc group spaces would be so simple that the facilitator does not need to spend time managing permissions, and up keeping the space. But people may still be spending a portion of their time contributing.

Here are some points from our discussion.

• I am trying to set up a CoP for people with experience in 3D animation and visualisation.
• This is a specialist area with only a few of us officially doing this role.
• But recently I have noticed a lot of people with experience coming out of the woodwork ie. engineers and the like who have experience with some of the software…I know that around the globe there are several people with this expertise.
• I would like to set up a CoP for a couple of us, and then attract some of these people
  - the CoP as a way to amplify what’s already happening
• We have a lot of work, and it would be good if anyone could help us out, rather than sourcing outside help
  - why spend money externally, when we have the talent internally
  - this ties in with my post, We are more than our job title describes
• We also want to use the CoP to gather what our company needs are for 3D animation.
• Besides conversations, the CoP will also be a great “place” to showcase our gallery.
• We are inhouse specialists, and we want the word to get out that we exist

I really like this last point
- email is not a place
- the Intranet is not going to promote these guys (it’s not interactive anyway)

The online CoP is going to harness their talent, and offer a space where they can be known…then only after this grassroots effort, where they may one day prove themselves as a viable component of our workplace, will they get an official spot on the Intranet.

I mentioned similar CoPs eg. Software Development, Learning and Development…and that some people here in Perth are flash gurus.
He said, ohhh…we just required a flash guru for a job here in the Canada office, we couldn’t find one and had to source externally.

Need I say more, if we are visible and participate, we can then connect and converse, and ultimately collaborate…and generate work (connect the human resources so they are optimising the collective talent).

The theme of this post is do it yourself enabling tools, that allow grass roots efforts to emerge and be seen.

These new bottom-up social tools are surfacing opportunities that the top-end of the business are not thinking of, but are getting traction as knowledge workers now have a way to engage and propel.

KM or Enterprise 2.0 is not only about aligning to business strategy, but instead allowing workers to actively participate, creating their own value, where ultimately what they are doing can be noticed and officially be added as a strategy.

Top-down crowdsourcing is one thing, but bottom-up emergence of invention is another thing…we are not here to just give input to top-down ideas, but the top can notice what we are doing at the street level, and say “I like that, I’m glad we give you tools to demonstrate your talent.”

Of late we have seen posts by folks at ThoughtFarmer and Socialtext on pilot/implementation methods. These are great posts and show the difference between focused phased piloting and no pilot at all. I may cover these posts at a later date, as my post today is more on adoption or participation at the group level.

My focus is not on the social computing practitioner, but rather on a regular person wanting to run an online Community of Practice (CoP). It’s more about the social computing practitioner helping a CoP Facilitator help themselves.

ie what are the conditions that a facilitator can create to get their CoP off the ground.

I can’t help myself, just quickly…the Socialtext post above refers to the interactive nature of social software (compared to transactional) where scale and network effects are essential to actually see the potential and emergence. And this is so true for enterprise wide tools such as social networks, microblogging, blogosphere, etc..

But this is not always the case with social computing islands such as CoPs. You don’t need network effects for a group space to work, you just need willing and interested members…and in regards to a team, you need a task or issue to tackle where social tools will replace current tools. I went in depth into this in my post, Do group tools get more traction due to not requiring network effects.

Just to mix it up, group spaces aren’t just about the talent of the group, the task/agenda, and how they work with social tools, which a pilot helps with…they are also about others roaming from CoP to CoP, and as a visitor being able to ask a CoP a question or perhaps answer something…this is serendipity and emergence that will only present itself with scale (it is less likely to happen in a pilot).

The two takeaways here are

1. social tools to help you do what you already do better

2. connecting the enterprise to increase cross-team awareness, cooperation, collaboration, ideas, sourcing information (who knows what), serendipity, opportunities, diversity of emergence…

Basically the more connected an organisation is, the more productive and effective they are. As I alluded to in my social PKM post, that a whole bunch of personally productive people does not make the organisation necessarily productive.

Oops, I wasn’t meant to get into this in this post!

What are the reasons for a pilot again?

• Helps to discover and squash tech issues before release

• Helps to discover and assist in user issues

- that’s why a cross-section of people is important in the pilot

• Deployment team can get an idea of early good practices, codes of conduct, showcase examples

- and will be prepared with the knowledge to help a greater number of people and issues when comes release time

- the more tech and usability issues found and documented in pilot stage the more room this makes to devote time to championing and facilitating

• Stewart Mader has similar thoughts…a good one is use cases in how you can use wikis, he says:

“The teams involved in the pilot would help define and model wiki uses that can then be shown as examples during the wiki rollout to the rest of the organization. This embeds the right kind of uses throughout the organization, and ensures sustained use of the tool.”

Many points in this post have been enrichened by a podcast with Stewart Mader, here’s some notes.

WHAT ARE THE CONDITIONS THAT A FACILITATOR CAN CREATE TO GET THEIR COP OFF THE GROUND?

Following on from my post on workshopping and piloting a new community are the adoption factors a facilitator can massage to get participation off the ground.

After creating a community that everyone wants (or if it’s a task space; finding an issue to solve/fix a process), and piloting it to test it’s use, you will have done all the right things to get started on the right foot, you will have hopefully circumvented any fundamental obstacles.

Next is to create conditions for people to use the community; you need interactions and conversation to grow the community. This requires facilitation, guidance and some tactics or notions to be aware of when dealing with getting a group of people to channel their time into a certain direction.

We all agree the community was a great idea, and here it is, but some people have cold feet, or find it’s unfamiliar. There is an unintentional resistance, and this can be facilitated or nurtured with some points about adoption.

“…people don’t resist change, they resist being changed”
- Peter Bregman

“…resistance is not so much about the change; it’s all about being changed”
- Peter Vajda

“Resistance to change is situation specific, not an attribute of an individual or group”
- Nancy Dixon

We have already asked the questions (needs analysis), workshopped and piloted, so what do we need to know for it to grow or start breathing, and sustain a heartbeat.

Design and Structure

• People need to be a click or two away from what they need to do

• If it’s too complex people won’t have the time to learn, they need to orient themselves with ease

• Create a guide on how, and when to use each tool (better still incorporate it into the design)

• Blank slates don’t help (people are used to structured tools that are designed for a specific purpose, and are not used to the idea of flexing unstructured tools to fit their needs)

- I like ThoughtFarmers idea of usage scenarios

• Create a stickiness factor so people return (frequent blog posts, a communal wikipedia)

- are you appealing to all members

Frequency

• Core group of bloggers to do weekly columns

• Whenever something happens, blog about it
eg. I uploaded a presentation into our library, go check it out…

Email Interaction

• If it’s not in your inbox it doesn’t exist

- people are more likely to react if it comes to them

• Also being able to publish via email is handy

Peer to Peer influence

• Sometimes people will only adopt if their close colleagues are participating

• Prior to this they have not dedicated the time to investigate, but if a close colleague finds it of value, then this will influence them to give it a try

• Again, we are influenced by people we trust, more than a training programme or by others we don’t know well. We take recommendations from people we value.

Eg. If someone recommends a movie I may not go, but if a friend does there is more chance I will go.
The same applies to participating in CoPs (if my trusted colleague or someone I respect is doing it, I may give it a go).

EXAMPLE

Peter and Joe are both Project Managers who attended a training session on communities. The online tool offers all the solutions to their needs about communication, awareness, sharing and learning.

When they got back to their desks Joe had a look at the communities and just didn’t have time to learn them…if the design was more appealing and intuitive, perhaps Joe would have delved further. A couple of months later Joe and Peter are chatting and Peter tells Joe of the brilliant transition his team has made to using online communities over emails and attachments. Peter told Joe it took a lot of getting used to, discipline and facilitating, but eventually it became part of their routines (it’s the way stuff is done around here now).

Joe really values Peter’s work ethic and they are mates and trust each other, help each other out…they have a history together. Due to this close relationship Joe has decided that if Peter thinks it’s good, then it must be, as past history shows that Joe trusts, respects and admires Peter and his endeavors. Indirectly Peter has influenced Joe to give it a try.

This example shows us that a training session is just one aspect to gaining adoption. We are more prone to take the time to try things out, based on recommendations by someone you trust over someone else that does not have as much influence on your decision-making.

What does this say…if you want to influence someone, influence their peers or people they respect and admire, and this will in turn make it more attractive or motivated for them to take up your offer.

I guess case studies are also influential as they can make known (to some degree) the worthiness, risk and return on trying something out…time or attention is also a factor.

People are like that; take up tends to increase when people can see others didn’t get hurt or they had a success, so it’s now safe to join…let others do the work first. I guess those who test the waters first, get to learn from their mistakes first hand (which is the best type of learning), and they are also perhaps the innovators or cutting edge people who reap the benefits or become known for their endeavors as the pioneers.

At my wife’s work there is a campaign to build a unique service centre for children who have been taken away from their families. A lot of high level people have been approached and have shown interest, but have not committed. But they noticed that when one person chose to commit, then this had a chain effect where those previous people that were approached also decided to commit.

This has an amazing snowball effect when people are visibly connected in online networks. Since we have more ambient awareness of each others actions, it doesn’t take long for people to see what their peers are doing and choose to follow…visibility and participation is the fundamental key.

There is more chance for peer to peer adoption for any old thing when people are connected in online networks; the irony of this post is we are trying to get them to be participants of online networks in the first place (actually this post is about communities, but you know what I mean).

Peter Bregman points to a study which illustrates our nature of peer influence:

“You could tell the children you expect them to eat their vegetables. And reward them with ice cream if they did. You could explain all the reasons why eating their vegetables is good for them. And you could eat your own vegetables as a good role model. Those things might help.

But Birch found one thing that worked predictably. She put a child who didn’t like peas at a table with several other children who did. Within a meal or two, the pea-hater was eating peas like the pea-lovers.

Peer pressure.

We tend to conform to the behavior of the people around us. Which is what makes culture change particularly challenging because everyone is conforming to the current culture. Sometimes though, the problem contains the solution.”

Champions and role-models

• In team-based communities especially (as opposed to shared interest groups), if the leads are not role-models in active participation, then this sends a signal that the community is not important

• Facilitators must lead by example, and encourage senior/respected people to be role-models

- People will follow or respond to their lead and encouragement

Viral Approach

• Concentrate on training a core group

- they will set the good examples and be an influence on others

Push sharing in a pull system

• I had a scenario of a CoP facilitator emailing a link to a few people

- I suggested using the blog otherwise it sends the wrong signal (kind of like a parent telling their kids off for something they do themselves)

- if their intended audience aren’t subscribers of the blog, they can create the blog post, then send them the link

It’s about conversation

• It’s not all about the blog post itself

- it’s about the the conversations that the blog post triggers (this will build community spirit…like a thriving dinner party…you will go to the next one as you enjoyed the company and stimulation of the previous one)

- people are more prone to comment, rather than blog or write a forum topic

- don’t have to be provocative, but even when posting about a journal article, rather than just share the link, write an opinion based review…this will get people to react

Raids/Barnraising

• Similar to handholding and more popular with wikis is spending a session on using a wiki for a specific and real purpose

- this gives people real experience at using them, and using new tools for current needs

- the idea is that they will go back to their seats and continue using it, as they have overcome the technology barrier and the “what can I use this tool for” barrier

- it also builds working collaboratively

- as the ThoughFarmer post points out, it also gives people examples to learn from

- I have a Wiki CoP at work where we blog about wikis and ask questions in forums, it’s also where I list examples of wikis that people are creating (it gives others ideas of how they can use wikis)

- here are some links to barnraising wikis

Re-purposing email (It’s more about new behaviours)

• CoP tools replace the email distribution list

• If people continue using email out of habit, the facilitator must thank them for participating. And then mention that if you are going to email an announcement, news or sharing information, please use a blog. And if you are going to email a question or topic for discussion use a forum.

- then demonstrate by re-posting their email into the forum with your reply, then send them the link

- ask them to subscribe in case the conversation keeps going

• Answer questions promptly so people feel heard and benefit from participating

- this will influence return visits

Hand-holding

• This is about breaking old habits with new technologies, plus people are expected to publish in an open place, rather than the more confident private email channels

- plus they won’t spare the time for themselves to learn a new tool, but they perhaps will if you instigate it

• This may involve sitting down with a member once a week for a couple of months and guide them along in publishing a blog post, until they get used to it and build the confidence.

• Once people get comments and ratings on their blog posts, it gives them confidence and encouragement to continue posting.

- see Nancy Dixon’s post on a company commander who became an active participant after he found out that other people were getting valuable use from his AAR document

- being appreciated and feeling you have made a difference are good conditions for further participation

• After a while this system becomes self-rewarding as people may draw a reputation

For more on this, read the next section on “Feedback”

Feedback (Reputation/Recognition)

NOTE: I will state here that I lean more on the natural and sustainable method of the conversational element in self generating peer reputation to propel the community, rather than incentives.

• I’m finding that when people use CoPs well I am impressed and give them feedback

- this encourages more participation (see the end of the previous section on “Hand-holding”)
eg. good use of blogging

- one facilitator blogged to her members that she has email subscribed all members to the main blog, and took the courtesy to explain how to unsubscribe.

- Just today I emailed a picture of a gold star to a CoP facilitator for really using their blogs and forums well, they have a really active community…and he emailed me back saying “ha ha - I would rather have had a picture of a beer”

- and of course we hope a comments discussion self generates the motivation for more blog posts (HP’s study hold this as one of two highest factors to participation)

Nancy Dixon relates this to recognition:

“Recognition means the most to us when it comes from those who really know the subject – who know what they’re talking about. It’s great to have your boss think you’re a top performer, but chances are your boss doesn’t know enough about the technical part of your work to know how good you really are – but your peers do. For a peer to say, “The person that really understands that problem is Pete,” that comment Pete would regard as a sign of respect and one he would highly value.”

Group building

• Face-to-face interaction and connection, or online ways for members to connect in real-time

• These can be social gatherings, meetings, or workshops

The next section on “Confidence” extends on the impact that building rapport has for knowledge sharing/participation

Trust (Confidence/Comfort)

• Are people confident and comfortable enough to participate? ie. do they have a relationship with other members
eg. at a house party we are always more comfortable in sharing our lives after a lot of small talk where we build a rapport (a certain level of trust)…or after a few drinks

- Karen Stephenson’s article for more.

Relationships (Give and Take)

• Is there an equilibrium of give and take (both with members and non-members)

- do some members just ask questions and never help out with answers

- are members willing to research answers for questions from non-members
(this is an important point, and the reason why most CoPs are membership based, you are willing to take the time to help out others within the membership circle, as they will in turn help you out next time (like the reciprocal altruism of vampire bats)

- People you trust will give you confidence they will not misuse your knowledge sharing

- Are some members being burdened
(again membership is important, as you take the time to help out a handful of people)

Gia Lyons has a great post on this

“Because you are the one individual who knows this stuff, you are reluctant to advertise that fact, for fear of the avalanche of requests to collaborate. You need more emails, IMs, and phone calls like you need another orifice in your cranium. Plus, these people who would swarm you like flies on poo will not perhaps care too much if you are over-extended. But, you are more than happy to share what you know with one or two others, after you’ve discerned that they won’t abuse you, won’t stab you in the back, won’t take credit for your intellectual capital, and will perhaps return the favor. The people who invest in creating a relationship with you are rewarded with your experienced point of view.”

More from Nancy Dixon:

“We do not give that knowledge away lightly. Before we take the time and trouble to share that knowledge, we need some assurance that our knowledge will be treated with the respect it deserves, given thoughtful consideration, and that the recipient actually knows enough to make use of it.”

In order to share knowledge, we need to build relationships, and we do this by informal conversations on sites such as online communities:

“The way a professional can know how someone will treat the precious commodity of her knowledge is to know that person well enough to make that judgment call.”

“…sharing knowledge is risky, the other person may make a cutting remark about it or indicate that it’s not worth listening to. And sharing knowledge is time consuming, because to really respond to another’s question or problem takes the time to understand the issue and to explain in sufficient depth. So we rightly place conditions around sharing our in-depth knowledge. The relationships we build with others provide a needed level of confidence that our knowledge will be treated with respect. Knowledge sharing and relationship are coupled.”

Personal relevancy

• Is the community personally relevant, or fulfilling needs at an individual level?

Dawn Foster lists some motivation factors

Portal

• In addition to being a conversational place, dress the homepage with common links so it becomes a pivot point for peripheral needs

In-the-flow

• Choose an activity or type of communication that is conducted in an email list and now do it in the CoP

eg. broadcast announcements are now done in the CoP blog, people have no choice but it visit the CoP
- while they are there they may look around and participate elsewhere

For more see the Transparent Office blog

Activities

• Offline

- choose something you do offline eg. a question time pre or post a conference/meeting…and complement this with using a forum for pre and post questions

• Member intros

- one of our CoPs makes it mandatory that new members fill in a forum topic where they can tell the group a little about themselves, experience, why they joined, aspirations

• Lounge forum

- some of our younger generation (graduate) CoPs have non-work forums as a way to build commonality, fun and relationships

- the more rapport we build the more we build opportunities to collaborate and help each other out

- Dawn Foster has more on the lounge concept

• Blog carnivals (thematic topic weeks)

• Polls

• Coffee corner/Fill in the gap

- fun quiz, riddle, story…

• Member of the month

- this showcases a member

- one of our graduate CoPs also asks questions to the community about a member
(this gets people talking to each other, and finding things out about each other)

• Showcase hot discussions (weekly roundup posts)

• Share personal stories

• Keep track of people traveling

• Guest posts from other CoPs

• Use engaging media (videos)

• Link to your CoP in your email signature

• Create your own newsletter to reach others

• Promote the CoP in other newsletters

• Write about stuff happening in other communities

• Build a relationship with sister CoPs (drive traffic to each other)

• Guest bloggers from other CoPs

• Rehash old content in other ways

• Events / guest speakers

• Blog columns (frequent posts)

General facilitator duties

The focus of this blog kind of bleeds into some of the duties of a Facilitator, so I’ve included a few below

• Gardening/Weeding (move topics, distill great posts on wikipages)

• Design

• Help and welcome new members

• Assist people in using CoP

• Answer questions promptly

• Make sure content is correct (re-edit old posts, leave a comment to correct/update)

• Help guides

• Remind people which tools to use

• Re-purpose email

• Off topic reminders

• Welcome suggestions and Feedback (via a forum)

• Barnraising

• Monitor/Listen in and always offer pointers or feedback or congratulate

• Understand member motivation

• Encourage members to specialise

• Promotion

Related

Preparing for community release
Self-serve create groups is essential to harness emergence and adapt
I don’t create communities, I create online spaces!
Enterprise social networks and ad-hoc groups

Unless you can structure it yourself like Nathan Wallace did with a Confluence wiki…not sure if SocialText can achieve a similar thing, but I believe OpenText Social Media, Lotus Connections, Jive, Awareness, Traction, Telligent, Connectbeam, and more suites made of components rather than designed as an Intranet.

Getting an internal Facebook that is designed as an Intranet replacement is more like Intranet 2.0, and seems to be what ThoughtFarmer are doing.

I suppose the third category would be to alter your existing Intranet by mashing in these types of features.

The latest Neilsen report on the social intranet says a few interesting things on this point:

“It’s important to integrate social features with the main intranet to avoid burdening users with double work.”

“That said, several of our case studies successfully implemented a staged approach, initially separating social features from the main intranet because of their different design and feel. Eventually, these features should be integrated, ideally as part of a bigger project to redesign the entire portal.”

I guess the difference I’m making here is that these new social network/group tools are mainly about connecting and collaborating, whereas Intranets are usually about profile information on each unit, heavily used tools and links, and news from teams to the rest of the organisation.

In this sense it seems designed tools like Thoughfarmer are combing the best of both worlds:

Doing work/finding stuff

• individual connecting with the organisation
• individual sensemaking
• collaborate in groups

Company information, tools and news

• make a profile page for your team with links to lots of info and what you are about…and also news your team wants to share with the organisation
• find common tools and links (timesheets, repositories, etc…)
• a company homepage as the pivot point

This is taking us back to the true meaning of Intranet (via Matthew Hodgson), rather then the hijacked, vetted, static, one-to-many tool it became.

“Essentially, he observed that people were creating small websites inside their organisations to share knowledge and communicate information”

Matthew then explains it’s relationship with early KM efforts:

“…the idea that, much like print publishing, documents are worked on by individuals and then released to others once it is finished and officially approved. KM guru David Gurteen suggests that this “create and publish” behaviour is also likely to be the result of early knowledge management efforts to bring structure to information in the organisation and make it searchable and easily accessible to employees. Unfortunately, as Gurteen highlights, too often employees didn’t see any value in this for themselves and, as a result, such systems failed”

“The essence of this failure of early intranets to bring true communication value into an organisation and to its employees is perhaps bound with the lack of recognition and understanding of how knowledge is created and information is shared by people. It’s also the factor that underpins Web 2.0’s success where traditional intranets have tended to fail. That is, that information is shared through social networks, from person to person, and that there are a number of roles in that social exchange.”

Related

KM: Round 2.0
KM 2.0 is about “showing your workings out”
Is publish a dirty word in enterprise 2.0

I set the scenario that at work there may be a task or initiative which involves people from many departments.

What usually happens is everyone gets invited to a meeting: in a room, via a telecon, or something like webex (we now use MS Office Communicator).

After the meeting the coordinator will go back to their seat, document the minutes in MSword and send an email attachment.

Then various people use email to do their bit.

Then we reconvene in a new meeting to see where everyone is at.

This is hopeless; I say when we go back to our seats we can still assimilate the real-time room (meeting) environment in an asynchronous fashion.

This makes for better communication, coordination and awareness…and transparency by default.

After the meeting someone can create a group space and invite all members as quick as sending an email.

Here they will find the minutes in a wiki, each page has a comments stream.

Here they will find a question space (just like issues raised in the meeting)

Here they will find a blog to post updates about the part they are working on.

Well, look at that, we can do asynchronously, what we usually do when we are in the same room.

This online tool is a social network with ad-hoc groups, where you have your own “mypage” that lists all groups you are working in, even better if you can post to any of the groups from your page.

Integration

A good way for adopting new practices is in the design and integration with existing tools.

Just like Jon Mell describes less use of email by incorporating IM into email (placing it in the same spot where you create a new email)…what I would like to see at the end of an Office Communicator Live Meeting, is to be able to spin this real-time (synchronous) ad-hoc group into an asynchronous ad-hoc group using a social network and group tool. Somehow both tools would be integrated, making jumping from one to the other the obvious thing to do; rather than using email for asynchronous communication and coordination.

People often find email conversation frustrating so it’s decided we need another meeting…with the correct asynchronous tools you don’t need so many meetings as we can use blogs to communicate, forums to discuss and wikis to collaborate on a perpetual basis…I alluded to this use case for teams a while back.

BTW-Why is Outlook not an internal Facebook and MS Office Communicator an internal Twitter?

Like my last post, design is key to influencing new behaviours.

More from Jon Mell:

“…there is no reason why at the front end we cannot combine communication tools at the presentation layer so that people don’t have to think as much about how they are going to communicate and which tools they are going to use. There is a scale here in terms of how advanced people are in their adoption and usage of Enterprise 2.0. Once people are comfortable with the concept of Enterprise 2.0 then they will naturally and intuitively know which tools to use without thinking. At the initial adoption stage, however, putting guidance and pointers in the flow of existing tools can have a significant impact in terms of alleviating any fears of using a new system. Some users may always stay in this mode, where they need the system to do the thinking for them in terms of which tools to use, and others may move to a position where the thinking becomes more intuition.”