path: root/wiki/src/blueprint/usability_testing.mdwn
diff options
authorTails developers <>2014-03-08 11:28:54 +0000
committerTails developers <>2014-03-08 11:28:54 +0000
commit08bb538eae578cd5aacd3e940bd7dde5488508dd (patch)
treecd623d35d82343295a183e781b5047be6a0a0d85 /wiki/src/blueprint/usability_testing.mdwn
parent3e13d6aed55f4b834b99d2a409cf08fed293d788 (diff)
Add a few guidelines.
Diffstat (limited to 'wiki/src/blueprint/usability_testing.mdwn')
1 files changed, 13 insertions, 0 deletions
diff --git a/wiki/src/blueprint/usability_testing.mdwn b/wiki/src/blueprint/usability_testing.mdwn
index 29909de..4880505 100644
--- a/wiki/src/blueprint/usability_testing.mdwn
+++ b/wiki/src/blueprint/usability_testing.mdwn
@@ -8,6 +8,9 @@ and are not attractive to potential users. They want to play a role in fixing
this, by building a bridge between the designers, graphics artists, and UI
experts community on the one hand, and the FOSS people on the other hand.
Here are a few exercises that we could propose them:
- Start Tails and end-up in an environment in their favourite language.
@@ -23,3 +26,13 @@ Here are a few exercises that we could propose them:
- Go through an incremental upgrade.
- Create a document and save it encrypted on your Tails USB stick.
- Find something useful you could do for Tails.
+* We should focus on things *we* can improve. E.g. we can easily
+ improve Tails Greeter, but we won't redesign Pidgin OTR ourselves.
+* Participants to the usability testing session will be first briefed
+ about what Tails is about, and its main distinguishing properties.
+ However, one should not assume they are used to handling security
+ concepts such as contextual identities, anonymity set and all.