In-the-Flow and Above-the-Flow

I often hear from wiki champions inside organizations that "It's hard to get people to use wikis". There's something right about that comment, but also something wrong. I'll explain why.

Wikis can be used for many different activities, which fall into two broad categories:

• In-the-Flow wikis enable people do their day-to-day work in the wiki itself. These wikis are typically replacing email, virtual team rooms, and project management systems.

• Above-the-Flow wikis invite users to step out of the daily flow of work and reflect, codify, and share something about what they do. These wikis are typically replacing knowledge management systems (or creating knowledge management systems for the first time).

When wiki champions complain that it's hard to get people to use wikis, they're usually thinking of above-the-flow wikis. Modeled on  Wikipedia, these wikis typically aspire to capture knowledge and insights that people collect in the course of their work. That's a hard thing to get people to do.

But the challenge of getting people to use above-the-flow wikis is an above-the-flow thing, not a wiki thing. Left to their own devices, people don't collaborate very much in above-the-flow ways. That was one of the great (if depressing) learnings of the Knowledge Management movement.

Above-the-flow wikis are used lightly (when at all) by large groups of people. Many are encouraged to participate, but participating is rarely an urgent or critical-path activity. Lurking is extremely common, and the bulk of content comes from <5% of users who are either personally invested in the success of the project or just love to publish. Wikipedia works because of the law of large numbers: A small percentage of a huge number is still a large number.

Adoption of in-the-flow wikis looks very different. It's not at all hard to get people to use in-the-flow wikis. They are used intensively by relatively small, well-defined groups of people: a project team, a business unit, etc. Once the group (or the group's manager) decides to use wikis as the primary collaboration tool, adoption is quite easy: People use it because that's the way to do their work. Lurkers are rare, since most people have a steady stream of things to contribute to the rest of the group.

In order to bring wikis into an organization, it helps to have both kinds of wikis. Both have value, and both bring different things to an organization. Given the low cost of launching wikis, champions should probably launch multiple wikis simultaneously. But they should not expect an above-the-flow wiki like an internal knowledge exchange to have the same level of usage as an in-the-flow wiki.

Comments

[Dan Keldsen]

Michael - interesting fine slicing of usage. Cleaning out a spare room in the house this holiday, and found my dusty copy of Mihaly Csikszentmihalyi's book on Flow. Combine that with one of our Enterprise 2.0 advisors, Stowe Boyd, and his discussion of flow in social applications (also based on Mihaly's work), and I think we're on to something here. Your description of in or above the flow isn't quite the same as Mihaly's, but very close, and certainly similar underpinnings.

There are good reasons why you'd want (as an individual or as an organization) very tight integration, and loose or non-integrated (wish dis-integrated made sense here...) solutions. Sometimes stepping out of the system (or flow) is exactly what you want, and at other times, you want a portal/dashboard workspace, with all tools/systems/knowledge readily at hand.

These are all behaviors that have been seen before, just not quite so obvious and easily attained as in the Enterprise 2.0 or Web 2.0-enabled world. Or at least that's the hope, eh?

[fred]

Hi! i found a lot of films here, of course if you are using rapidshare premium account http:// megauploadfiles.com

[Japanese words]

Great article. I agree with you that most people wont use a wiki and see creating it or working on it as a less important part of their job. They can be very useful though when used correctly

[Buy Penegra]

Like with any other product, you need all the facts available before you can buy Penegra. Penagra is an oral therapy drug whose main ingredient is Sildenafil Citrate. Sildenafil Citrate is the same ingredient that makes Viagra and Penegra is just a generic version of Viagra.

[darkfall online]

It's not at all hard to get people to use in-the-flow wikis.

[Viagra Online]

Wikis can be used for many different activities, which fall into two broad categories:

* In-the-Flow wikis enable people do their day-to-day work in the wiki itself. These wikis are typically replacing email, virtual team rooms, and project management systems.

* Above-the-Flow wikis invite users to step out of the daily flow of work and reflect, codify, and share something about what they do. These wikis are typically replacing knowledge management systems (or creating knowledge management systems for the first time).

I like this two categories, they are true and interesting!!

Juanita R. Mcniel

[TMJ]

These kind of information flow is totally different compared with the 90's flow behavior.

[louis]

I’m hoping that we’ll end up with a slew of prototyped ideas and a bunch of happy people. I’m sure there’ll be a lot more hard work until we can turn those embryonic proofs of concept into living