I agree with Larry and would just add that the best use of these is a
targeted use to a specific circumstance or need. We created one for our
Google migration that consisted of 4 simple statements of what to keep, and
3 of what to delete. This was designed for a large audience, and
essentially bulk clean-up. We created another on for our CMS migration that
had 4 decision points, and was more targeted to a smaller audience, and to
the specific kinds of records maintained on the system.

I think the complex decision trees simply overwhelm the intended audience,
and go in one ear and out the other.

As I mentioned before, we need to start aligning the specific obligations
of a given records custodian with their specific needs. If a given decision
tree includes items a custodian is not going to encounter on a regular
basis, they shouldn't include them.

-- 
Dwight Wallis, CRM
Multnomah County Records Management Program
1620 SE 190th Avenue
Portland, OR 97233
ph: (503)988-3741
fax: (503)988-3754
[log in to unmask]

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]