I've written technical requirements, detailed user scenarios (Business
Processes), mapped record schedules to taxonomies, diagrammed work
flows, and hand-held users through the bone jarring transition to
e-records. Yet I'm still not comfortable selling my ERM skills to IS.
It's true that I do not know the ins and outs of code nor the proper
pull downs involved in ERMS implementation. How deep does our IS
experience need to go before RMs feel qualified to lead e-record
programs? 


Thomas Love, CRM
 
Valero Energy Corp.
One Valero Way
E2-198E
San Antonio TX 7 8249
210 345 3718
 

So my questions to the list are this:
1. What does it take to get Records Managers (we handle paper) up to the
plate?

2. How do Records Managers (they are the folks in the basement) capture
the attention of management that they can be of more value than just
being an early warning system for a broken pipe?

3. How long will there be Records Managers if we don't figure out how to
do 1 & 2 above very quickly?

Bill R

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