W3C home > Mailing lists > Public > public-webplatform@w3.org > January 2013

Re: Contributor survey

From: Chris Mills <cmills@opera.com>
Date: Fri, 25 Jan 2013 09:24:19 +0000
Cc: Doug Schepers <schepers@w3.org>, Andre Jay Meissner <ameissne@adobe.com>, Scott Rowe <scottrowe@google.com>, "public-webplatform@w3.org" <public-webplatform@w3.org>
Message-Id: <C41CEFA6-5246-414F-816E-4660C2EFEFCB@opera.com>
To: Eliot Graff <Eliot.Graff@microsoft.com>
+1 thanks for the great work Scott. I have a few additional points to add on top of what others have said

* #6 - typo, "Sight architecture"
* #11 - seems weird, I don't really get what it is about or why it is there. Why do we need to know this? It would be better to have it as a checkbox list, i think, and say something like "what feedback would you like to share with us - a) general impressions after using/contributing to the site for some time, b) feedback about a recent doc sprint, c) initial feedback after I've just seen the site for the first time"
* #12 - it would be much better to provide a drop down list of recent doc sprints to choose from, and update this after each doc sprint is run. Making the user remember and have to go look up the date can be the sort of annoying detail that stops people from bothering to fill in a survey
* #25 - is "incumbent" the right word here? Something like "default" would be easier to understand for non-native English speakers
* "Scoring usability" section just before #26 - "we failed here" should be "we are failing here", as in this case, it is not an event that has passed - it is ongoing.
* Overall - it feels very long and daunting, but it didn't in fact take me very long to run through. Could we add something to make it feel less daunting, like a time taken estimate at the start (this should only take you 10 minutes), and/or a progress bar indicator? or page 1/4, 2/4  ? 

Chris Mills
Opera Software, dev.opera.com
W3C Fellow, web education and webplatform.org
Author of "Practical CSS3: Develop and Design" (http://goo.gl/AKf9M)

On 25 Jan 2013, at 04:33, Eliot Graff <Eliot.Graff@microsoft.com> wrote:

> Thanks so much for pulling this together!!!!!!
> This is loooooooooooooooooong. We see participation drop off with way fewer questions than this. I suspect that the first page might get results and then.......
> For what's there:
> Question 13: Add "Word of mouth"
> Questions 26-31: provide links to example pages where appropriate?
> Question 35: Need a "Other" or none of the above
> Thanks,
> Eliot
> -----Original Message-----
> From: Doug Schepers [mailto:schepers@w3.org] 
> Sent: Thursday, January 24, 2013 3:30 PM
> To: Andre Jay Meissner
> Cc: Scott Rowe; public-webplatform@w3.org
> Subject: Re: Contributor survey
> Hi, Scott-
> Looks great!
> I think Jay has some good points.
> I noticed a couple of things, too:
> * #3 s/company/organization/
> * Maybe tell people how many pages it is?
> * Move the last question, #39, to the 3rd page, to make the survey seem shorter... I always dread hitting 'continue' in surveys.
> Regards-
> -Doug
> On 1/24/13 5:22 PM, Andre Jay Meissner wrote:
>> Hey Scott,
>> love to see this evolving + great work! Here are my comments:
>> 1. As a rule of thumb, ideally, the first survey page should not
>>    contain more than *one* absolute no brainer question. Something like
>>    "yes I want to proceed/no", "I am male/female", "I like/dislike"...
>>    sth like that. Do not ask for the userID as the first question, do
>>    this as the LAST one (when the form is filled out. Yes, you can
>>    invite for lunch at that later time as well ;))!
>> 2. I would move the whole "You and your work" section to the end. Ask
>>    the private stuff in the end.
>> 3. #2 Designerdeveloper, Developerdesigner, Designstudent...? I suggest
>>    to use checkboxes, not radios, here. Or provide a ton more options.
>>    Or not ask for profession/job title, ask for experience
>>    (checkboxes). Like that.
>> 4. I don't get the "(#!%*@!!!)" at #5 - sorry.
>> 5. #5: include "not sure" and/or "don't know" as options  6. #6 needs 
>> more explanantion (like examples/links, imagine noobs
>>    facing this question) and/or a "not sure" option  7. #11: Huh??? 
>> If you want to do conditional question blocks maybe
>>    phrase a bit different and/or ask this as one of the first questions?
>> 8. #12: hehe, date field, huh? ;)=
>> 9. #12ff: doublecheck "Doc Sprint" spelling 10. #14/15: consider 
>> people answering the question AT the Doc Sprint 11. #33 link to 
>> examples (and do that with similar stuff as well) 12. #34 wow, that's 
>> hard to answer for people NOT following all our
>>    conversations... ;)=
>> 13. #33, #34, #35, + add a "don't know" option == "Hey Scott I didn't
>>    get the question but WANT to answer and help you to improve this survey!
>> In general, with close to 40 questions, consider to let the user 
>> decide if he/she wants to take the short or long route as a first or 
>> second question, and build a conditional route to the longer version 
>> after approx. 2 minutes into the survey. It's much harder to build 
>> that path, but quite doable on this topic - and it will deliver better 
>> results as if people begin to rush through non-mandatory fields to get to an end...
>> HTH *Jay
>> Von: Scott Rowe <scottrowe@google.com <mailto:scottrowe@google.com>>
>> Datum: KW 4 | Donnerstag, 24. Januar 2013 22:56
>> An: "public-webplatform@w3.org <mailto:public-webplatform@w3.org>"
>> <public-webplatform@w3.org <mailto:public-webplatform@w3.org>>
>> Betreff: Contributor survey
>> Neu gesendet von: "public-webplatform@w3.org 
>> <mailto:public-webplatform@w3.org>" <public-webplatform@w3.org 
>> <mailto:public-webplatform@w3.org>>
>> Neu gesendet am: KW 4 | Donnerstag, 24. Januar 2013 22:57
>>    Please review this WPD Contributor Survey <http://goo.gl/i0nFV> and
>>    append your comments and suggestions to this thread.
>>    Note: this is not yet a formal survey. If you do submit it, your
>>    responses won't count. We will ask you to formally take the survey
>>    as soon as it is finalized.
>>    The purpose of this survey is to start developing some metrics
>>    around the community composition (who are you people?), doc sprints,
>>    site usability, and community involvement.
>>    Many of the questions anticipate (ahem) improvements, and the survey
>>    will establish a baseline for future surveys. So don't be surprised
>>    if we ask questions that cover obviously broken functionality.
>>    The survey will be available via a link on WPD (haven't decided
>>    where yet), and I'm planning on testing the survey at the Berlin doc
>>    sprint.
>>    Thanks!
>>    +Scott
Received on Friday, 25 January 2013 09:27:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:46 UTC