It’s time once again for the ritual that I know we’ve all come to love: the quarterly update on Community team projects. This quarter’s projects are constrained by a lack of available technical/engineering resources on our Public Platform team, so you’ll see that we are focusing on projects that don’t require assistance from them.
Here's a brief recap of what we accomplished in Q2, along with details on our Q3 plans.
Here's where the Community platform is going this quarter. Spoiler: We’re taking on a lot of big projects.
We've got big things planned. And small things. So much stuff. Check it out!
As the number of users grows and we improve our site engine, the social aspect of the network becomes more complicated. With all this social complexity, the CM team must daily answer one simple question: Is the community healthy?
While working on the review queues project, the Public Platform team saw an opportunity to improve the help center and create a space for more canonical articles about reviewing. By adding new, specific review queue help pages, the help center could become a more accessible and useful resource to all of our users.
We review our ticket smash event, lay out our roadmap for Q4, and talk about what we've been learning from our moderators.
In response to COVID-19 and its impact on SYEP, over 50 nonprofits and technology companies came together to design the Summer Bridge 2020 plan to continue the program. As one of Summer Bridge’s partners, Stack Overflow designed a workplace challenge to give students a taste of what it’s like to work in the tech industry and to give us a chance to learn more about how students engaged with our developer community.
Here at Stack Overflow, we recently held our first Community-a-thon event. We wanted our employees to learn more about the SE network and how it feels to use it so they can get a better sense of what it's like to be a user here.
This quarter, we tried something new for the Community Team roadmap and worked through every idea the community team had in an initial planning session. Here's what made the cut for Q3.
If you have been active on the Stack Exchange network (especially the Meta sites) or have been a reader of this blog for any significant amount of time, you will see the term Community used quite often. But who is a member of the Community? Why is the Community important? The answer to this will probably depend on who you ask.
We received a bunch of requests to share how we use our feedback framework on specific features. We got excited about this, and given that we just released Dark Mode (and “Ultra Dark Mode”), we thought this was a great opportunity to show how we arrived at our solution.
After speaking with subject matter experts, we decided to take a step back. In this post, we list and organize our methods of feedback into a matrix. The goal is to offer a clear framework to follow and to identify areas that could use bolstering with alternative methods.
In this post, we'd like to talk about some of the initiatives that are happening internally at Stack Overflow aimed at addressing and repairing our relationship with our community.
We’re excited to share research highlights about the work we’ve been doing to understand how satisfied people are with Stack Overflow. We’ve been working hard to explore what users like best about Stack Overflow and what their top pain points are, with the goal of improving the overall experience of using the site. To this end, we’ve launched a site satisfaction survey, in which we continually survey users about their experiences using Stack Overflow.
If you work on a product that’s ever benefited from research – whether that’s talking directly to users, analyzing experiment data, or any number of other research methods – you know how indispensable these inputs are for making the right decisions. But how do you decide which methods to use and when? How do you know if you’re spending the right amount of time on research? How do you know when it’s time to change your research methods?