> My organisation has now purchased its EDRMS solution. My current view
> is
> that we manage e-mails within the EDRMS environment. I am aware of a
> number of issues this brings, string e-mails, possibly duplicated
> saving
> (although we should be able to identify the latter), capturing
> ephemera,
> deleting important e-mails without saving as a record etc etc.
>
> My question is... Will colleagues moving to EDRMS be seeking to follow
> a
> similar path? Or, do you consider the risk such that you will be
> looking
> for alternative means of capture? and if so what are your current
> proposals.
It's all about policy and training... and then more training, and then
just maybe a LITTLE MORE TRAINING =)
There are a number of auto-classification tools on the market, but they
have limited success and all of them require a lot of customization and
"tweaking" to have any reasonable level of functionality. The day will
come when the "best of breed" will be 75% out of the box, once you
program in your basic rules... but there will be a long time before
most organizations will be satisfied with 75% unless you have a VERY
LOW volume, are able to deal with the remaining 25% manually (until it
"learns" to do better), or are in a non-regulated situation where you
aren't concerned about effectively managing your e-mail as a record.
You need to get buy-in from high on the management food chain to
establish policies that are enforceable through training and set up the
ability to deliver "train-the-trainer" sessions to push it father down
to establish local points of contact, then provide guides and
additional one-on-one training as necessary... and you need to convince
individuals that it's worth the effort to do this, or there's no
buy-in. Find out what makes it valuable to them, and use this
increased functionality as selling points to get them on board.
Larry Medina
|