The ten reasons why ease of use doesn’t happen on engineering projects, from UIWEB.COM.
Here are the 13 reasons. The article has outlined some decent solutions for each of these reasons. It’s a good article. Worth reading.
1. Ease of Use in not an explicit project goal.
2. Ease of use is not defined in actionable terms.
3. Decision makers do not see the tradeoffs.
4. The unseen impact on ease of use on system/code architecture.
5. Confusion over how to use customer data.
6. Confusion over who the customer is. (user vs. customer vs. client)
7. Technical focus dominates the view of the project.
8. Diffusion of design authority. (Too many cooks)
9. Feature based design vs. scenario/task based design.
10. No connection made between business goals and ease of use.
11. General Incompetence. (#11 = the spinal tap commemorative entry)
12. The wrong people are involved.
13. Lack of familiarity with the creative process.
Comments are Open (0)
Posted at 12:00 PM