Gathering usage data
Jonathan Watt
I'm at Libre Graphics Meeting and saw a talk [1] yesterday on how ingimp gathers
usage data for user interface refinement. It's worth watching the whole thing,
but the part of the video from 18:10 to 28:30 seems especially valuable for us.
E.g. in getting our "know your rights" message across. (It's pure gold around
21:50 :-) .)
Besides that, are we doing anything like this for gathering usage data for user
interface refinement?
Cheers,
Jonathan
Mike Beltzner
Thanks for the link, will look. Right now there's a project called
"Test Pilot" which we hope to turn into our primary mechanism for
usage data collection, and hope to develop into a place where people
can ask questions about "how do users currently?" or "what are users
trying to do when" and end up getting answers. Ambitious!
ref: http://labs.mozilla.com/projects/test-pilot/
Staff are coming on board, look for more from Test Pilot later this
summer.
cheers,
mike
> _______________________________________________
> dev-usability mailing list
> dev-us...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-usability
Justin Dolske
> It's worth watching the whole thing,
> but the part of the video from 18:10 to 28:30 seems especially valuable for us.
> E.g. in getting our "know your rights" message across.
Interesting work. I'd love to see the slow gears of the legal world
start to move based on this kind of data -- throwing a wall of legalese
at someone and expecting an "I Agree" click to be some kind of iron-clad
contractual agreement is full of all sorts of fail. Companies that bury
sleazy things in these kinds of terms&conditions should have to meet a
higher standard than just making the text bold.
I think we should aim in a different direction, though, by striving to
remove or mitigate the kinds of things that require interrupting a user
to grab their attention in the first place. For example, an
informataive, attention-grabbing EULA is better than a wall-of-text, but
no EULA is even better.
But this would be directly applicable to something like Test Pilot
(where we want to make sure we have informed consent from a user who
installs it, so users are not surprised later on). And it might be
interesting to think about things like malware/certificate warnings in
the context of this work.
Justin
Jonathan Watt
On 5/7/09 6:52 PM, Mike Beltzner wrote:
> Hey Jonathan,
>
> Thanks for the link, will look. Right now there's a project called
> "Test Pilot" which we hope to turn into our primary mechanism for
> usage data collection, and hope to develop into a place where people
> can ask questions about "how do users currently?" or "what are users
> trying to do when" and end up getting answers. Ambitious!
>
> ref: http://labs.mozilla.com/projects/test-pilot/
>
> Staff are coming on board, look for more from Test Pilot later this
> summer.
>
> cheers,
> mike
>
Aza
:)
-- aza | ɐzɐ --
Jonathan Watt
> On 5/7/09 8:48 AM, Jonathan Watt wrote:
>
>> It's worth watching the whole thing,
>> but the part of the video from 18:10 to 28:30 seems especially valuable for us.
>> E.g. in getting our "know your rights" message across.
>
> Interesting work. I'd love to see the slow gears of the legal world
> start to move based on this kind of data -- throwing a wall of legalese
> at someone and expecting an "I Agree" click to be some kind of iron-clad
> contractual agreement is full of all sorts of fail. Companies that bury
> sleazy things in these kinds of terms&conditions should have to meet a
> higher standard than just making the text bold.
Indeed.
> I think we should aim in a different direction, though, by striving to
> remove or mitigate the kinds of things that require interrupting a user
> to grab their attention in the first place. For example, an
> informataive, attention-grabbing EULA is better than a wall-of-text, but
> no EULA is even better.
Sure, but as I said to Chris I'm more interested in seeing these tricks used to
more effectively communicate the "Mozilla message" to a mass audience in the
"know your rights" thing we use than in EULAs (although that's interesting too).
> But this would be directly applicable to something like Test Pilot
> (where we want to make sure we have informed consent from a user who
> installs it, so users are not surprised later on). And it might be
> interesting to think about things like malware/certificate warnings in
> the context of this work.
Indeed. It would be great to do all we can there to head off crazy accusations
of Firefox turning into spyware.
Jonathan