Priorities 1 - 10 when you need a person to interact with a records system directly.

1. User experience.

2. User experience.

3. User experience.

4. User experience.

5. User experience.

6. User experience.

7. User experience.

8. User experience.

9. User experience.

10. User experience.

If you focus on anything else, they probably won't use it.

This doesn't mean that you can't do functional classification (even though it destroys adoption).

It doesn't mean you can't ask for metadata (even though historical experience has also shown that it destroys adoption).

It just means that you have to ask yourself a question before you implement ANYTHING in the system.

Does it improve the experience of the user doing their job?

The important thing about asking this question, is that you can't answer it.

The person who is supposed to do the work also can't answer it at design time.

The tendency of people asked if they want something that sounds like they should want it, particularly when it's positioned without a cost - is to say yes.

Then they have to pay for it - and because the cost comes after the design decision, they get stuck with it.

This is why so many "good designs" fail at implementation. The design choice is made by someone who doesn't have to pay the cost of the design in effort every day.