@t=1:17:49:
- status-completed How would you describe the relationship between SO Inc. and the most deeply engaged users of the public platform over the past couple years (such as those who consistently try to engage with the company on meta)?
- Is it what you want it to be?
- What do you want it to be, and what do you think it will take concretely to get that relationship there?
- status-declined What have you heard from those users of their answer(s) to those questions?
- Does your answer differ? Why do you think that is?
Answer by Philippe (@t=1:18:13):
I would describe it as- it's got some rough spots for sure, but we've got a lot of really positive collaboration as well. I've been a part of a number of sessions where we've been openly and very frankly discussed lessons that we've learned so that we can do knowledge transfer to avoid repeating mistakes from the past where we can.
We've also got a number of initiatives either running or being planned that examine things like where we communicate, how we set our expectations, and how we convey things like the deprecation of a feature, or tests that are intended to provide valuable data that we need, but which may not be really popular with some parts of the userbase. And so, it's worth pointing out that in some of those things, we're making changes that frankly are pointed to the new contributors that are joining us. We're doing some necessary revisits of processes and tools and the ways of communication that we have because we believe that with strong growth, we have an opportunity to improve on those things. So some things that might not be built for a power user can seem like a waste of time, or can impact community trust, but that's because the feature isn't meant for you. It's meant for somebody else. Over time, of course, we want those newer users to become the power users. So some of the changes that we've been implementing and that will be implemented are disruptive change. So by their very nature, some folk aren't going to like them. Honestly, if we don't make some sort of disruptive change, though, we could continue to see the number of questions drop.
So, yeah. We test out some things that aren't real popular. Some of them we keep, some of them we don't; we change some things that some folks maybe wish we hadn't, and all of these can lead to tension, and trust me when I say that I do not relish that tension. Nobody on either side of it enjoys it, but I do believe that as we get better at understanding the why behind why we do things, community members will come to believe in our good intent, and that we can gradually regain some trust from those who lost it, and we can get better at delivering features that will meet needs, even when the need isn't totally appreciated yet. And I believe that that will grow confidence in the company as a good steward for the network. But it is trust that is won inch by inch and foot by foot.
And Prashanth added (@t=1:20:21):
Sometimes I describe what we're doing is a little bit like we're governing [inaudible] of about a hundred million people. It is quite complex in that ultimately we need to listen to do that successfully- we need to listen to people, but we need to listen to people from various perspectives- not just a certain group of people, especially the diversity we have on the website: the power users, and then the newer users, etc., ultimately, in the spirit of serving the whole. That's the complexity of what we are doing- serving a very large community. That's easier said than done.
I think Philippe's response doesn't do justice to the fact that changes or features can be made with design for UX that help new users and don't frustrate power users for whom the change or feature is not intended. The recent comment experiment is a good example (and from Philippe's words, it sounds like his response is written with that context in mind, along with other recent changes like testing the stacks editor). The comment change had a purpose and an audience. In intent, it may have been a "[change] pointed to the new contributors that are joining us", but in implementation, it was deployed to everyone, and made UX worse for many people whom it didn't need to in a way that was heuristically avoidable. (It didn't even just affect general commenting either. It temporarily broke commenting in review queues, several of which are there to... serve new users (maybe there's a moral in that mini-story)).
Hurting your power users' UX to attract new users isn't necessarily necessary. And if you want those newer users to become power users like you've claimed in your answer to the question, then that would be a sadistic and vicious cycle conveyer belt human wildfire to orchestrate: make a change to attract some large number of new people, and burn some large number of those you previously attracted; repeat, but with a bigger appetite. Obviously from the your words, it doesn't sound like you want to create that kind of growth. But as I think the comment experiment is demonstrating, intention and implementation are two different things, and even if you can get us to "believe in [your] good intent", that doesn't mean you will have gotten us "librarians" to stop expecting it to mean bad outcomes for us / the library even if those bad outcomes are avoidable with some thought and effort and you would want to avoid them.
I'd also like to say that (me being a "power-user") some of the ideas I have about improving the network that I'm most interested to see considered are designed specifically to improve the user experience for non-power-users. And to my memory, whenever I express those ideas, the company doesn't seem to see it or take it into consideration. I don't feel like Prashanth's response does justice to the fact that there are power users who are keenly interested in improving the experiences of new/non-power-users, and doing so in a way that considers the complexities of serving a diverse set of parties. To me, it reads like a lecture on something I already believe.
but I do believe that as we get better at understanding the why behind why we do things
Who is "we" here? The company? Why would you need to get better at understanding why you are doing something? Are you referring to the company and the userbase? I'd find that phrasing patronizing and mildly heavy handed.
Details of this particular discussion aside, I appreciate that you held this event and prepared answers to our questions- including tough ones. Thank you :)