Description
Inspect software against five politeness requirements (respect, visibility, helpfulness, remembering, responsiveness) to find selfish behaviour that drives users to uninstall.
Whitworth defines politeness as giving users more choice than the law requires, in ways that are desired, rightful and optional. Selfish software commits social errors: changing settings, running hidden processes, nagging, forgetting answers. The inspection checks five requirements. Respect: no pre-emptive acts on user-owned or shared resources. Visibility: declare who you are and what you are doing. Helpfulness: offer clear, understandable choices, not choices hidden behind other choices. Remembering: carry past choices forward. Responsiveness: accept correction and do not interrupt. Findings are classified into impolite types (blameware, pryware, nagware, strikeware, forgetware) with remedies such as meta-choices like 'Yes to all'. It is judgement-based with no severity scale, but its choice-dependency analysis of installers and settings is concrete and repeatable.
Attributes
- Discipline
- Usability & Evaluation
- Loss type
- Latent
- Stage
- Evaluation, Post-launch
- Data
- Analytical / expert
- Effort
- Hours
Steps
- Install the software and record every choice offered, including hidden or pre-selected ones (choice dependency analysis).
- List background processes and startup items it adds and check whether each declares itself.
- Check for pre-emptive changes to shared or user-owned resources such as home page, file associations and startup.
- Check whether registration asks for data the task does not need.
- Use the software over several sessions and note repeated questions and forgotten choices.
- Classify findings by requirement and impolite type, and propose fixes such as meta-choices and remembered preferences.
Sources
- The Social Design (Whitworth & Ahmad, 2014)
Also known as
- Politeness heuristics
- Polite computing checklist
- Selfish software audit
Categories
- User Research
- Usability & Evaluation