When Corporations Forget

Forgetting Is Only Acceptable for Charming Little Puppets

My grandmother used to say to me that I’ve forgotten more than she’d ever known. (She was just trying to be kind, boost my confidence. ) What’s curious from a KM perspective is that that statement – that one may forget more than another ever knows – isn’t just applicable to much-loved grandchildren… but, of course, to organizations.

Over 5 years ago, Andy Seidl (2004) wrote a great blog post about corporate amnesia – or organizational memory leak – which he argued was the result of “numerous, seemingly insignificant, day-to-day forgetting events”. The act of forgetting is a critical issue for KM in large organizations in particular, especially those with higher turnover rates.

What happens when knowledge walks out the door for the last time? What steps can an org take to avoid organizational memory leak?

I guess the bigger question is, Why would knowledge walk out the door for the last time in an enterprise-sized organization? In a small one with a few employees, sure – but in a large corporation with 250+ employees, there must be one or two who have similar jobs, use the same databases or shared drives, etc. No? So why then might an enterprise suffer from corporate amnesia?

Recent job cuts are a problem – especially when a corporation decides to cut a whole group, such as engineering/development, HR or Creative Services, in favour of outsourcing.

But what’s more interesting than that (because I’m sooooo tired of hearing about the tough economy) is the idea of social capital and tie-formation. More specifically, the idea that strong and weak ties can help people share knowledge across organizational boundaries. Check out this great article (1999) by Morten T. Hansen for more about search-transfer and weak ties The short story is that creating opportunities for people to network within an organization – for the third floor to mingle with the second – can actually help to prevent corporate memory loss.

Can technology help to avoid the loss of at least some organizational knowledge?

Seidl made a decent case for knowledge capture by means of internal blogging and fitting those intra-blogs into a federation of blogs (which he called a channel). He also offered an example of the success that this sort of knowledge capture achieved at a certain unnamed company, where the CEO insisted that everyone get involved in the “project blogsite”.

Today (yes, I know it’s just 5 years later), I think a lot of KM folks & employees alike would argue that being forced to contribute to a blog is… just… not… going… to… work. Further, with failed intra-blogging attempts abounding and the ongoing rhetoric of blogs as time-wasters doomed to failure, you’d be hard-pressed to find an enterprise-sized organization with a strong blogging community — a blogging community that’s able to effectively capture knowledge and a blogging culture that’s willing to visit said blogs to ascertain knowledge.

It seems there’s no affirmative response to the KM question: Can technology effectively capture both implicit & explicit knowledge? (Urgh! I so wish someone could build an app that would actually do this!)

But what, then, can we do about memory leak, about knowledge walking out the door? Pei-Wen Huang (n.d.) suggested a few solutions:

• Create more apprenticeship programs
• Debrief at the end of a project so people in & out of the project are brought into the loop about wins, failures, etc.
• Establish a “corporate history”
• Build “knowledge profiles” so you know whom to go to in an org for certain subjects

Apprenticeship programs are, of course, potentially expensive (but more expensive than losing a seasoned employee with high institutional knowledge?). The others seem simply time-consuming.

…There’s always an excuse, isn’t there? But I’m pretty sure shareholders wouldn’t want to hear that the corps they’ve invested in are “unable to commit the time” to holding 30-minute power-debriefs at the end of projects to avoid repeating mistakes & wasting money………

Well, if anyone has a better idea or wants to chime in on the above ideas – or simply wants to post a link to a blog on the topic – feel free. Looking forward to it…

~joanna