WordPress User/Pro Survey: 11 questions and a script

I recently had the humbling realization that calling this survey the “User and Developer Survey”… ignores a host of other roles in the WordPress ecosystem, as if we don’t care to gather data from designers, content creators, support professionals, translators, and project managers (to name a few). Because that’s not true, I’m going to start calling this the “WordPress User/Pro Survey” when discussing with contributors. For the general public, I think we should just call it the “WordPress Survey.”

The WordPress User/Pro Survey needs your help! In this post, you will find 11 questions excerpted from the survey that need feedback, plus a link to the entire survey script. The full survey script is very long, and many questions from previous surveys are included, so this post includes only the 11 questions that I think are more likely to be affected by blind spots.

As you read through these questions, please note any thoughts you have about answer options that should be added or removed. If you don’t know how you would answer a particular question, I’d love to hear about it in a comment on this post. I’ll also request feedback on an optional question about gender, which I will elaborate on below. 

Questions that have stars (*) next to them are required questions (in the survey, not for this post!). Click “Show full post” to see the questions and the specific feedback requests.

Continue reading

#survey, #user-developer-survey

Updates to the WordPress User & Developer Survey

For many years, information on how people use WordPress has been gathered through an annual survey published on WordPress.org. In the early years of WordPress, interesting results were shared at the State of the Word. In 2017, I shared results from 2015-2017 surveys in a post on the News blog. There was no survey in 2018.

In preparation for the 2019 survey, I’d like to collect topic suggestions from WordPress contributor teams. Ideally, the questions can be updated to gather information that will help inform contributor work in the coming year.

A few important notes:

  1. This survey is mostly publicized through WordPress.org, which affects the base of respondents.
  2. A full export of the raw data will not be published, to avoid sharing information that might reveal something that respondents consider private. (I’d love to make this information as accessible as possible, though, so if you have a suggestion for an OS project or tool that would allow people to access with the data, but that still protects individual response privacy, please leave a comment on this post!)
  3. Long surveys generally gather fewer responses. It might not be possible to include questions on every suggested topic.

Suggest a topic!

WordPress contributor teams, what information would help you prioritize or direct your work in 2020? Suggest some survey topics in a comment on this post!

#survey, #user-developer-survey

Contributor Experience Survey

Attention team reps: Please pass this survey along to your teams via your team blogs and ask folks to take it and also to spread the word. Use whatever wording you like. 🙂

Take the contributor experience survey — it’s short, and none of the questions are mandatory. Please post, tweet, tell your co-contributors/community members via any/all communication methods. Thanks! Here’s the link: http://wordpressdotorg.polldaddy.com/s/wordpress-contributor-experience-poll

Anyone else reading this, you don’t need to post to the team blog, but if you could take the survey and help spread the word, that would be greatly appreciated.

Many thanks from the community outreach team. 🙂

#contributors, #feedback, #survey