On 11 December 2013 20:57, Rob Weir <robw...@apache.org> wrote: > On Wed, Dec 11, 2013 at 2:40 PM, Gregory Zobel <zob...@wou.edu> wrote: > > I'd be happy to help develop the survey questions. > > We could devise probably 4-7 more questions without users resisting too > > much--long surveys annoy users. Ending with a couple of open-ended > > questions: what is most frustrating to you about AOO? what do you like > most > > about AOO? could also shed some light. > > > > From what I can tell, ASF has a policy of open content, open source, and > it > > would follow that open data is a part of this. It might be possible to > get > > engagement from parts of the academic usability community (i.e. analysis > > and discussion of what the different results mean, what to adjust, as > well > > as promoting AOO in academia) by sharing the usability responses/results > > openly. > > > > Just an idea. I know when I was training, it was hard to find usability > > data because most entities protect it like IP--can't give results, > > shortcomings, or improvements. Having the data would also be nice. > > > > We take user privacy seriously as well. Even though we're a US-based > non-profit we know that data protection laws vary and are stronger in > Europe, where many of our users are. So if we anticipate that we'll > want to make the raw survey results open (as opposite to just > aggregate summarize) we'll need to think about what additional steps > will be needed. For example, I usually track IP addresses in > LimeSurvey to detect multiple submissions. We'd need to strip that > out of any publicly released data. We'd also need a prominent > disclaimer/notice to the user, stating how the data will be used. >
I am not sure how known it is, but just in case: the european laws on this subject got more strict about 1 year ago. Now a disclaimer is not enough, the user most positively accept it (checkbox is valid). It the cookie story all over. rgds jan I. > > When we did the logo survey (results here [1]) we received over 5000 > responses in one week. So there is an opportunity to get a > substantial number of responses. > > If you want to start designing the survey questions a good place for > this might be on the UX section of our wiki [2]. Maybe a new page > linked to the UX Research Strategy page? Then send a link to that > page to the dev mailing list and anyone interested can follow along > and help. I'll volunteer to translate the survey design into > LimeSurvey. If we keep it short it should be possible to then get it > translated into a handful of languages. > > Regards, > > -Rob > > > > [1] http://survey.openoffice.org/reports/aoo40-logo-poll/ > > [2] https://wiki.openoffice.org/wiki/Apache_OpenOffice_User_Experience > > > > Best, > > gz > > > > > > On Wed, Dec 11, 2013 at 11:34 AM, Rob Weir <robw...@apache.org> wrote: > > > >> On Wed, Dec 11, 2013 at 1:29 PM, Gregory Zobel <zob...@wou.edu> wrote: > >> > Hi Rob, > >> > > >> > I like the idea of a satisfaction survey. I would suggest using an > >> industry > >> > standard, the SUS. > >> > http://www.measuringusability.com/sus.php > >> > > >> > It's been around for 25 years or so, it has provided reliable metrics, > >> and > >> > it could prove to be a rich data source. > >> > > >> > >> Thanks for passing that link along. The SUS approach might be even > >> more interesting to apply to a satisfaction survey of the OpenOffice > >> product itself. > >> > >> One thing to know: we do have access to a LimeSurvey instance > >> (http://survey.openoffice.org). We used it most-recently to gather > >> feedback for our AOO 4.0 logo contest. But it would be easy to use it > >> for a SUS survey as well. The advantage with LimeSurvey is it makes > >> it really easy to manage multiple translations of the survey, > >> something nice with our international user based. > >> > >> If we did this survey, what other questions would we want to ask, to > >> give data to correlate against? Maybe demographic factors like age, > >> sex, country. Maybe operating system used (usability might vary by > >> OS), certainly what version of OpenOffice is used, how long they have > >> been using OpenOffice. > >> > >> Regards, > >> > >> -Rob > >> > >> > Another alternative is to create the survey in Google Forms and then > >> embed > >> > it on sub-page. I've used this approach in many classes taught online, > >> and > >> > it goes pretty well. Plus you get more questions. > >> > > >> > Best, > >> > gz > >> > > >> > > >> > > >> > On Wed, Dec 11, 2013 at 10:24 AM, Rob Weir <robw...@apache.org> > wrote: > >> > > >> >> Google has a new service that makes it easy to add a website > >> >> satisfaction survey to a website. The free version has 4 questions > >> >> that are asked of 500 random website visitors each month. We would > be > >> >> given results on a monthly basis. (They also have a paid version of > >> >> this service where you can customize the questions, but I think the > >> >> free version is fine for our use). > >> >> > >> >> The questions are: > >> >> > >> >> I. Overall, how satisfied are you with this website? > >> >> > >> >> 1) Very satisfied > >> >> 2) Somewhat satisfied > >> >> 3) Neither satisfied nor dissatisfied > >> >> 4) Somewhat dissatisfied > >> >> 5) Very dissatisfied > >> >> > >> >> II. What, if anything, do you find frustrating or unappealing about > >> >> this website? > >> >> > >> >> III. What is your main reason for visiting this website today? > >> >> > >> >> IV. Did you successfully complete your main reason for visiting this > >> >> website today? > >> >> > >> >> 1) Yes, I was successful > >> >> 2) I'm still completing my reason for visiting > >> >> 3) No, I tried but wasn't successful > >> >> > >> >> You can see an example of what the survey looks like here: > >> >> > >> >> http://www.google.com/insights/consumersurveys/websat_example > >> >> > >> >> Adding it to the website is easy: a single line added to the header. > >> >> > >> >> Regards, > >> >> > >> >> -Rob > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >> >> For additional commands, e-mail: dev-h...@openoffice.apache.org > >> >> > >> >> > >> > > >> > > >> > -- > >> > --- > >> > Gregory B. Zobel, Ph.D. > >> > Assistant Professor of Educational Technology > >> > MSEd Program Coordinator > >> > > >> > Western Oregon University > >> > 345 N. Monmouth Ave > >> > Monmouth, OR 97361 > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > >> > >> > > > > > > -- > > --- > > Gregory B. Zobel, Ph.D. > > Assistant Professor of Educational Technology > > MSEd Program Coordinator > > > > Western Oregon University > > 345 N. Monmouth Ave > > Monmouth, OR 97361 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
