Teqleez Motley:
>> sajolida:
>>> I started dumping ideas on doing a quantitative survey of our user base:
>>> https://tails.boum.org/blueprint/user_survey/
Hi Teqleez,
I think it's your first email to the list, so welcome!
> I wonder if there should be 2 distinctly different questions about missing features vs. problems/pending bug-fixes.
Note that so far I wanted to discuss the research questions that we want
to answer in the survey. Not yet the questions to ask in the survey.
This would be the next step.
> a) Which features are most missed
> b) Which unfixed/outstanding bug fixes/reported problems are preventing more use of Tails
As you can see in the current research questions, I was focusing more on
knowing better who our users are and what they use Tails for. I bet that
starting with answering these questions will already lead to a survey
that will be long enough (I want it to be quick and simple to answer)
and great findings.
I'm afraid of opening the door for features requests because:
* We currently don't have the capacity of addressing them. We are
still struggling to fix usability issues that we've known for years.
In this regard, we're more interested in learning how to prioritize
them than learning new ideas. That's why I propose to learn about the
"user tasks" instead.
* Asking people what they want is not usually such a great idea when
trying to improve usability. See:
Jakob Nielsen's First Rule of Usability: Don't Listen to Users
(a bit provocative on purpose...)
https://www.nngroup.com/articles/first-rule-of-usability-dont-listen-to-users/
About the famous quote misleadingly attributed to Henry Ford:
"If I had asked people what they wanted, they would have said faster
horses.":
https://www.entrepreneur.com/article/290410
* It's the kind of open questions that make surveys much longer to
answer. It might be good to have 1 or 2 open questions at the end but
we should be careful about keeping the survey super short. And
definitely making the open questions optional.
> Suggested new question:
> c) Do you think it is important/possible that the current start page (where Tails is configured during startup) could be further improved/simplified or is it suitable/good enough in its current form?
By start page, do you mean this:
https://tails.boum.org/doc/first_steps/startup_options/tails-greeter-welcome-to-tails.png
or this:
https://tails.boum.org/home
?
These kinds of problems and possible simplifications are best discovered
doing usability testing. We already did usability testing of Tails
Greeter ("Welcome to Tails!") before releasing it so I would say that's
not the hottest one of our interfaces.
> Btw:
> - Maybe the survey invitation email could also include a (visual) example of exactly how easy it is and where to get involved in reporting problems and discussing feature requests, for those who are still on the fence in terms of active participation.
The survey would be pointed to from the homepage of Tor Browser in
Tails, and not by email. This way we can potentially target everybody
using Tails, not only the people we have the email from.
> Perhaps make a page "showcase" of the "best" feature requests that were taken into account and implemented during the last x months/years, with links/extracts from their actual issue queue messages?
Unfortunately, this is not something we have the resources to do a lot,
so I don't think that the showcase would be very exciting :)
--
sajolida
%20Which%20features%20are%20most%20missed%0A>%20>%20b)%20Which%20unfixed/outstanding%20bug%20fixes/reported%20problems%20are%20preventing%20more%20use%20of%20Tails%0A>%20%0A>%20As%20you%20can%20see%20in%20the%20current%20research%20questions,%20I%20was%20focusing%20more%20on%0A>%20knowing%20better%20who%20our%20users%20are%20and%20what%20they%20use%20Tails%20for.%20I%20bet%20that%0A>%20starting%20with%20answering%20these%20questions%20will%20already%20lead%20to%20a%20survey%0A>%20that%20will%20be%20long%20enough%20(I%20want%20it%20to%20be%20quick%20and%20simple%20to%20answer)%0A>%20and%20great%20findings.%0A>%20%0A>%20I'm%20afraid%20of%20opening%20the%20door%20for%20features%20requests%20because:%0A>%20%0A>%20*%20We%20currently%20don't%20have%20the%20capacity%20of%20addressing%20them.%20We%20are%0A>%20%20%20still%20struggling%20to%20fix%20usability%20issues%20that%20we've%20known%20for%20years.%0A>%20%20%20In%20this%20regard,%20we're%20more%20interested%20in%20learning%20how%20to%20prioritize%0A>%20%20%20them%20than%20learning%20new%20ideas.%20That's%20why%20I%20propose%20to%20learn%20about%20the%0A>%20%20%20%22user%20tasks%22%20instead.%0A>%20%0A>%20*%20Asking%20people%20what%20they%20want%20is%20not%20usually%20such%20a%20great%20idea%20when%0A>%20%20%20trying%20to%20improve%20usability.%20See:%0A>%20%0A>%20%20%20Jakob%20Nielsen's%20First%20Rule%20of%20Usability:%20Don't%20Listen%20to%20Users%0A>%20%20%20(a%20bit%20provocative%20on%20purpose...)%0A>%20%0A>%20%0A>%20https://www.nngroup.com/articles/first-rule-of-usability-dont-listen-to-users/%0A>%20%0A>%20%20%20About%20the%20famous%20quote%20misleadingly%20attributed%20to%20Henry%20Ford:%0A>%20%20%20%22If%20I%20had%20asked%20people%20what%20they%20wanted,%20they%20would%20have%20said%20faster%0A>%20%20%20horses.%22:%0A>%20%0A>%20%20%20https://www.entrepreneur.com/article/290410%0A>%20%0A>%20*%20It's%20the%20kind%20of%20open%20questions%20that%20make%20surveys%20much%20longer%20to%0A>%20%20%20answer.%20It%20might%20be%20good%20to%20have%201%20or%202%20open%20questions%20at%20the%20end%20but%0A>%20%20%20we%20should%20be%20careful%20about%20keeping%20the%20survey%20super%20short.%20And%0A>%20%20%20definitely%20making%20the%20open%20questions%20optional.%0A>%20%0A>%20>%20Suggested%20new%20question:%0A>%20>%20c)%20Do%20you%20think%20it%20is%20important/possible%20that%20the%20current%20start%20page%20(where%20Tails%20is%20configured%20during%20startup)%20could%20be%20further%20improved/simplified%20or%20is%20it%20suitable/good%20enough%20in%20its%20current%20form?%0A>%20%0A>%20By%20start%20page,%20do%20you%20mean%20this:%0A>%20%0A>%20https://tails.boum.org/doc/first_steps/startup_options/tails-greeter-welcome-to-tails.png%0A>%20%0A>%20or%20this:%0A>%20%0A>%20https://tails.boum.org/home%0A>%20%0A>%20?%0A>%20%0A>%20These%20kinds%20of%20problems%20and%20possible%20simplifications%20are%20best%20discovered%0A>%20doing%20usability%20testing.%20We%20already%20did%20usability%20testing%20of%20Tails%0A>%20Greeter%20(%22Welcome%20to%20Tails!%22)%20before%20releasing%20it%20so%20I%20would%20say%20that's%0A>%20not%20the%20hottest%20one%20of%20our%20interfaces.%0A>%20%0A>%20>%20Btw:%0A>%20>%20-%20Maybe%20the%20survey%20invitation%20email%20could%20also%20include%20a%20(visual)%20example%20of%20exactly%20how%20easy%20it%20is%20and%20where%20to%20get%20involved%20in%20reporting%20problems%20and%20discussing%20feature%20requests,%20for%20those%20who%20are%20still%20on%20the%20fence%20in%20terms%20of%20active%20participation.%0A>%20%0A>%20The%20survey%20would%20be%20pointed%20to%20from%20the%20homepage%20of%20Tor%20Browser%20in%0A>%20Tails,%20and%20not%20by%20email.%20This%20way%20we%20can%20potentially%20target%20everybody%0A>%20using%20Tails,%20not%20only%20the%20people%20we%20have%20the%20email%20from.%0A>%20%0A>%20>%20Perhaps%20make%20a%20page%20%22showcase%22%20of%20the%20%22best%22%20feature%20requests%20that%20were%20taken%20into%20account%20and%20implemented%20during%20the%20last%20x%20months/years,%20with%20links/extracts%20from%20their%20actual%20issue%20queue%20messages?%0A>%20Unfortunately,%20this%20is%20not%20something%20we%20have%20the%20resources%20to%20do%20a%20lot,%0A>%20so%20I%20don't%20think%20that%20the%20showcase%20would%20be%20very%20exciting%20:)%0A>%20%0A>%20--%20%0A>%20sajolida%0A>%20%0A>%20 "Reply to this message")
