Great idea for do user testing! My thoughts: - For new users start with the what brought you.. poll, then from that build a few tests and get volunteers to try some specific tasks. The idea of a few users doing specific tasks to look for the really glaring stuff sounds good. - start small and build from those findings. Only go larger if the small tests aren't productive say at least 10 hot items. - Get screen casts with voice inputs on what they are trying to do and why. - do not limit it to the new users, but the user levels should be different studies. - I see no reason why this could not be applied to potlatch, JOSM, merkator (any other OSM software) and the wiki as well. Even to getting maps on a garmin GPS or what ever else new users might have as reasons for signing up.
A side item, where making tasks easier is problematic or fails. Do video tutorials with a transcript or written instructions to go with it. -- Dale Puch On Tue, Mar 9, 2010 at 9:36 AM, Ian Dees <[email protected]> wrote: > On Tue, Mar 9, 2010 at 8:02 AM, SteveC <[email protected]> wrote: > >> * Once in some very small sample size (perhaps between 1 in 1,000 and 1 in >> 10,000 signups) a popup appears >> * The popup says something like "Hi! We'd really like to know why you came >> to OSM" and they say simply why. This is open ended on purpose so we catch >> as many things as we can, not just what we're looking for, but things we >> won't expect. >> * They're offered to record a short (10 minute max) screencast of them >> trying to achieve whatever it is (like look at a map, find OSMers, add a PoI >> and so on) >> * That screencast is analyzed in aggregate with many others by Bolt | >> Peters with all their expertise in doing this stuff, and they come back with >> a set of findings. >> > > Won't this skew our answers a little bit? Users will have to download or > install some sort of screen capturing application and answer this question. > If I were a novice OSM user and saw this request *and* had to figure out > Potlatch or JOSM, I would be even more inclined to back out of fixing the > location of the ice cream stand. > > >> What should our goals be? (General UX? How good/bad signup is? How >> good/bad editing is? How is it finding info?) >> How often should we ask a signup for feedback? (the more the better but we >> can only look at so many) >> How can we include more crowd source feedback? (I think of asking random >> signups for feedback as crowdsourcing it) >> What else should we think about? >> > > I think editing of various kinds should be looked at: anywhere from simple > POI adding/changing (how do they figure out how to describe the POI?) to > adding/changing a road network (how do they decide what kind of road it > is?). > > Thanks for getting this rolling Steve, I think it'll help! > -Ian > > _______________________________________________ > Talk-us mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/talk-us > >
_______________________________________________ Talk-us mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-us
