Mimi:
"Super Users" are a database software concept in general, not just in
the EDMS/ERMS arena. For instance, we are currently looking at a new
Customer Information System (CIS) from a large international software
vendor and "super users" are a part of the process. They are used in
two ways - as a sort of business function representative for design
(rather than the designers having to go to every user of that business
function) and as part of a "train the trainer" approach for user
trainer. Most large software vendors offer training of "super users"
who are expected, in turn, to train other users. The private sector is
used to the "super user" concept more so than state and local government
(I'm not sure about the Feds) because of the size and cost of the
systems they implement on a more regular basis.
Ginny Jones
(Virginia A. Jones, CRM)
Records Manager
Information Technology Division
Newport News Dept. of Public Utilities
Newport News, VA
[log in to unmask]
-----Original Message-----
From: Records Management Program [mailto:[log in to unmask]] On
Behalf Of Mimi Dionne
Sent: Tuesday, May 03, 2005 4:30 PM
To: [log in to unmask]
Subject: Re: Super Users
Hi Larry,
Sir, you raise some interesting points...I'm curious though--from my
perspective, I've only experienced them in a governmental records
setting...do you think "Uber Users" are more common there than in
corporate implementations?
Your friend in standards,
Mimi
-----Original Message-----
From: Records Management Program [mailto:[log in to unmask]]On
Behalf Of Larry Medina
Sent: Tuesday, May 03, 2005 3:23 PM
To: [log in to unmask]
Subject: Re: Super Users
>
> I'm curious: does anyone have an idea of the history of Super Users in
> EDMS/RMA implementations? How S.U.s came about in general and why we
> adopted them into our projects--is it an offshoot of the established
> idea of Records Coordinators scattered throughout the organizational
departments?
Hi Mimi!!
Well, for my money the adoption of bringing super users into the
equation early on was based on the failures in attempting to implement
EDMS without having done it before... sort of an offshoot of "Lessons
Learned" on why so many implementations failed. It's the same old story
of someone at a high level in an organization saying "we need an EDMS"
without understanding WHY you need one or WHAT you're going to do with
it... I think in many cases it was because someone gave a REAL GOOD
sales presentation or someone else they know in a competing company got
one and it was a case of "system envy" =) For years, many of us in RIM
have attempted to fight off the desire of management to "throw IT
solutions at unanalyzed RIM problems".. or what I prefer to think of as
the "Cheshire Cat Scenario":
*"Alice came to a fork in the road. 'Which road do I take?' she asked.
'Where do you want to go?', responded the Cheshire cat. 'I don't know.'
Alice answered. 'Then,' said the cat, 'it doesn't matter."*
If sufficient work is done up front with the "Uber Users" to determine
what they do, how they do it and whythey do it that way, then the
development of front end interfaces is much more logical, as is the
manner in which data is indexed and systems are structured.
Larry
List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
|
