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

WordPress User/Developer Survey: clarifying goals

Thanks to everyone who made suggestions on the previous post about updating the WordPress User & Developer Survey! Commenters shared lots of ideas as well as some wise words about survey design and data collection. There are plenty of questions we could ask, and it became clear to me immediately that the best way to move forward would be to clarify the goals of the survey. Once we’re settled on what we’d like to learn, we can use those goals to direct and inform the questions we ask.

Clarifying goals

The goal of this survey is to learn more about who uses WordPress, and how they use it — data that we can’t gather anywhere else — so we can build better software. Here is an outline detailing sections of questions, with some thoughts on what contributor teams would find each section useful:

  1. Who are the people currently using WordPress? (all teams)
  2. How do people find WordPress, and why do they decide to use it? (marketing, community, design, accessibility)
  3. What do people want to accomplish when they use WordPress? (core, design, accessibility, training)
  4. What do people find difficult when using WordPress? (support, docs, training, community, core, design, accessibility)
  5. What tools would make people happier when using WordPress? (themes, plugins, core, design/a11y, support)
  6. How do people extend or customize WordPress? (plugins, themes, design/a11y)

Once people answer questions in the above categories, we can offer an additional set of questions designed for WordPress contributors, past and present. Presumably a contributor will be willing to give a little extra time to the survey, since they have a closer relationship with WordPress than non-contributors. We could probably use the list of questions asked in the 2015 Contributor Experience Survey as a starting point; it seems like a pretty comprehensive start.

Early request for help in promoting the survey

Mentioning this now so that marketers can plan ahead: this year I’d like to promote the survey more widely than we have in the past.

We’ve always promoted the survey through a banner on WordPress.org, plus an article on WordPress News and through word of mouth. This has been successful in the past, but less so in recent years. In 2015*, 45,997 people filled out the survey, but in 2016 and 2017, less than 10,000 responses came in. We won’t have time to add a notice to everyone’s dashboard (even if everyone agreed that would be wise), so this year I’d like to ask everyone to help promote the survey through as many channels as they have available to them.

Here are some ways you can help:

  1. Promote the survey in your or your company’s newsletter.
  2. Write a blog post about the survey.
  3. Mention it on social media.
  4. Encourage people at your local WordPress meetup to take the survey. (Heck, organize a take-the-survey event, and then discuss the questions afterwards! Easy meetup idea!) 
  5. Mention the survey to the audience of your podcast.
  6. Remind people who attend the meetings of your contributor team to take the survey.

Next Steps

Based on feedback on the broad goals of the survey, I’ll work up a survey draft, incorporating questions we asked in past surveys as well as new questions, which I’ll then publish on this site for additional feedback.

Request for feedback

  1. Do the sections above seem reasonable (if the goal is to get an idea of who uses WordPress and how they use it)?
    1. If so, is there any particular item on this list that would help your contributor team make more strategic decisions in 2020? 
    2. If not, what would be the most useful thing for your team to know about who and how people are using WordPress?
  2. Do you have any other suggestions for ways people can promote this survey?

* There were 27,662,162 active WordPress installations as of Dec 24, 2015.


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