Community Insights/Frequent questions/zh
關於「社參」調查 edit
社群参与调查是维基媒体基金会（WMF）的新项目，旨在帮助WMF中的各个小组收集他们所服务的社群的数据。根据维基媒体基金会关于共享权力的指导原则所言，“维基媒体基金会与全球志愿者社群合作，这里的‘志愿者’包括文章作者、编辑、摄影师、管理员、巡查员、质量评估员、翻译者、默默无闻的贡献者、询问处的答疑者、开发者、机器人作者、外联工作者以及很多其他人”。“社参”调查是通过每年评估我们与全球社群的协作的情况，来达到我们和社群开展更好合作的目的，这同时也能反映出WMF的工作产生了怎样的影响。
目标 edit
“社参”调查由四个目的：
- 目的 1：改善我们与维基媒体全球社群的一致性 - 通过需求评估和项目评估，将这些问卷调查讲作为改善 WMF 与社群一致性的手段。
- 目的 2：收集问卷调查数据，用于年度规划 - 每年从社群中收集最有用的数据，尤其是使用了 WMF 产品及 WMF 职员支持的人群。
- 目的 3：通过协作，减小各个团队的经费开销 - 通过向 WMF 的各个团队提供集中支持及合作，减少团队的开销。
- 目的 4：避免重复调查 - 协调团队之间的数据收集工作，以减少各种项目中问卷调查导致的辛苦工作。
总而言之，这个项目意在收集社群的反馈和意见，这些信息可直接影响维基媒体基金会的工作。
关于此调查 edit
Annual WMF Performance Survey edit
The annual survey is the larger of the three surveys. This survey will heavily focus on information that can support teams in annual planning; often tied with KPIs. The performance survey will focus on 5 core audiences only, or audiences within these 5 major audiences. Most importantly, the survey employs a collaborative process - if a team at the WMF proposes questions, that team would also need to support the survey process in some way.
Pulse Surveys edit
Pulse surveys were an idea to have shorter surveys available throughout the year. We do not yet have the capacity to do more than one survey at this time.
Evaluation edit
Evaluation of CE Insights will be done through two means. First, we will use the CE Insight surveys as well as annual WMF staff surveys to evaluate the project. In addition to these methods, we will conduct a process evaluation to determine how useful the process was for staff and for community members involved. The process evaluation and surveys will results in annual recommendations for improvement which will be published in June or July of each year, during the design of the following year's process.
Goals will be measured by the following two surveys
- Annual CE Insights staff survey: Goal 1, 2, 3
- WMF performance survey: Goal 1, 4
For more information, see the Evaluation section.
Frequently Asked Questions edit
Community members don't like taking really long surveys. Are these going to be very long surveys? edit
There are three main ways we will keep these surveys short:
- We will focus on the most important questions that we need to make decisions as an organization.
- The surveys will get split up by audience so we will keep the surveys specific to the audience of interest. We will do this by using specific avenues for reaching users.
- We will use many screening questions to users will answer questions that are most relevant to them. As an example, if someone did not engage in the WMF strategy process, they will not get asked any questions about the strategy process.
How will we make sure users respond to questions that are most relevant to them? edit
There are two ways we will do this. First, there will be separate surveys for each audience, and we will reach these audiences in a specific way. For example, to reach developer/tech collaborators, we can survey them on labs, mediawiki wiki, phabricator and other technical spaces.
A second method will be to heavily use "screening questions" so they don't answer questions about everything. We will only ask users to review/give feedback on activities they have participated in. For example, they will choose whether they have engaged with software processes, developing tools, participating in WMF-hosted hackathons, etc. They will likely have to choose 3 areas that are most important to them and then they will get a set of questions related to those areas.
If our team would like to do more research about a result from a survey, would the Learning & Evaluation team be able to help? edit
The Learning & Evaluation team would be happy to help you design and plan any follow-up studies you would like to do based on the results of CE Insights. Research projects are a great learning opportunity for your team to engage in learning how to conduct interviews, focus groups, surveys, or other studies. L&E would maintain an advisory role. We have other teams would would likely be able to help as well, such as the Research or the Design Research teams.