Skip to main content
. Author manuscript; available in PMC: 2014 Sep 10.
Published in final edited form as: Appl Ergon. 2005 Sep 22;37(3):283–295. doi: 10.1016/j.apergo.2005.07.003

Table 10.

Ease of use: perceived ease of use (TAM); Ease of use/complexity (IDT); System should be simple and easy to use (STS)

Theory component Study results
Concerns System should be easy and quick to use, and should contribute minimally to extra workload
Barriers Reporting process should not be lengthy, drawn-out, or burdensome for users or the organization
Content Format should have facilitative, time-saving features (e.g., checkboxes, templates)
System design Users should be able to report quickly, at their leisure, and through other, integrated systems
Instructions Instructions should clarify system characteristics and how to use it