A replacement plan is a great resource, even when you’re not being replaced.
A year ago, as the role of OpenStack community manager at Red Hat was moving from one person to another, we started thinking about what needs to be in place to effectively transition a role. More generally, we started thinking about planning, and documenting, for your eventual replacement.
We’ll talk about what worked, what didn’t, and what had unexpected benefits for the larger community.
This presentation helps existing and new community managers take a hard look at their roles within their projects to delegate tasks, encourage future advocates, and facilitate the evolution of their community role.
This post is going to be super first world and come from a place of massive privilege – I recognize that I’m in an amazing place to be able to talk about owning a house and selling it and buying another one and setting up my own office at home. That it’s amazing to have a job, to have a remote job, to have a well paying remote job with an amazing company like Red Hat. All that. This post is entirely about bragging about my new home office. And while I feel incredibly proud of how hard we’ve worked to get where we are today, I also realize how very much this is because we appear white and straight and well functioning and normal and this is very much an advantage we have in the world.
I have my very own home office.
Separate from my own home.
When we found out we were pregnant with twins, among the plethora of stressors was that we’d need to remodel our house extensively to make it work once said twins were old enough to want their own spaces. This is YEARS in the future, but it was still right there with all the other OMG things that were dancing through my DOUBLY hormonal brain.
And instead of taking a deep breath and Putting It Aside we put our house on the market, found a new house, packed, moved, and had babies.