Email: KM killer or KM salvation?Posted: January 25, 2011
We know these things:
- In an emergency, critical roles can be held by a series of staff, all involved for a short period. They might be on site and involved for a couple of months, a couple of weeks, or even a handful of days.
- In emergencies — and at other times – a lot of the core discussions and decisions are chiefly documented in, or at least circulated by, email.
- When staff leave a job a or country, their email repositories go with them. They’re not available as a source of knowledge or narrative about what’s gone on for the team, even if they stay working for your agency elsewhere.
We know these things cause this problem:
- When institutional knowledge about even recent day to day decisions is unavailable or difficult to obtain for new staff, it has a detrimental impact on our ability to work coherently internally, as well as with external actors like partners and donors. In short, it contributes to institutional idiocy and is a barrier to getting on with good programme delivery across the phases of a response.
We have ways to try to deal with it:
- Printing emails to place on hard copy project or partner files; saving off critical emails and attaching them to management information systems; ensuring that communications docs get stored coherently in ever-so-tidy folder structures on group drives…. blah. Unless you have OCD or nothing better to do, this stuff makes you weep.
- The problem is that these are all highly time consuming during a period when the time of staff and managers is at an absolute premium. It is not storing, managing or sharing knowledge inside the critical workflow. Which means that all too often, basically it doesn’t happen. And the contents of network/server drives typically can’t be easily accessed between offices, between countries, with HQ – all barriers to highly useful transparency and knowledge management.
- We can pretend that handover notes and briefings deal with this issue. But all too often handovers are limited, or recruitment delays mean that the right staff don’t actually cross paths. No, handovers are not a robust or reliable approach. Nor is the belief that we can reduce staff turnover to the point where this isn’t going to be a problem.
A way to improve the situation might work like this:
- So we all have project/grant/financial management information systems, right? And these systems have unique IDs for each project and/or grant, right? So…. what if key emails about a project or donor grant, could simply be CC’ed to an address unique to that project/contract (eg: Grant0123@HRI.org, ProjectPKN93@HRI.org), where it would be swooshed off somewhere to be accessible and searchable by the successor project coordinator and other team members?
- The key benefit from this approach is that it would be quite “frictionless” for front line staff at the point that information and internal thinking and daily decision making needed to be stored – no more difficult or time consuming than adding a cc recipient to an email.
- I’m not suggesting that all emails would need to be stored – indeed an unmediated dump of a PC’s emails wouldn’t be an improvement. But picture an incoming project coordinator being able to skim through the last month’s key email communications with staff, partners, donors and HQ in the 72 hours before arriving in post. You’d arrive with a substantial shortcut to situational awareness. Picture being able to have access to a log like this when doing an after action review or evaluation down the road.
- I’m agnostic where that repository might be – so long as it’s a web browser accessible platform, meets all the standard security requirements so only accessed inside the organisation, and is simply organised on the surface but well searchable.
- It would be the work of a couple of days to set up a ‘pilot’ of this using (say) HRI-PKN93@gmail.com. And while I’m enormously in favour of skunkworks projects in the main, on this one it’s not getting off on the right foot – my shop has more than enough information stovepipes as it is; this thought bubble can’t contribute to that problem. And never mind lobbing potentially confidential information onto a gmail server.
I guess the bottom line is, is that for emergency/relief NGOs, a critical part of the organisation (ie: field staff in emergencies) are often quite realistically constrained in going beyond plain trusted old email for their communication, and their inboxes for their knowledge management, into fancy tools like Sharepoint – which the rest of the tail back towards HQ may have already adopted, or be very keen to have in ubiquitous use. They’ll just never get there, and INGOs must bite the bullet and effectively interface with these staff where they are and how they work. Email is simply where some of our most essential people work; that’s unlikely to change; we should have core approaches to KM that connect with these facts – and are absurdly easy at the point of use to boot.
So now I’m looking for someone who can tell me of a system that already works like this, or conversely, why it’s a rubbish idea for a reason I’ve overlooked.