theopensourceway / guidebook

Guidebook of open source community management best practices; is somewhat opinionated.
Other
170 stars 42 forks source link

Write a chapter on community manager self-care #70

Closed semioticrobotic closed 3 years ago

semioticrobotic commented 4 years ago

File name in repo: community_manager_self_care.adoc

Needs a Conclusion

Compose a guidebook chapter explaining the importance of community manager self-care, with tactics and resources for maintaining healthy community management behaviors.

In #69, contributor @samus-aran proposed an excellent overview of this material. Let's consider beginning this work as a chapter and broadening to an entire section of chapters if a single chapter grows large enough to warrant.

semioticrobotic commented 4 years ago

For some reason, I am unable to make @samus-aran the assignee?

quaid commented 4 years ago

@semioticrobotic I'm not entirely clear how we want assignments to work, but I think your barrier is that in this project (config or just the way things are?) the assignee needs to be a member of the project. I just invited her, so we'll see if that works.

I think that may be a "way things are", that you can only assign issues to people who are project members. I don't think there needs to be a barrier to being a project member other than interest (ask for it, say yes to offer).

quaid commented 4 years ago

We just saw a presentation by @mary-grace on "Community Manager burnout". I took these notes, which are incomplete I'm sure but largely capture the essence of things. There are some quite useful bits in here, such as the five signs of pending burnout.

5 causes of burnout -- These are things you can watch, ask for changes around to prevent burnout

  1. Lack of Control
    • decisions made without our input
    • things difficult in the community e.g. CoC violations
    • can't control the people around us
  2. Unfairness
    • responsible for too many things
    • always lands on your plate
  3. Insufficient Reward
    • can be salary/comp
    • recognition, in community or org
  4. Work Overload
    • not being to stop and put focus on one specific project
  5. Lack of Community
    • ironic
    • surrounded with those we are taking care of, while being forced or feeling forced to neglect our own communities

13m search results showing "burnout community managers" shows this has been an exponentially growing discussion and need now being addressed. More search results likely due to:

What can I do about it? (for individuals)

  1. Put on your oxygen mask first -- if we aren't getting enough O2, we aren't going to be able to help others
    • be selfish, it helps you be selfless
  2. Step away from the work
    • Learn to say no
    • Get your workload reprioritized to take things off
  3. Take time when you are sick
    • mentally, physically
    • medical issues that deserve attention that a medical problem get
    • insurance policy may have more resources
  4. Find our own communities
    • ones that work FOR us
    • non-tech related may be a good idea
    • people who share similar experiences or interests

What can I do about it? (for managers)

  1. Schedule 1:1s
    • regular (weekly, bi-weekly)
    • not about current work but check-in about how they are feeling about work
      • impact
      • too much on their plate
      • what are the motivated vs required to do
  2. Mistakes will happen
    • blamless post mortems
      • "Accelerate" book recommendation
    • conversations about how to do things better in the future
    • how to best handle them going forward
    • retrospective about what is going well/not going well
      • team, manager, org
  3. Encouraging staff to take time off
    • own health, health of team
      • take time off to recover, better able to focus and take care of community when working
  4. Manager is the umbrella
    • help prioritized, de-prioritize
    • shield them from work they shouldn't be loaded with
    • resources and time needed to do work expected

The Dark Side of Community Management

Resources

Q&A with community managers

Audience suggested resources

samus-aran commented 4 years ago

Just a quick mention here that above is a fantastic overview of the presentation (I believe I'm looking at the same one "The Care and Monitoring of You"). :+1:

Some additional resources: https://burnout.io/en/latest/index.html https://burnout.io/en/latest/furtherReading.html Also reading "The Business Value of Developer Relations: How and Why Technical Communities Are Key To Your Success - Mary Thengvall (Mary Grace)" section about burnout

lmaffeo commented 4 years ago

Love this idea, @semioticrobotic. Ashley McNamara's keynote at ATO last year - The Thing About Burnout - would be a great source for this chapter.

vmbrasseur commented 4 years ago

Decloaking for a moment:

No general objections to the idea of the chapter. However, as this would be walking the fine line of health advice, it's probably best to enlist a mental health professional to write/assist. The advice of well-meaning amateurs can be problematic.

mary-grace commented 4 years ago

I completely agree! I talked with @samus-aran about this on Monday as well. Any suggestions I give in my book or in any talks are always framed with "I'm not a medical professional." I'm simply speaking from personal experience in the community manager role and know personally just how prevalent of a problem burnout can be for this particular subset of tech professionals. The tips I give are far more about how to manage pre-burnout symptoms and what Ash and I talked about at more depth included ways to make sure moderators have the appropriate training (e.g. https://www.mentalhealthfirstaid.org/) to handle any issues within their communities.

vmbrasseur commented 4 years ago

While I respect that, even advice prefaced with "I'm not a medical professional" can still be interpreted as medical advice by the audience. Best to play it safe with such things and collaborate with someone who can say "I am a medical professional." IME, if you ask them they're very happy to help.

samus-aran commented 4 years ago

@vmbrasseur I would very much agree with that statement. I don't know at this very moment in time if there would be any barriers to ask a medical or healthcare professional to collaborate in the context of a guide such as this but that shouldn't stop the process of requesting for input. I personally would like to see a sub-section that details at a high level a where-to-go-from-here if seeking official medical advice supported by the medical professional(s) input. However, we need to ensure that it is generic enough, not specific US based practises/support groups, due to the global audience.

On the more conservative side and not getting too ahead of ourselves, having a health care advisor would certainly be a plus for this section if not a minimum if possible but not a current blocker to begin the chapter. Now sourcing that professional is another challenge... Anyone have any referrals or those that specifically deal with online community managers or tech?

quaid commented 4 years ago

This is such a thoughtful discussion, I thank all of you. I appreciate us taking care of each other, ourselves, and others not present, all in the process of talking about writing about taking care of ... Using our own best practices to do this thing is one of my favorite recursive pleasures of this project.

I think @vmbrasseur's point highlights that there are going to be two types of content in this guide -- where community architects/managers hold the experience, and where other professions hold the experience.

For the latter, we would normally/ideally e.g. have a technical edit of a chapter on code audits by a software engineer, and a legal review of a chapter on choosing a license by an experienced open source software lawyer. Thus is makes sense to follow the equivalent is for a medical or mental health professional to provide review/guidance on the content.

I was talking with Leslie Hawthorn about this the other day; she is this project's mentor and one of our chief champions. We agreed that while we didn't quite know how this will work, we are committed to going this necessary step for this content. It's the right thing to do for any content, and particularly important for one with such interpersonal effects. We'll take the details on "who/how" to the private back channel for discussion, in respect of the sensitivity and unknown nature of this.

samus-aran commented 4 years ago

Hey just a quick call out to the team @quaid or @semioticrobotic That I'm unable to be assigned to this issue. I believe I need to have write access in order to assign myself, unless a team member wants to assign this to me ^^ (I'll write a quick note on the governance issue on the overall set up of teams of the repo's organisation to help with new assignee/project members)

semioticrobotic commented 4 years ago

Thanks very much for raising this, @samus-aran. I was able to add you as an assignee on this issue, but agree that's a stopgap action until we can determine the best way to organize access privileges and the like. I'll take a look at the issue you've opened regarding this. Thanks.

samus-aran commented 4 years ago

Just a quick update that I'm looking to get started on this next week :)

quaid commented 4 years ago

Just noting here that we'd like to include this chapter in a preview release in a few months, schedule TBD.

samus-aran commented 4 years ago

A wee update! I'm back to having a completely dedicated schedule for this so this is my priority at the moment :+1: I am aiming for a PR pushed by this time next week. I may push it up earlier with the expectation it's WIP and then add to it reaching the deadline.

Apologies on the radio silence if it was felt.

samus-aran commented 4 years ago

Further update, working well on this. Though it has become a bit of a monster. I will reflect upon why I feel this is when the PR is pushed up as well as other points to highlight like references, suggested SMEs etc. I'm just revising the chapter as a whole and converting everything into American-british :wink:. Expect a PR in the next couple of days :+1:

semioticrobotic commented 4 years ago

Reopened as reaction to automation.

quaid commented 4 years ago

@samus-aran Just a heads up that I have a solid lead on your SME review plan, and am feeling pretty confident we will land a review in the coming few weeks.