The Japanese train system is famously fast, clean, friendly, and efficient. On the drive home from my first day back at Google I was reminded of why as I listened to the 99% Invisible podcast episode “Wait wait ... tell me!”. I’ll give you the tl;dr summary of the story and explain some connections I made to product development for online communities that got me so in my head I missed my exit for the 405.
One of the secrets to Japan’s impressive system of bullet trains, called Shinkansen, is simple. It’s the kind of elegant solution I dream of and representative of the values I hold as a product and community person. In order to improve rider satisfaction with wait times while trains were cleaned, the new CEO of Shinkansen didn't sacrifice quality. Instead he introduced transparency between workers who cleaned trains and waiting customers. He did this by literally making workers more visible (e.g., bright red uniforms) instead of intentionally invisible (pale blue uniforms that blend in with their environs). Beyond physical appearances alone, he also encouraged workers to actually speak with passengers.
Making their work more visible in these ways had profound effects on behaviors in the system between workers and waiting passengers. Namely, passengers:
Were less frustrated by wait times because they could better see and understand the purpose of waiting
Empathized with workers to the point of being more conscientious by proactively cleaning up their own messes
With this transparency, passengers were empowered with insight into the common interests between themselves and workers. They not only tolerated the extra wait as workers cleaned trains, they embraced it. And no one had to tell them “because it’s good for you.” Additionally, Shinkansen was able to maintain high standards of cleanliness.
In a conversation with a friend about the Shinkansen train system story, he brought up IKEA’s cafeterias. The ones with the amazing Swedish meatballs and lingonberry sauce. Where you bus your own table. Not only is a DIY approach appropriate here (it’s IKEA!), they make it consistently transparent throughout the diner’s “user journey” so there’s no room for unmet expectations for Michelin-grade experiences. And it goes beyond signs everywhere. The carts where you stash your emptied trays are an unmissable centerpiece of the cafe. In most places they are hidden out of sight.
In my blog post reflecting on my time leading product for Stack Overflow’s public Q&A, I alluded to tensions among different types of users. Curators and moderators and question-askers and question-answerers. One of the things that I think is well appreciated by moderators and curators (and probably many question-answerers, too) is the importance of the quality of content that gets created and maintained over time. Interestingly, question-askers (mostly new users) are the driving force behind content creation on Stack Overflow, yet often their local and immediate needs may not make the quality of the entire repository present in mind. The tension, in part, in my opinion is a lack of transparency between integral parts of the system (people!) that could be communicating.
If the flow a question enters when it's closed was more transparent, would that help people understand why it happens? If people saw how content reviews help keep up a healthy ecosystem of question and answer pairs, would they more eagerly contribute to review themselves? What if the average user knew that without a small number of volunteer moderators handling flagged content toxicity would be double what it is?
I’ve long thought that much of Kaggle’s relative welcomingness as an online technical community stems from its inherent temporal transparency between power users and newcomers. This started with Competitions. Each Competition which runs for a couple of months is a new shared objective for new and old users alike to collaborate and share ideas. Each competition generates a cohort that’s basically a community of practice with a deadline. Once it’s over, users often write-up their approaches (example), sharing what they learned with the community. And then they start all over again with the next competition. Over time, each user is on a cycling trajectory from novice to expert and there’s always some new technique or framework to learn as the state of the art in machine learning evolves. I really believe it's visibility and participation in constantly cycling cohorts with shared goals that make it easier for users of all levels to better empathize.
In an online community, you need to find ways to foster and incentivize ways to encourage different types of users to interact positively and contribute to your mission. I believe that transparency, especially by making shared goals and opportunities to empathize apparent in the product itself, can be an important way to achieve this.
Thank you once again to Josh Heyer (AKA Shog9) for his feedback on this post (and for talking to me about delicious lingonberry sauce). Thanks also to my fellow Kaggle Noobs moderators (Aakash, Yifan, Mikel, Jorge) for their discussion on this topic.
Follow the conversation and discuss on Twitter.
Meg Risdal 👾@meganrisdalI wrote up some thoughts on transparency in online communities. 👀🤗 mrisdal.github.io/blog/posts/tra…03:54 AM - 23 Jan 2020