An evaluation is an important part of the product development process, and any kind of project if improvement is sought. Reading about the DECIDE framework gave some essential insight on how an evaluation can be planned and executed. Determining a clear goal is key to a working and project-improving evaluation, and a task that every project group has to face. The challenge is to determine realistic, achievable goals and ask questions that encourage reflections from previous experiences. The next step can be quite hard, especially for the inexperienced. The choice of evaluation method can greatly impact the outcome of the evaluation. The questions that might be asked during an interview should properly reflect the thesis of the project. This felt quite hard in our own field study earlier in the course, as I have not done a evaluation or field study previously.
Different kinds remotely controlled and designed evaluation are very common in today's society. If you for example download a new app on your phone it’s sometimes likely that a popup-screen is going to come up and ask for your user data anonymously. Therefore you as a developer can get access to a lot of information on different platforms and then troubleshoot for example bugs and interface misconceptions more effectively. Inspection methods are however often used as a process for identifying and analyzing of problems in usability of a product using Heuristic evaluations and walkthroughs. Heuristics is a set of usability principles developed by Nielsen and some of his colleagues that experts uses to evaluate whether certain user-interface elements conform to tested principles.
Question: What are the risks of setting an ambiguous goal for an evaluation?
No comments:
Post a Comment