Usability testing - Communicate Results and Findings - Selling Findings to Stakeholders
6 important questions on Usability testing - Communicate Results and Findings - Selling Findings to Stakeholders
Name some problems in convincing other about the need to take action on the usability finding?
- Some stakeholders are skeptical towards usability and usability tests.
- Some developers, for example, view “their” user interface as an extension of themselves and might take it personally when someone finds fault with it.
Why must the usability tester understand the maturity of an organization regarding usability issues?
In organizations with low usability maturity, it may only be possible to make the consequences of ignoring usability visible by performing usability testing and then “selling” the findings in a convincing manner.
What's the risk of certain stakeholders with a strong opinion and who are skilled at arguing their case?
Some times others are willing to hold back their own opinions. There is a risk that valid usability problems may be dismissed because opinions dominate the discussion and not facts.
- Higher grades + faster learning
- Never study anything twice
- 100% sure, 100% understanding
What can be done the avoid that stakeholders are dismissing usability problems?
- Involve them in the risk assessment
- Invite them to participate in writing and reviewing the usability test plan, the usability test scripts and, in particular, the usability test tasks
- Invite them to participate in the recruitment process, in particular defining the test participant profile and creating the recruitment screener
- Invite and encourage them to observe usability tests
- Make it easy for them to observe usability test sessions
- Involve them in the reviewing the usability test report
How can you make it easier for stakeholders to observe usability test sessions?
- Schedule usability test sessions at times that are convenient for stakeholders, for example on Friday afternoons
- Advertise usability test sessions widely, and indicate that observing only part of a usability test session is also acceptable
- Carry out usability test sessions at locations that are convenient for stakeholders, such as where stakeholders work, instead of at a remote location
- Make it easy for stakeholders to observe usability test sessions as a group
- Watching and discussing can convince skeptical stakeholders of the benefits of usability testing.
How are stakeholders dealt with in agile software development?
The Product Owner is a source of information about usability requirements and helps to clarify situations where opinions differ (e.g., when rating the severity of usability findings).
The “whole-team” approach adopted in agile software development encourages the regular exchange of views between team members and imparts a sense of shared ownership regarding product quality (including usability).
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding