Mailing-List: contact ooo-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Date: Fri, 30 Dec 2011 23:58:00 -0500 (EST)
From: confluence@apache.org
To: ooo-commits@incubator.apache.org
Message-ID: <14920311.36972.1325307480019.JavaMail.confluence@thor>
Subject: [CONF] Apache OpenOffice Community > Survey Design
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated

Space: Apache OpenOffice Community (https://cwiki.apache.org/confluence/display/OOOUSERS)
Page: Survey Design (https://cwiki.apache.org/confluence/display/OOOUSERS/Survey+Design)


Edited by Graham Lauder:
---------------------------------------------------------------------
||*Survey Design for Marketing Survey of Announce List users*||

Preamble: The design of this survey will be guided by a number of factors.  The demographic of the respondents, the information that the project needs to glean from the respondents and the instrument for delivery.  Because of resource constraints, the latter is pretty much fixed at this point:  Email via the Announce lists.  This has distinct disadvantages in terms of our sample but it's what we have to work with at this point in time.  The results will tend to be slewed but there's not a lot we can do to alleviate that given that the information is needed in the short term rather than longer.

The first part will be pre-notification sent out to the announce lists,  with reply-to set to the marketing list.  All people who respond to that mail will be then sent the full questionnaire.  Pre-notes always give better response levels.

Questions will obviously be either marketing oriented, UX oriented or community oriented.  At this point my feeling is that we should lean toward UX, this to demonstrate that the project is open to listening to the wider user community.  Obviously there will be some crossover into the other areas but I think the broad focus should be UX.  (My opinion, open to discussion.)

Before we get into detail however the Goals of the survey need to be established:  What would we like the respondents to tell us, ie: Branding, User experience, future directions.  Are we after cold fact or opinion.  
And what do we want the survey to tell the respondents (surveys tend to tell the respondents a lot about the surveyor).  There will have to be a number of defining questions that tell us a bit about the respondent but only insofar as narrowing of demographics: age, broad location, NL, usage type(Home, work or study).  

||Goals||


||Pre-Notification Text||  


Resources:
[http://www.stats.govt.nz/surveys_and_methods/methods/survey-design-and-data-collection/guide-to-good-survey-design-2nd-edition.aspx] My survey bible, caution really gruesome PDF production and geared to Govt depts 
[http://www.surveysystem.com/sdesign.htm] Survey System Design guidelines 
[http://help.surveymonkey.com/euf/assets/docs/pdf/SmartSurvey.pdf?noIntercept/1]SurveyMonkey Smart Survey guidelines PDF 
[http://help.surveymonkey.com/euf/assets/docs/pdf/Response_Rates.pdf?noIntercept/1]  SurveyMonkey response rates advise PDF

Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action