Microbes, Whales, and Everything in Between: A Vignette of Terror at 4x the Speed
A throwback flash talk from 2016! Let it remind you that you can do tough things, but:
A throwback flash talk from 2016! Let it remind you that you can do tough things, but:
I get a lot of WordPress swag over the course of the year. They are all charming reminders of specific events, but this year I got two that I especially loved.
Every once in a while, the WP Briefing episode about disagreements and decisions gets a big bump in listens. Right now it’s in the middle of one of those surges.
I often go back to old reference materials because I need to remind myself the best ways of moving forward in a difficult moment. So, to help folks who know they’ve heard me say it, but can’t quite get it to show up in search, here it is:
At this point I assume we all have seen the episode of Silicon Valley where Gavin says “the bear is sticky with honey”. While I found that entire plot line (?) incredibly funny, it also made me think about the way that we as leaders sometimes offer information to the people we lead.
Every leader I’ve had over the years, and I myself early on, would send pieces of content completely free of context. It would get forwarded without comment in an email, or dropped into a messaging app or social channel with a blithe “I’m just going to leave this here”. While I was always sharing it with the intention of letting other people come to their own conclusions, there was a point in my career when people started to feel like I was inviting them to a high-stress exercise in mind reading.
Context-free sharing of anything assumes that everything between you and the recipient is identical: the same frame of reference, values, and requisite information. I have found that, especially when I want team members to come to their own conclusions, I owe it to them to give them some concept of what made this worth their time in the first place.
So, I’ve stopped “just sharing” and instead offer content that’s relevant to current or past conversations and highlight why I found it relevant.
That’s it.
That doesn’t force a perspective. It makes it clear why you think it’s valuable to them, what area of focus it’s in, and ultimately makes it clear that you see their time is precious.
What methods do you use to help lead in lean times? Anything that helps rebalance the signal:noise ratio?
Late last year I attended a wonderful leadership session that walked us through closing the book on 2022 and preparing ourselves for the opportunities coming in the new year. There were 30 or so leaders representing a vast array of sectors, and in our opening breakout session we were invited to look at a number of individual images or quotes and select one or two that really called to us as a kōan for 2023.
The image I chose was something like this:
Now at first glance, there are a few obvious choices for what a photo like this might mean. It might mean that I expect the year to be fast-paced with a series of ups and downs. It could mean that I anticipate the weightless feeling of escaping something holding me back. It could also mean that I have grown a sudden interest in death sports.
But there is also a hidden sort of element to it and that’s what drew me to this photo.
If you are like me—a planning, strategic thinking, “yes, but how did we get here” type person—then you probably know that that photo implies countless hours of training, practice, and probably a handful of painful lessons. No one ever got to the point where they are floating, attached to nothing, free from the aid of wings or the safety of a harness without years of intense dedication.
For any sport like this (gymnastics, motocross, dance, surfing, anything) one of the earliest things you have to learn is how to fall well. Since what goes up must come down, you are told early on how to land safely. How to limit the risk (of injury) in the resolution (of reuniting with Earth).
I just wrapped up the latest episode of the WordPress Briefing. In it I talk about what the end of Phase 2 for the Gutenberg project does and does not mean for our everyday users. Throughout the writing and recording of that episode, all I could think of was this photo and that one phrase I immediately associated with it: “there’s risk in the resolution”.
From a big picture, long-term perspective it is easy to look at a project that successfully got off the ground and assume that the rest will take care of itself. There is an extent to which that’s true. Honing the skills, seeing the opportunities, and then having the wherewithal to put it all together in a way that creates enough speed and momentum to get you in the right place at the right time—yea, that’s hard. Once that’s done, the rest is just “get back down and continue safely forward”. But if you haven’t been told how to get down safely or how to convert that momentum into forward movement, then it’s more likely that you’ll run into difficulty doing those things.
Does that mean that I’m worried about the rest of our work on Gutenberg? No. I believe that the WordPress community can and does close the chapter on important projects all the time. If anyone can make this a joyous return to Earth, it’s the people supporting this project. But I also believe that they can because they have been for nearly 20 years.
Does it mean that I’ll be relying on our collective knowledge more than ever? Absolutely.
I have a list of reminders on my lock screen. If I remember, I’ll share one at the bottom of each of my posts in 2023, because we can never know who is in need of a little encouragement.
In case you hadn’t heard yet, WordPress is about to reach an important milestone. In May this year, the CMS that is the internet’s best kept secret (did you know that we power over 40% of the web?) will be turning 20 years old!
There will be a lot of opportunity to celebrate, so don’t forget to keep an eye out for more information!
There are quite a few resources from WordPress contributors over the years about how to identify and resolve conflicts in open source projects. There are posts that cover why conflict occurs, the structure of conflicts over time, and what to keep in mind while in the middle of conflicts.
I’d like to share some additional explanation of my Four Os checklist, a tool that I use to make sure I know the facts of a situation as well as the feelings. This was first shared on Andrea Middleton’s primer on Conflict De-escalation in Open Source which I also highly recommend.
If you’ve never mediated a discussion or helped to de-escalate a disagreement before, you will be surprised just how much the emotional state of the participants in the room can affect you. To make sure you are a well-grounded, calm-headed guide, there are two things you have to know going in: Know the facts, and Know the fights
In the heat of the moment, your short term memory can fail you, so having done the work ahead of time to assess the situation is important. Also, if you have asked all participants in a mediated discussion to answer these questions as well, then it’s easy to see where there are agreements, so folks can focus on working through the disagreements.
This is my primary checklist before heading into any conflict resolution work:
These might not all apply to every situation you encounter. Not all conflicts have deep and meaningful context (and that’s a good thing), sometimes it comes down to miscommunication. When we’re working across cultures, sometimes the role of an impartial guide through some facts and feelings is the thing we need most.
* I know this is a terrible name, but honestly, it’s all I can come up with. 🙂
Have you ever stopped to ask why documentation gets created? Those little bits of paper that arrive with your latest online purchase or crammed into that IKEA box, those make sense. They are there to tell you how to use the thing in the box. Their primary function is explanatory, but you could argue that “documentation” as we know it can broadly include these functions:
If you’ve never considered how documentation could be seen as a *diversity, equity, and inclusion effort, I’ve got a few things that will probably help open up that area of thought for you.
Had you ever looked at documentation from that point of view? What are other ways that “writing the docs” could bring more diversity into your communities?
If you’re not familiar with Dungeons and Dragons (or table top games in general), the best way to describe it is “collaborative story crafting where a group of characters try to solve problems, save folks in trouble, and survive quests that they uncover along the way”. A colleague of mine, Andrea Middleton, once used a Dungeons and Dragons style session to introduce contributors to some basic issues that arise during the course of organizing an event, and ever since that session folks have asked for more trainings in the same style. I had the opportunity to do this recently myself, so I thought I would share some tips for hosting a training adventure of your own.
When you’re hosting these sessions, it’s important to do some documentation before you meet. You will be playing the role of everyone except the people who are in the room so there is a lot to think through. But also, don’t worry about getting too granular since your team will be a little unpredictable—just know the general shape, the main players, and the key elements.
Before you host your session, determine how familiar your group is with this type of game. Not everyone plays games let alone adventuring table top games. If people have never played before, make sure you give them an overview of the process (or send them your favorite one shot). Also, if you are going to use this to track goals and progress over time, consider some sort of “character sheet” to document progress. Don’t get too rigid with the mechanics, though. You want them to come out having succeeded at the learning objective!
Once you’re finished, I recommend doing a little debrief if you have time. If you take good notes during their session, you’ll be able to go back and look at the various branches and see what could have been done differently.
This is a loose concept based on my recent experience. If you end up trying this, let me know in the comments!
When I woke up on Thursday, I was met with the devastating news that the Russian-Ukraine conflict had escalated. My first thought was, of course, whether anyone in the WordPress community lived in any affected areas. Then, I questioned what I could possibly do about it from halfway around the world.
I can’t comment on the specific politics of this conflict and, for what it’s worth, I can’t for the life of me think of the “right” thing to say. But when I don’t know where to start, I generally like to start small. So, I’ll share what I’ve been thinking about for my communities these past few days.
While I am certain that my words—no matter how carefully chosen—cannot possibly change the hearts and minds of nations with which I am wholly unaffiliated, I am equally certain that in my own communities there are people who are longing to learn how to help. I know I am.
As the world faces war, it’s also the same world in which kindness, community, and integrity co-exist—you are testament to that. WordPress is built on the commitment of thousands of contributors from all over the world to a unified mission. I’m sure many of you are in solidarity with those affected by this week’s events.
If you want to show your support, check in on your fellow contributors, friends, or families and let them know it’s okay to ask for help. You can also donate to a nonprofit that offers material relief or refuge to those in Ukraine. And of course, do what you can to stay informed. The world is a much more connected place today than it’s ever been. With all eyes bearing witness, learning, and paying attention, we are better equipped to move toward resolution.
But as you do all of these things to support your community, however you’re defining it, remember that you do not personally hold all the responsibility for “making things work” today. We are all here as part of a passionate and compassionate global community—please be gentle with yourselves and others.