Week 9 Discussion Topic: NEAT Warnings
Goal for today: Design a warning for the encrypted email interface you are designing as part of your next assignment.
Warning
For your next assignment, you are working on desinging a new interface for encrypted email. What happens if someone sends you an encrypted email, but 1) it isn’t signed, or 2) is signed by the wrong person? Your interface will need to display a warning to them to let them know that something potentially dangerous is going on.
Today, we are going to try to design that warning using Microsoft’s NEAT warning ideas.
NEAT Warnings
- Necessary
- Explained
- Actionable
- Tested
SPRUCE Explanations
- Source of decision
- Process to make a good decision
- Risk of making a bad decision
- Unique Knowledge of the user
- Choices, with a recommendation
- Evidence to help
Necessary? Timing?
Start by asking is this warning necessary? Why? Can we just make a decision for the user? Is there information that only the user has that is important?
Also, part of necessary is thinking about timing – when should we display this warning? Should this be always up (“beware unsigned messages”)? Should this only be displayed as needed? Before or after decrypting and displaying the message?
What form should the warning take? Should it be a popup window? Should it cover up the message, or be displayed next to it / above it? Should it be active (the user has to interact with it) or passive (the user just sees it)? If active, how active?
Warning Content
Next, we need to think about the content of the warning. There are a couple of things to work on here
SPRUCE Explanation
Let’s use the SPRUCE framework to figure out what the warning should say. What information needs to be conveyed in the warning? Go through all 6 parts of the SPRUCE framework, and write down an answer for each. This is just for you right now; we will figure out how to convey it to users later.
Actionable
Warnings are requests for action; they ask the user to do something – something that the program can’t just do on its own. Next, we need to carefully think about what that action is; what are we asking users to do?
Think through possible scenarios / use cases where this warning might pop up. Think about both benign (safe) and malign (dangerous) use cases. What is the user trying to do? What is an attacker trying to do (in a malign case)? What is the sender trying to do (in a benign case)?
For each use case, write down what the correct action is. What do you WANT the user to do? (aside: Why can’t the program just do that for the user?)
Wording
Next, we need to communicate all of the above stuff to the user. How might we word this to clearly convey to users this warning? Brainstorm multiple ways to communicate this. Try coming up with different versions, such as:
- A “sky is falling” type warning that is overly worried
- A version that downplays dangers
- A version that is balanced between these two extremes
- A version that reminds users of why they are being asked
- A version modeled after some existing warning (like Chrome’s TLS certificate warning)
- A multi-step version that asks the user questions and provides advice
Tested
Next, we need to test our warnings. We are going to do 2 tests – a heuristic evaluation and an expert review.
Heuristic Evaluation
For the heuristic evaluation, go back to the NEAT/SPRUCE framework, and check each of your warning messages. Does it check all of the boxes? Explicitly make a speadsheet-like chart – warnings on the left, NEAT/SPRUCE principles across the top. Put in checkmarks.
Which one looks best?
Expert Review
Take your best candidate warning, and create a mock-up. Draw out a version of the warning with the text and any icons/images you want. Basically, create a paper prototype of the warning.
Next, share this paper prototype with the group next to you, and ask for feedback. See what they think. (At the same time, you can review their ideas.)
As you review your neighbor’s warning mockup, try to be helpful. Think about what is needed, and remember how hard it is to design a good warning.