Sep 18

If you’re a knowledge management professional (that is, somebody who thinks about knowledge management more than they probably should), you’ve probably encountered the formal-versus-informal debate in some capacity.

Much of the time, as knowledge management folks, we try to come up with processes — processes for how people work, processes for how organizations make decisions, processes for how technology gets put into place. Yet where there’s a place for building, there’s a place for tearing down.

We’ve all had to deal with nonsensical but well-intentioned processes. Maybe somebody thought it would be a great idea to make somebody fill out a form every time they want to be recognized for sharing knowledge — thinking that it would be easier to track who was doing a good job of sharing and who was shoveling knowledge into their own personal silo.

Yet somewhere along the way, we become purveyors of complexity for complexity’s sake. Much of the time, real value is realized through tearing down the inane corporate complexities that we all have to deal with every day, and allowing people to do their work.

And while this is a noble ideal that most people (including us knowledge management practitioners) would agree with, things turn around when we’re called on our proclamation of less complexity for all. I talked about this a few posts ago — and as a profession, knowledge management practitioners need to learn to let go.

Take communities of practice as an oft-quoted knowledge management best practice. Often, in practice (no pun intended), communities of practice end up turning a loose group (a community of interest, which is by definition less formal than a community of practice) into a formalized, structured body that no longer has the flexibility that it once did.

It’s the informal nature of these groups that often acts as one of their biggest strengths — and while formalization has its place (in terms of rejigging workflows, setting up good governance practices and the like), we really need to strike a balance between the formal and the informal.

Keeping and leveraging the messy, unorganized nature of spontaneous collaboration can be both scary and tough to do, but the tendency to overly-formalize these collaborative happenings often means squashing the life out of them.

Like this post? Subscribe now to the full RSS feed.


Related Posts


4 Responses to “Should knowledge management be more formal?”

  1. James Dellow Says:

    For someone in a KM role, perhaps another dimension to this is the difference between formal and informal support for CoPs and CoIN. A Knowledge Manager can still support informal groups with formalised support mechanisms – e.g. promotion, advocacy, infrastructure, coaching, governance etc.

  2. Atul Rai Says:

    While there has to be a certain amount of informality, to “allow the water to flow on its own course”, there has to be also some kind of alignment with business objectives. After all, thats what we are trying to achieve, arent we? As college students, we used to have debates and discussions, and they simply used to jump from one topic to another, until, after a few hours (of chit-chat, cigarettes, and cups of tea), you didnt have a clue where the entire discussion began from. This is something which needs to be addressed.

  3. Should Knowledge Management be More Formal? at Information Innovation Exchange Says:

    [...] Read the full article here [...]

  4. Lucas McDonnell Says:

    James and Atul, I think your points complement each other. Promoting informal groups through the more formalized infrastructure that James recommends only makes sense if those groups are linked to the objectives of the business.

ss_blog_claim=29bfc7ccb63aa1b751455bbcb7b2edf9