<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Strasz on Medium]]></title>
        <description><![CDATA[Stories by Strasz on Medium]]></description>
        <link>https://medium.com/@straszvr?source=rss-a07555883243------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3_CqS0yrUcI4e7u1TMx_5A.png</url>
            <title>Stories by Strasz on Medium</title>
            <link>https://medium.com/@straszvr?source=rss-a07555883243------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:01:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@straszvr/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Making sense of the screaming: or, what makes feedback good (or bad)]]></title>
            <link>https://medium.com/@straszvr/making-sense-of-the-screaming-or-what-makes-feedback-good-or-bad-87c868f26b23?source=rss-a07555883243------2</link>
            <guid isPermaLink="false">https://medium.com/p/87c868f26b23</guid>
            <category><![CDATA[community-management]]></category>
            <dc:creator><![CDATA[Strasz]]></dc:creator>
            <pubDate>Mon, 03 Mar 2025 20:45:52 GMT</pubDate>
            <atom:updated>2025-03-03T20:51:44.101Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7kOTwT1N9jwEyWqgsJe2rg.png" /><figcaption>A stack of speakers and amps at a Sunn O))) concert. On a post about feedback. Get it??? Haha, I’m so funny and clever. You see they are a drone metal band and,</figcaption></figure><h3>Making Sense of the Screaming: Or, What Makes Feedback Good (or Bad)</h3><p>There are about as many witty sayings about opinions as there are people with them. Understandably so, to the disappointment of most Buddhists, when we experience things, we tend to have opinions on those experiences. And when we have an experience that passes a certain threshold, we want to share it with others.</p><p>Those experiences — those judgments — are often emotional. They’re often microcosmic chunks of not just that singular experience, but every preceding experience. They contain the thing you are judging, the thing you are experiencing, and every other thing that built your experience up to that point. They’re heavy. They’re important. They’re part of you.</p><p>Every single opinion shared online, no matter how concise, is a novel.</p><p>…and yet, are they useful?</p><p><strong>The Reality of Feedback</strong></p><p>As a Community Manager, you’re going to spend most of your waking life swimming through a deluge of feedback — positive or negative. I don’t know many of us who work for companies whose products are received with complete apathy.</p><p>That feedback is going to take different forms.</p><p>Some feedback is going to be direct — it is going to be where you expect it, and in a format that makes it (mostly) digestible and (mostly) understandable. In this corner, we’re talking things like VRChat’s Canny, or in threads where there’s been an explicit call to action asking for opinions.</p><p>Some feedback is, uh, not that.</p><p>I’ve been trying to be diplomatic about this, but one thing I want to do with this blog is be honest, so uhh, yeah. It’s going to be everywhere, man. It’s going to be <em>everywhere</em>. You’re going to open up social media and you’re going to see it. You’re going to hear it from friends. You’re going to get it in your email. LinkedIn? I’ve seen it. Reddit? Of course. Discord messages at 4 AM irritated that you aren’t responding to their concern right then and there? Yeah.</p><p>As a Community Manager — or anyone in development, really — it’s easy to shrug and toss one group of feedback into the “good” bin and another into the “bad” bin. The person writing a long, detailed message with precise suggestions on how to fix their problem via the official feedback forum with 1,000 upvotes is clearly writing the most useful feedback, right? And the person telling you to <em>fix your fucking game</em> at ass o’clock in the morning is just worthless… right?</p><p>Right?</p><p>…right?</p><p><em>oh god</em></p><h3><strong>What Makes Feedback Bad</strong></h3><p>First: “bad” here is really incorrect. A better descriptor would probably be, “inactionable,” or “not representative.”</p><p>“Inactionable” feedback is all the stuff that is basically just seething anger without any substance. There’s not much you can do with that most of the time! Likewise, “not representative” is also accurate for a lot of feedback you’ll see in/on places like Reddit, or Twitter, or YouTube, or Discord. While not always, this is usually feedback that represents the opinions of the loudest (and often angriest or most passionate) users… but not the majority.</p><p>Still — this feedback has <em>some</em> merit, hence why I’d lean away from “bad.” It’s still a sign, even if it’s not the greatest one.</p><p>But not all feedback is even that — some is genuinely, truly awful. You shouldn’t burden yourself with it.</p><p>This includes:</p><h4><strong>The Contrarian Poster</strong></h4><p>Given enough time, your project will eventually attract a crowd of folks that will want to build a brand on disagreeing with whatever it is you are doing. These folks will be in every thread, happy to write a dissertation on why your latest choice is the wrong one.</p><p>Sometimes folks like this are powered by a grudge (maybe you nerfed their favorite class five years ago, maybe you banned their friend for screaming a slur, maybe they had a friend who was let go and are channeling their anger), but most of the time they simply are just lost in the sauce.</p><p>These folks often will hold strange opinions not just contrary to you (and any data that you have), but to other community members as well.</p><p>You’ll know who they are.</p><h4><strong>Buzzwords (aka: red flags)</strong></h4><p>Very frequently, there will be some sort of topic du jour that will pop up basically everywhere, despite having nothing to do with your product.</p><p>See: posters leaving a ton of feedback about your product that amounts to “too much diversity,” or “DEI,” or whatever. This stuff is almost entirely worthless because it isn’t really feedback on your product at all, but more just them parroting their worldview because it’s the internet and thats’ what people on the internet do.</p><h4><strong>Abusive feedback</strong></h4><p>People simply being mean isn’t useful — it’s an indicator that they are upset, but it’s not on you to figure out why. Any value in their thought will be delivered by someone with way more tact. To be clear, this doesn’t mean “ignore angry people” — but if someone can’t deliver a coherent thought without making it personal, let data sort it out.</p><p>To put it another way: you’re not your community’s therapist. It’s not your job to dig down into someone’s anger to figure out why they had a bad day. These sorts of engagements are a drain on energy, morale, and your time. Seriously. If someone is simply spouting off anger at you, just walk away. You aren’t going to miss anything by not engaging. I promise.</p><h4><strong>The Echo</strong></h4><p>Something you see across gaming is the ability for a content creator to toss their particular pet peeves at their community, only to hear some of those same thoughts echoed back at them. This echo isn’t because their community shares their beliefs — but rather because their community sees them as a “leader.”</p><p>The thing is, a lot of influencer types hear this echo and then believe it is an acknowledgement that a problem exists, and it then becomes a sort of bugbear rallying cry. They repeat it, and then it gets repeated back at them, over and over.</p><p>What might be a tiny problem, or one that is incredibly niche ends up becoming something, suddenly, that <em>can appear</em> to be much larger.</p><p>If you’re a community manager for a game or product with a competitive scene, you’ll see this sort of thing a lot: emphasized by the most mechanically skilled players talking about subtle balance changes that only appear in the top 1% meta being game breaking… and then hearing folks who are nowhere near that level repeating those arguments as if they’re something they experience daily.</p><p>These folks often (given their reach) find their way in front of executives who aren’t as familiar with the “real” numbers, and are typically receptive to passion. While this feedback can be useful, it’s important to put it in context. These folks will also drive your data team insane, so probably befriend them early and realize that you’re actually best friends.</p><p>In general, you should see a pattern here: in the above examples, the feedback isn’t really <em>about</em> your product or your team, it’s really just about <em>someone else</em>. That is, ultimately, why this feedback isn’t worth your time — because it literally has nothing to do with your work.</p><p>Once again: you are not being paid to be someone’s therapist. You are not there to help someone work out how to emotionally regulate, and you are not being paid to be yelled at because someone had a bad day, or because someone needs a bad guy for their community of sycophants.</p><p>But to some extent, you kinda knew that, right? When you imagine “bad” feedback, everything I’ve talked about is probably what you’ve imagined. But what about the folks that are just… <em>passionate?</em></p><h3><strong>On Passion: Or, Pick Up a Shell, Hear the Ocean</strong></h3><p>Whenever I talk to someone casually about my job, they’ll usually ask how I deal with being screamed at 24/7. This is especially true if we’re on the end of a particular rough cycle or update that has made some folks angry.</p><p>The answer I always give has been a touchstone for me since I started: people being angry is (ultimately) good — it means they care. It means they’re passionate. It means the thing you are working on is something that they really, really care about.</p><p>While people get angry about things that don’t matter to them all the time (or things that they’re forced to use, rather than passionately use), I believe you can fundamentally tell the difference. There’s a certain sort of, “this really matters to me,” pathos that bleeds through.</p><p>This passion is generally a good sign — but it doesn’t by default mean that “passionate” feedback is automatically good.</p><p>A lot of your most passionate users — the folks that care the most about the platform — are actually, conversely, sometimes the worst people to listen to. These folks are paying attention to everything that you’re doing. They’re commenting on every balance change, every minor tweak to netcode, every UI change, basically they have an opinion on everything — and often, these opinions have a tendency to either be overly fawning or overly critical.</p><p>These folks are people I like to think of as “frequent flyers” and I can bet that every community manager out there immediately understands what I mean by that. These are your reply guys, your top forum posters, and so on. They’re folks that mean well and really do care, but often are in the “1%” of your particular community (or communities).</p><p>In this way, these folks can also have blinders on: they’re your “hardcore” users, and they use your application or game in a very, very specific way.</p><p>The feedback that they deliver isn’t necessarily bad, per-se, but it’s important that you take it with a grain of salt.</p><p>It is also worth noting that these users often are a good thermometer for a certain kind of engaged user, and their feedback is often contrary to what the data says.</p><p>To that end, it’s important to make sure that their feedback is heard, but it’s also important to temper it to the rest of your team. In my experience, while I think the industry stereotype (at least outside of it) is that product folks typically only listen to data, I’ve found that intense feedback from power users can actually shift the direction as well — and that’s not always a good thing.</p><p>I think there’s a tendency, with this sort of feedback, of it being like picking up a shell and hearing the ocean. You might think you’re hearing the voice of an entire community, but realistically it’s a very small fraction of it. In short, you’re mentally buying into an illusion.</p><p>I’ve seen features get scrapped because of this sort of feedback — only for the data to show that this was the wrong choice later. (Or, sometimes, the users providing the feedback themselves change course once they’re actually listened to!)</p><p>This appears to be a somewhat common problem — I’ve had personal conversations with game and app developers that have backtracked on some pretty big decisions because of their most passionate users getting very vocal about choices they made, entirely because of (well meaning) community managers bringing that feedback up internally and turning what should be a singular data point into a red alert situation.</p><h3><strong>Listening Too Hard</strong></h3><p>If you spend any time on the internet at all (and especially if you spend time on social media) you’ll almost certainly experience the general opinion that developers don’t listen to feedback. This is entirely untrue, and I’d argue that the reverse is actually true: that developers (and especially game developers) have a tendency to listen to users too much.</p><p>There are a few reasons for this, but I believe it fundamentally boils down to two things:</p><ul><li>Community managers want to be seen as good at their jobs.</li><li>Community managers tend to be certain kinds of people.</li></ul><p>Let’s break those down.</p><p><strong>We want to be good at our jobs.</strong></p><p>Both internally and externally, we can perceive our “quality” comes down to how often the community we are representing says nice things about us.</p><p>We’ve all played a game (or used a program) with a community manager that was loved by everyone. They were always bringing us great news, they always seemed to listen and hear everyone out, and everyone would always talk about how lucky the community was to have them.</p><p>We want to be that person!</p><p>And so, when things go wrong, we want to be the person out there making the community happy to have us. We want to be the person that takes feedback, goes into a meeting, and really makes a player or user feel heard — not in the cushy feel good way, but in a meaningful way.</p><p><em>We want to make a difference.</em></p><p>I can’t tell you the amount of times I’ve been stressed out (or that I’ve seen someone else stressed out) because of some negative feedback we received that we know we won’t be able to respond to in just the way that particular person needs. Likewise, when people get mean, I see so many community managers go into fawn mode. Oh, you called me bad words? Let me use all my active listening skills to try to make you feel better!!!! Let me personally reach out to you so you can feel taken care of!!!</p><p>This bleeds right into that second category: the folks drawn to this job tend to be builders. We tend to be the folks trying to unite community. We tend to be squishy, we tend to have big hearts, and we tend to want to see the best in everyone — even if those people don’t deserve it.</p><p>I’ve never had to tell a community manager to listen better. I’ve never had to tell someone that they were being stubborn, or that they were being too defensive, or that they had been ignoring feedback because it wasn’t worded in the “right” way.</p><p>I have, however, had to put my hand on someone’s (proverbial) shoulder and let them know they could let go a little, that they didn’t do anything wrong by not giving someone personalized attention, and that — going back to the metaphor above — that they were picking up a shell and hearing the whole ocean.</p><h3><strong>What Makes Feedback Good</strong></h3><p>Up until this point, I think it would be fair to say I’ve been a little bit negative toward feedback.</p><p>So let’s reel it back a bit: feedback can be good, and in a way, it always is in the aggregate. Generally, one piece of feedback is an anecdote and a hundred is data, but once you’ve heard that singular piece of feedback, you need to be able to synthesize what the “real” problem is, else you might mistake a stray anecdote for a piece of that larger data pie.</p><p>So — the way I like to look at things — is that if you collect some feedback, you should go through a little bit of a process:</p><ol><li>Strip it down. What is it saying?</li><li>Have you heard it before — and when?</li><li>Can you put it in a bucket you already have?</li><li>…do you need a new bucket?</li></ol><p>The first part is the hardest: strip it down!</p><p>Figuring out what someone is actually saying can be difficult. As we’ve discussed above, feedback can be sandwiched between a lot of impassioned, emotional verbiage. It can sometimes be describing multiple things. It can sometimes be contradictory. But, in everything, there is <em>something</em> trying to be said — and it’s your job to figure it out.</p><p>A really important note here: this is a job for a human. There are a lot of “AI solutions” that will try to analyze stuff like this. They are bad.</p><p><em>(And I’ve certainly seen folks toss feedback in ChatGPT and essentially go, “what is being said here.”)</em></p><p>To be a little more technical here — AI tools are trained on a lot of garbage data, which means they aren’t specific to your community, your game, or the specific problem a user is having. It might pull out, “This user is upset about X,” but it won’t be able to get the <em>real</em> problem out.</p><p>There’s no singular way to do that, especially because it’s going to look a little different for everyone. Generally, though, you have to work within the context: who is giving the feedback? What communities are they in? What struggles are they describing? How experienced are they? What aren’t they saying?</p><p>This is why that second step is important: have you heard it before — and when?</p><p>Some feedback is straight-forward, and often with volume comes clarity. If you keep hearing a singular piece of feedback, then how you approach this might change. Is this another tally mark — in other words, is this approaching “data” — or is something different here?</p><p>This also changes with the complexity of the systems being referred to. If you release an analog light switch and folks are struggling to turn it on, you can be pretty sure about where the feedback should go, versus a digital, variable switch with a screen and touch controls.</p><p>There’s often this immediate urge to pair like with like and dismiss (or shuffle/categorize) feedback immediately — like, oh, this is absolutely a performance issue, let’s shove it in that drawer. That’s necessary when you’re slammed! But if you have the time, I do strongly suggest stepping back and asking yourself: what’s <em>really</em> going on here? Have I <em>really</em> heard this before?</p><p>Can I really put this in a bucket I already have?</p><p>That’s the next step — once you’ve broken it down, it’s time to dump it in a bucket.</p><p>Look — I know I’m long-winded, but I’m not going to belabor this part! If you have a good understanding of what is actually being said, you should be able to file it away, so to speak. If it doesn’t fit, you might’ve stumbled on a new issue.</p><p>At the end of this process, you should have a pretty solid idea of what your next steps should be. Sometimes a “bucket” is simply noting it and moving on. Sometimes it’s passing info to your data or insights or QA team to validate something a bit more. Sometimes it’s something you notate somewhere, but know you’ll never touch again.</p><p>And yes, sometimes, you’ll get to the bottom of the list and realize the feedback isn’t very helpful — and might even be harmful. I’m saying this because I believe some CM out there needs to hear it: sometimes not passing feedback on is helpful, too.</p><p>No, your engineers don’t need to hear that they’re lazy pieces of shit, or that your designers need to go back to school because a game dev crank decided to hyperfixate on them this morning. In short: understand that sometimes this can apply for your feedback, too:</p><p><a href="https://www.youtube.com/watch?v=11lPhMSulSU">https://www.youtube.com/watch?v=11lPhMSulSU</a></p><p><strong>Okay, But What Does GOOD Feedback Look Like?</strong></p><p>Good feedback identifies problems.</p><p>If you are someone leaving feedback anywhere, forever, memorize that statement:</p><p><strong>Good feedback identifies problems.</strong></p><p>That doesn’t mean that good feedback can’t suggest solutions, but they’re usually worthless.</p><p>That’s tough to hear! But it’s true: anyone on one side of a problem functionally has no idea of why that issue exists, what barriers to solving it exist, or what context that problem in general exists in. They simply know it is a problem — that’s something they can be sure of.</p><p>It’s a bit like leaving feedback for a restaurant and saying that your pizza arrived to your table cold, so the restaurant should really buy new ovens.</p><p>The problem could be the ovens… but it could’ve also been a lack of staff, or it could’ve been a busy day, or you could’ve simply been forgotten due to the floor plan of the restaurant blocking you off from the view of the servers… or a million other things.</p><p>The only thing you can be sure of is that your pizza arrived cold. Providing that feedback to the restaurant is useful. Telling them how to fix it? Useless!</p><p>Game development is the exact same!</p><p><em>(Sidebar: to belabor everything discussed so far at once, that above bit is a good metaphor why it’s important CMs boil feedback down. If you take, “our ovens are broken,” back to your team, there’s a nonzero chance someone is going to spend two weeks checking the oven’s temperature, because it’s a system they take a lot of pride in and they trust your feedback. Which is to say, passing feedback along gives it the authority of your voice. Caution!)</em></p><p>So, once again:</p><p><strong><em>Good feedback identifies problems.</em></strong></p><p>If you’re a user, or a player, or whatever, it’s okay for your feedback to be passionate. It’s okay to say that you were really upset because of how something broke, or how unbalanced something feels to you. Sometimes “a problem” is simply, “this thing isn’t working for me and it’s making me feel bad.” That is identifying a problem, after all!</p><p>Generally, though, you should be respectful, given that (once again) you have no idea why something broke — and the answer might be way more complicated than you think.</p><p><em>(I’d strongly suggest reading </em><a href="https://medium.com/@straszvr/first-welcome-to-the-blog-im-strasz-06565c17f385"><em>my first blog post</em></a><em> discussing how different communities can have wildly different opinions on something — a thing that you might loathe might be someone’s favorite thing. It’s also worth noting that this is also why passionate feedback — when it crosses a line — can be less useful. Passionate feedback that shows a complete disregard for other communities or use cases is likely going to be listened to less.)</em></p><p>This is a two-way street, though. Developers are often guilty of being opaque as to what the problems <em>really</em> are behind a particular issue.</p><p>So, you might have a legion of players telling you that your game is broken because X or Y or Z makes them feel bad, and you ignore it and then tell them they don’t actually have a problem. Or, you propose a solution, but it’s half-assed (to them) and only addresses a small portion of their complaints with no explanation.</p><p>Or, they might really want something added to the game, but you know that it’s out of scope, and that it’s something only a minority of the users want (and you’d really want to give it to them, but it’s going to take a hot second at the very least).</p><p>Generally, if you know you’re wading into an area where you can’t “solve” a problem for a large chunk of your users, or alternatively, you can only get halfway there, it can be helpful to have an open dialogue wherein you explain your choices and why.</p><p>Another aside here: using the restaurant metaphor above, this method helps deal with the sort of folks that will get <em>really angry</em> when you don’t listen to their complete restaurant redesign idea that involves stripping out all the seats, because that would totally increase staff/customer vision.</p><p>These folks will always see your solution (sans explanation) as a marker of incompetence, because they’re unable to see the factors preventing the problem from being totally annihilated (often using their totally perfect and cool idea).</p><p>By explaining some of the challenges behind the scenes, you might not get them to see your point of view completely, but you <em>will</em> get them to consider that they don’t have the full picture — and that you don’t actually hate them/their subset of the user base (and instead, are trying to solve a complex problem they don’t see the whole of). This will appease most of your community — and they’ll appreciate the transparency. But we’ll get more into responding to feedback in the next post, so I’ll bottle this up for now.</p><p>So let’s say it one more time and move on, just to drive things home through repetition:</p><p><em>Good feedback identifies problems.</em></p><h3><strong>Bringing it home…</strong></h3><p>At the very beginning of this blog post, I opened with the idea that every opinion fundamentally is a novel. Every experience with a game — or anything, really — is essentially a piece of qualia. That is to say, each experience is unique while at the same time being influenced by so, so many other things.</p><p>A person sitting down to play a game is never really sitting down by themselves. They’re sitting down alongside every other game they’ve played, every critic they’ve read, every personal experience they’ve had — and when they write an opinion, you’re getting all of those takes, too.</p><p>These things are all so personal. They’re sacred. To share our experience of something — that’s a big deal!</p><p>I think on some level, all of us within this field get that, and that’s why we take it so seriously. It’s why we try our best to always make sure everyone’s voice gets heard.</p><p>And, likewise, it’s also why we’re so appreciative when folks understand that good feedback identifies problems. Doing so is kinda like saying, look, I know I’ve got a lot of baggage, I know my experience might not match everyone else, and I know I don’t understand every system here, but this isn’t working for me.</p><p>That feedback helps us direct energy to where it’s needed. It helps us get our teams on the same page. Most of all, it shows empathy to us, to our coworkers, and honestly, to everyone else experiencing the same thing, too.</p><p>Anyway, in the next post, like I said above, we’re going to talk about responding to feedback — and making it work for you. It probably won’t be this long. Haha, just kidding.</p><p>Help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87c868f26b23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Does a Community Manager Actually Do?]]></title>
            <link>https://medium.com/@straszvr/first-welcome-to-the-blog-im-strasz-06565c17f385?source=rss-a07555883243------2</link>
            <guid isPermaLink="false">https://medium.com/p/06565c17f385</guid>
            <category><![CDATA[community-building]]></category>
            <category><![CDATA[vrchat]]></category>
            <category><![CDATA[community-management]]></category>
            <dc:creator><![CDATA[Strasz]]></dc:creator>
            <pubDate>Wed, 12 Feb 2025 03:28:36 GMT</pubDate>
            <atom:updated>2025-02-12T03:29:43.536Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PYjWngrKmY7o3l1eYtuFrA.png" /><figcaption>Pictured: the VRChat community — or at least a subset of it, featuring the virtual venue Concrete.</figcaption></figure><p>First: welcome to the blog! I’m Strasz!</p><p>This is the first post of many that deal with the art and science of community management. I’m starting this blog for two reasons: one, I’ve noticed that most folks writing about the industry tend to be outside of it, typically writing from a position of, well, agony.</p><p>Essentially, these are folks that were chased out, burned out, or otherwise left the industry. While their perspective is real, useful, and should be something anyone looking to work in this profession pays attention to, I’ve been a little surprised by how little writing about community management is done by people <em>in this shit</em>. So, yeah.</p><p>Two: I want to let people into what I do and what my philosophical process is who maybe aren’t “in” community management, or maybe want to understand how we think a bit better.</p><p>In short: if you’re a CM, I want to help you tackle your day-to-day problems. If you aren’t, I want you to understand how I think and what I think about.</p><p>With that said, I want to jump right into it, answering the question I receive most from folks outside the industry:</p><p><strong><em>“So… what do you actually do?”</em></strong></p><p>If you’re a community manager, you’ve probably heard that one a few thousand times — and it’s understandable!</p><p>We’re often very visible, our role isn’t immediately explainable by the title itself (ex: graphic designer, server engineer, writer, and so on), and if you ask any of us what we do, you’re liable to get a totally different answer.</p><p>And, like, I get it — defining what I do by itself is pretty difficult! When I was an adjunct professor, I could simply say that I taught and list out my courses. When I worked in marketing, I could tell you that I focused primarily on search engine optimization, but also had expertise in PR. When I worked in IT, I could tell you that I focused on small business and local government networking.</p><p>Simple!</p><p>But community management?</p><p>Well — let me start by giving you the answer I tell most folks, followed by an additional two levels of depth.</p><h3><strong>Level 1:</strong></h3><p>So, what do I do?</p><p>If you walk up to me in VRChat, or we’re at some sorta real-life function, and you ask me what I do, this is the answer I typically give.</p><p>I break my role up into three chunks: managing feedback, crafting messaging, and <em>other</em>.</p><p>Most people are pretty happy with that answer, but for those that want to know what those chunks actually are, this is what I tell them:</p><h3><strong>Level 2:</strong></h3><p>Managing feedback is relatively straightforward. Generally, any given company has a few sources of customer data that tell them if people like, don’t like, or are indifferent toward something they’ve done. Generally, an insights or data team will manage a lot of the “hard” signals — the analytics, the polling, the giant mess of numbers that is generated simply by people existing and using a product.</p><p>The “soft” signals, however, give that stuff context — often naked data isn’t super helpful. It’s too abstract! It’s our job, then, to bring back vibes — but not just vibes. We can also figure out <em>why</em> the data curved in a certain direction. If a feature is being used in an unexpected way, we can help figure out why. If a bit of design isn’t clicking, we can make sense of it.</p><p>It also sometimes feels like those of us that are embedded in the community are a bit of a barometer. While not foolproof, we can give pretty accurate estimates as to how something will be received, or what folks are particularly hurting for at any given time. Often, we can surface this quickly (and cheaply).</p><p>Crafting messaging — like the first — is one that people can probably guess is often a purview of ours, though this certainly isn’t the case for every community management team.</p><p>“Messaging” here refers to basically everything the public sees that isn’t “marketing” (but also, sometimes marketing).</p><p>An aside: it’s pretty common for folks in the general public to see any communication a company does as “marketing.” In a sense that any communication is theoretically part of a company’s brand, this is true, but in terms of the goals of each… not so much! Marketing often is a discipline that is focused on finding channels of growth for a business through promotion. (And as an aside to this aside, marketing is often strategic, it’s about finding the customer, whereas advertising typically is about targeting the customer.)</p><p>The difference is that the messaging that community managers tend to focus on is very (as you could guess) focused on the community. Essentially, our job is to inform the community of what is going on, why it is going on, and how it’s going to go on — at least, to the best that we are able.</p><p>Blog posts, videos, certain social media channels — these are our tools to reach the community at large.</p><p>Those two are pretty easy to understand! But the third one — other — well, what’s that about?</p><p>If you are a community manager, this is probably where you are cackling.</p><p>Community managers wear a lot of hats. At various times in my career, I’ve had to slot into the following roles:</p><ul><li>Influencer management</li><li>Streamer/talent</li><li>Event management</li><li>Crisis PR</li><li>Designer</li><li>Graphic designer</li><li>Video editor</li><li>Social media manager</li><li>Marketing manager/strategist</li><li>Event IT</li><li>Professional Punching Bag</li><li>…and probably, group therapist, if I’m being honest.</li></ul><p>There are many more! This is one of the reasons why there are so many ways “in” to this position. You’ll see people with this title that worked in STEM, that were teachers, marketers, laborers, and so on. It’s wild out here.</p><p>It’s the end of the year, as I write this — and I can confidently say that while those first two chunks I mentioned above were consistent, that last “other” one? Yeah — totally different every month. My job in January didn’t look like how it did in April, nor September, nor December. While some tasks stay the same, others shift.</p><p>But okay. You’re not here for the stuff you could’ve found digging around Google.</p><p><em>Where’s the good stuff, Strasz?</em></p><h3><strong>Level 3:</strong></h3><p>We’re ambassadors. We’re negotiators. We’re community shop stewards.</p><p>So first off, I’m going to suggest watching Liana Ruppert’s video on this same subject, which you can find below:</p><p><a href="https://youtu.be/4ZPZ9LvJiW8?si=ZS4oQ7W_X1564cVP">https://youtu.be/4ZPZ9LvJiW8</a></p><p>Around the 5 minute mark, Liana discusses the complexities of considering feedback from multiple different communities in Destiny 2. In general, she explains, people tend to think of Destiny as having two communities — the PvE folks and the PvP folks. But this isn’t true! There are numerous different microcosms within the larger community, which can be summed up not just by what content people tend to focus on, but how they focus on it, what their background is, and how “hardcore” they are (among many, many other factors).</p><p>To quote her:</p><blockquote>“You’ve got all these microcosms that need X amount of features and X amount of communication to be happy. But the problem is, what the PvP crowd needs is very different from [what the PvE crowd needs]. So, when you have two microcosms, it’s complicated as hell — and Destiny doesn’t even have just two microcosms… so at that point, it becomes, which community do you piss off the least?”</blockquote><p>Each of these groups must be represented, in some way. If you miss one, you risk irritating them, and potentially nuking yourself past the <a href="https://blogs.cardiff.ac.uk/sarahlethbridgelean/trust-thermoclines/">trust thermocline</a>.</p><p>Your smallest groups might be the most vocal, and your largest might be the most quiet. Your streamers might have an idea of where the game should go, your data might be saying something else, and you might have four different communities with needs that simply can’t be met with the budget and resources you have.</p><p>Further on, Liana discusses the <em>other</em> side of the job — dealing with designers, producers, engineers, and decision-makers — all who have <em>their</em> idea of what a feature should look like, or what should be focused on.</p><p>So, to recap: you have different communities and interests (streamers, users, creators, hardcore players, casuals, business needs, small niches, and so on) all vying for your attention, and all (often) screaming at each other.</p><p>And it’s your job to make sense of all of it for the rest of your team — and, not only that, to knowingly keep tabs on who <em>isn’t</em> being served by a decision that gets made, and figuring out how to best explain that to them while not throwing another element of the community (or your company!) under the bus.</p><p>You are a two-way ambassador. In the community, you serve as the representative for the rest of the company — and behind closed doors, you serve as the community’s ambassador to the folks making the inevitably hard development choices.</p><h3>A Brief Detour to Discuss Becoming a Diplomat</h3><p>At the top of this section I listed “community shop steward,” and I really want to dig down on that.</p><p>If you’re unaware of what a shop steward is, they’re generally someone in a union shop that serves as a representative for folks to make sure that the company can’t take advantage of them. If someone gets written up, for example, for not doing their job, typically the shop steward will step in to make sure that they know their rights (or their contract).</p><p>My dad did this and shared a lot of stories with me when I was growing up. It was often a hard position to be in — you’d be trying to help folks understand what they needed to do, or what protections they had, and sometimes they’d just ignore you. Alternatively, sometimes you’d be advising and trying to help someone that made your work life difficult.</p><p>My dad was really talented at what he did, and he’d tell me stories of having to help folks that were much worse at his job than him — folks that would mess up, wouldn’t listen, and then he’d have to defend them. They wouldn’t understand what his role was (either as an employee or as a union representative) and end up directing their anger at <em>him</em> instead of the company.</p><p>This made it difficult to remain a shop steward for my dad, but he felt it was important, so he kept doing it.</p><p>I think most community managers can probably relate to this.</p><p>The thing about diplomacy — about being an ambassador — is that you don’t always get what <em>you</em> want. That, after all, is the nature of compromise. It’s about fighting the good fight, trying to get folks’ voices heard, and then realizing when you need to bend on this or that in order for the end product to meet the needs of the many. This is hard — and it’s a never-ending process.</p><p>But, very often, one or two elements of the community will get angry at you personally for some perceived change they do not like — or for some communication they did not receive. Because this is the internet, and because you are the most visible person of the team, this means it’s almost a rite of passage for a community manager to receive all kinds of really unpleasant things in response to a “bad change.”</p><p>On the light side, that’ll mean people posting about how you’re bad at your job, or how you should be outsourced. On the heavier side, it’ll mean people trying to dox you, to swat you, to send you death threats and gore.</p><p><em>(And it’s also one of the reasons that, internally, we sometimes jokingly call ourselves the “tank” of the team — we take the heat so our fellow developers can keep working without having to see what we see, or be harassed like we are.)</em></p><p>And that can be hard, because even among the bile, sometimes there’s solid criticism in there, and you have to remain level-headed and humble enough to be able to sift through the emotion, to have empathy, and to have a certain level of discernment to figure out where the pain is coming from — and to be able to isolate that feedback and bring it back.</p><p>This is really fucking hard — and it’s one of the main reasons why we don’t have a long shelf life. Here’s a quote, that fits with my experiences talking with others in the field:</p><blockquote>“It’s a tough gig. A community manager typically lasts only three years before either burning out or moving on to something else. The best community managers are brilliant connectors, but they can ‘disappear in a puff of smoke’ due to the exhausting efforts required of them.” (<a href="https://berniejmitchell.com/what-is-community-manager-burnout/">source</a>)</blockquote><p>This is something I’ll likely talk about more in a later post. Before moving on though, I’d like to say something to my fellow community managers:</p><p><strong><em>Stepping away doesn’t make you a failure — burnout is a huge issue in our profession, and believe me, it’s real understandable.</em></strong></p><p>There are easier ways to make more money, and “passion” doesn’t pay the bills. If you’re a broken person like myself and love it — or you’re just <em>on that zen grind</em> (this is what I tell myself), then by all means, stick to it. But it’s okay to move on.</p><p>A lot of us do, and all of your colleagues really and truly get it. Those of us that survive are not doing it through grit or strength, but likely because we’re just lucky enough to have strong support networks and employers who really understand our worth and do their best to support us. Without that, burnout is inevitable (and even with it, to be honest).</p><p>But yeah — back to the job.</p><p>“Community management” is never about managing a community, but managing communities. It’s allowing yourself to be a catalyst for others in the boardroom, and then managing to make all parties understand where the other is.</p><p>In VRChat, this means understanding that you have engineering-focused creators who want code-focused tools, you have artistic creators who want to <em>never </em>think about code, you have creators who want to make a game (but are artists) and you have engineers that want to make art (but with code). You have users who have thousands of dollars of hardware, who attend PC-only events nightly and you have users with mobile-based devices that simply want to say hi to their friends. You have myriad hardware options, situations, use-cases, and ages ranges, and they all can’t even decide if they’re playing a game, logging into a platform, or interacting with a social network.</p><p>My job, in short, is understanding all of them and what they want (and need) well enough to represent them… and then to balance them against one another. Oh — and then to be able to explain all those little nuances to… well, everyone.</p><p>…and remember that other category? You’re going to be doing <em>all of those other things</em> on top of this, and those things will change over time.</p><p><em>(And if you want to know why that is… well, that’s for another post!)</em></p><p>This is a never-ending struggle! It requires (really, demands) constant improvement. It’s a job that requires you to put your ego aside, while at the same time not being afraid to push back when necessary. Out of every job I’ve done, it’s easily the most stressful — and it’s not close.</p><p>But it’s also the most rewarding, and that too, isn’t close.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=06565c17f385" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>