Do the Work

It’s been one month since a white police officer in Minneapolis murdered George Floyd, a 46-year old Black father of five. I’ve found the subsequent response remarkable for its intensity, unprecedented diversity, and impact. While I’m moved by how many people and organizations seem genuinely compelled to act, I’m also vexed by some of the rhetoric around what “doing something” actually means.

Woke theatre aside, I get that it’s hard to know what to do or how. I can see how easy it is to be overwhelmed by the enormity of wanting to eradicate 400 years of structural and cultural racism or by the fear of doing or saying the “wrong” thing. Fortunately, there are a lot of resources out there, and folks have been circulating them with abandon. While many resonate with both my personal and professional experience, I’ve found several to be questionable or worse, and I can’t help feeling like most of this resource sharing misses the point. You can’t just work your way through a listicle and solve racism.

This work is hard, but maybe not in the way most of us think it is. The muscles required to create a more equitable society are the same ones needed to be skilled collaboration practitioners, and they can only be developed through practice and repetition. The key is to focus on the right things and to do them over and over again. The devil, of course, is in the details, and I want to riff on those here.

But first, I want to tell two stories. The first is about data, narratives, and human psychology.

According to the Mapping Police Violence database, 91 people have been killed by police in the 38 days since George Floyd’s murder. Nineteen of them (21 percent) were Black, a slight decrease from the overall percentage over the past eight years (25 percent). Thirty-two of the 91 killed were white.

I read all of the news items documenting each of these 51 killings (not counting the 40 victims of other or unreported race). The vast majority of the victims were armed. Many were violent criminals — rapists, murderers. Several of the deaths were the result of shootouts, and some cops died as a result. A few cases of both Black and white victims raised my eyebrows, but there was nothing that felt as clearly wrong and overtly racist as George Floyd’s murder.

Reading about these 51 deaths left me feeling depressed, but not outraged. As I dove more deeply into these incidents, I couldn’t help wondering how I would have felt about racialized police violence if I had not been exposed to countless stories like George Floyd’s over the years, if my only exposure to police violence were accounts like the 51 articles I read.

It was a troubling thought, because of all the numbers that I mentioned and stories that I shared, there’s only one that really matters: that 25 percent of people killed by police are Black. Why does that number matter? Because only 14 percent of Americans are Black, which means that Black people are disproportionately killed by police by a big margin. Even if George Floyd or Breonna Taylor or Philando Castile or any of the many Black women and men who were definitively unjustly killed by police over the years had never happened, that 25 percent number would still be a clear indication of a racial disparity that needs to be addressed.

Therein lies the essential challenge. No one has ever looked at a number and taken to the streets. There are lots of mental hoops required to make sense of that number, to trust its implications, and then to get outraged by it. We’re seeing this play out right now with the massive racial disparity of COVID-19 deaths, which is killing far more Black and Latinx people than police violence, yet hasn’t resulted in large-scale public outrage. In a perfect world, it shouldn’t take a shocking video of a Black man being callously suffocated to death by a smug white police officer for folks to recognize that the system is racist, but for most of us, that’s exactly what it took.

Except that’s not quite the whole story either. As visceral as George Floyd’s death was, it still wouldn’t have had the impact that it did without the massive amount of work and resources that the Movement for Black Lives has invested in organizing, mobilizing, and collectively aligning around a policy platform over the past eight years. Contrary to how it may appear on the surface, the Movement for Black Lives isn’t just a hashtag. It’s also not a single organization with a clear hierarchy of decision-making and leadership. It’s a network full of leaders, organizations, and activists, some more visible than others, but every one of them playing a critical role. That makes it harder to understand, talk about, or fund.

Human beings love simple, emotional narratives. We need to accept this about ourselves and leverage it to motivate change. But once we allow ourselves to be moved, we also have to be willing to let go of these simple, emotional narratives and dive more deeply into the messy and far less compelling nuts and bolts of the work. Real change takes lots of hard work, the kind that most people are completely uninterested in hearing about or doing.

The second story I want to tell is about basketball.

When your team has the ball and is trying to score, one of the easiest ways to help your teammates is to set a screen. This consists of positioning your body so that it serves as a kind of wall that prevents the defender from chasing your teammate. If the defender sees it coming, they can try to dance around the screen, but that split second of separation is often enough to give your teammate an advantage. If the defender doesn’t see it coming, then it results in a collision, which usually hurts them a lot more than it hurts you.

If you’re defending, and you see the other team set a screen, all you have to do is yell, “Left!” or “Right!” depending on where the screen is relative to your teammate. At best, your teammates can adjust and eliminate the offensive advantage. At worst, you save a teammate from a painful collision. It is a simple and effective intervention that doesn’t require any special athletic abilities. All it takes is attention and communication.

Still, it’s not intuitive. Many players — even experienced ones — have to be told to “call out the screens,” often by a frustrated teammate who has just been flattened by one.

I find this fascinating. Basketball is a hard sport to learn and play. I’ve played it my whole life, and I’m still mediocre at the shooting and dribbling part, which require physical acumen. But I’m great at calling out screens, which simply requires me to talk. Why is it so hard for others? Why isn’t this the first thing that people learn how to do?

It turns out that being an ally is a muscle, and that developing that muscle takes practice.

A few weeks ago, I was on a check-in call for a network of Black activists and allies. On the first part of the call, folks shared a number of inspiring stories about some of the amazing work happening on the ground in Minneapolis and other places around the U.S. Themes around being invisible and the importance of reclaiming one’s own agency and not replicating existing power dynamics came up over and over again.

Afterward, we broke out into small discussion groups. I was in a group with four other people, including a moderator. None of us knew each other, so the moderator called on people, one-by-one, to introduce themselves, and he inadvertently skipped me. I waited several moments for someone — anyone — to point this out, but nobody did, and the group started diving into the discussion. I finally found a point to jump in, saying with a smile, “I have a thought, and while I’m at it, I’ll also introduce myself.”

The moderator profusely apologized, not just in the moment, but throughout the rest of the discussion. I was touched by how badly he clearly felt. It was fine, I knew it wasn’t intentional, and I would have been okay regardless. And everyone in the group was lovely. What really stuck out for me, though, was how no one else in the group noticed or said anything, especially after all of the talk beforehand about the importance of seeing each other, of being seen, and of being good allies.

I’ll say it again: This work is hard, but maybe not in the way most of us think it is. The muscles required to create a more equitable society are the same ones needed to be skilled collaboration practitioners, and they can only be developed through practice and repetition. The key is to focus on the right things and to do them over and over again.

I’ve worked with all kinds of groups over the years, including many social justice groups, and I’m constantly struck by how bad most of us are at the fundamentals. It’s why I’ve moved away from larger systems change projects and have focused my energies on training and coaching. If you’re trying to create a more equitable world, but you can’t even run an equitable meeting, much less an equitable organization, you’re focused on the wrong problem. Everything is connected. If we just stepped back and started with smaller, simpler (but by no means simple) challenges, giving ourselves plenty of permission to make mistakes along the way, we would be far more likely to make headway with the bigger, harder societal problems that so many of us care so much about.

Which brings me to the thing I really want to say to collaboration practitioners and organizations who want to contribute to a more racially just world. Urgency is the enemy of equity. If you really want to make a difference, start by slowing down.

All of the racial equity training in the world won’t make a lick of difference if you don’t have the mechanisms and the right mindsets in place to get clear and aligned about success, to adjust based on what you’re learning, and to hold yourselves accountable to your stated values. In many ways, these are the easiest things to implement, and yet they’re the things groups are most likely to skip. I can’t tell you how many groups have approached me over the years wanting to change their culture somehow, someway, and yet weren’t willing to schedule regular time to assess how they were doing. Frankly, most practitioners I know skip these steps too, and our impact suffers as a result. We get away with it, because no one holds us accountable to long-term success, and the status quo continues merrily on its way.

Earlier this year, I wrote about my six-year journey to learn how to slow down. I know how hard it is to change these habits, and I don’t want to suggest that what I did will work for everyone. All I know is that it matters, that it’s an affliction that infects many of us, and that you’re more likely to propagate than address inequity if you don’t figure out how to fix this. It won’t be worthy of a press release, but it’s more likely to result in the impact you want to have in the long run. Moreover, if enough of us do this, the right things will start to happen in society at large.

Update: I clarified the number of victims since George Floyd’s death (91) above, explaining that I focused on the Black and white victims (19 and 32 respectively, for a total of 51). Thanks to Travis Kriplean for the suggestion.

Illustration from Black Illustrations: The Movement Pack.

Do-It-Yourself Strategy and Culture

Biker

In 2009, I was asked by the Wikimedia Foundation to design and lead a movement-wide strategic planning process. The goal was to create a high-quality, five-year strategic plan the same way that Wikipedia was created — by creating a space where anyone in the world who cared could come and literally co-author the plan.

We had two fundamental challenges. First, it wasn’t enough to simply have a plan. It had to be a good plan that some significant percentage of the movement both understood and felt ownership over.

Second, we were asking people in the community to develop a strategy, but most people had no idea what strategy was. (This, frankly, is true of people in general, even in business.) It was different from Wikipedia in that most people already have a mental model of what an encyclopedia is. We had to be more concrete about what it was that we were asking people to do.

I explained that strategic planning, when done well, consists of collectively exploring four basic questions:

  • Where are we now?
  • Where do we want to go? Why?
  • How do we get there?

I further explained that we were going to create a website with these questions, we were going to get as many people as possible to explore these questions on that website, and by the end of the year, we would have our movement-wide, five-year strategic plan.

And that’s essentially what we did.

Get the right people to explore core questions together. Where are we now? Where do we want to go, and why? How do we get there? Provide the space and the support to help these people have the most effective conversation possible. Trust that something good will emerge and that those who created it will feel ownership over it.

This is how I’ve always done strategy, regardless of the size or shape of the group. It looks different every time, but the basic principles are always the same. People were intrigued by what we accomplished with Wikimedia, because it was global and primarily online, because we had gaudy results, and because Wikipedia is a sexy project. However, I was simply using the same basic approach that I use when working with small teams and even my own life.

The craft of developing strategy is figuring out how best to explore these core questions. It’s not hard to come up with answers. The challenge is coming up with good answers. To do that, you need to give the right people the opportunity and the space to struggle over these questions. That process doesn’t just result in better answers. It results in greater ownership over those answers.

Breakfast and Culture

What’s your strategy for eating breakfast in the morning?

Are you a grab-and-run person, either from your own kitchen or from a coffee shop near your office? Eating breakfast at home is cheaper than eating out, but eating out might be faster. Are you optimizing for time or money? Why?

Maybe you have kids, and you value the ritual of kicking off the day eating together? Maybe you’re a night owl, and you’d rather get an extra 30-minutes of sleep than worry about eating at all in the morning.

Where do you want to go? Why? How do you get there? These are key strategic questions, but you can’t answer them without also considering culture — your patterns of behavior, your values, your mindsets, your identity. Choosing to cook your own meals is as much a cultural decision as it is a strategic one.

In my past life as a collaboration consultant, groups would hire me to help with either strategy or culture, but never both. I realized fairly quickly that trying to separate those two processes was largely artificial, that you couldn’t explore one without inevitably colliding with the other.

Peter Drucker famously said, “Culture eats strategy for breakfast.” He did not intend to say that one was more important than the other, but that both were necessarily intertwined. Or, as my friend, Jeff Hwang, has more accurately put it, “Saying culture eats strategy for breakfast is like saying your left foot eats your right foot for breakfast. You need both.”

As with strategy, culture work is a process of collective inquiry, except instead of focusing on action (where do you want to go?), the questions are centered around identity:

  • Who are we now?
  • Who do we want to be, and why?
  • How do we get there?

The key to effective culture work is to explore these questions yourself, to struggle over them together as a group, and to constantly revisit them as you try things and learn.

DIY Strategy and Culture

Toward the end of 2013, Dharmishta Rood, who was then managing Code for America’s startups program, asked me if I would mentor one of its incubator companies, which was having some challenges around communication and decision-making. I had been toying with some ideas for a do-it-yourself toolkit that would help groups develop better collaborative habits on their own, and I suggested that we start there.

We immediately ran into problems. The toolkit assumed that the group was already aligned around a core strategy, but with this group, that wasn’t the case. They had been going, going, going without stopping to step back and ask themselves what they were trying to accomplish, how they wanted to accomplish those things, and why. (This is very typical with startups.)

This group needed space to do some core work around strategy and culture. I threw out my old toolkit and created a new one designed to help groups have strategy and culture conversations continuously and productively on their own. The revised toolkit was based on the key questions underlying strategy and culture depicted as two cyclical loops:

Strategy / Culture Questions

While most strategy or culture processes are progressively staged, in practice, inquiry is never linear, nor should it be. Spending time on one question surfaces new insights into the other questions, and vice-versa. Where you start and the order in which you go are not important. What matters is that you get to all of the questions eventually and that you revisit them constantly — hence the two cycles. My colleague, Kate Wing, recently noted the resemblance of the diagram to bicycle wheels, which is why we now call it the Strategy-Culture Bicycle.

Dharmishta and I saw the Bicycle pay immediate dividends with this group. People were able to wade through the complexity and overwhelm, notice and celebrate what they had already accomplished, and identify high-priority questions that needed further discussion. Furthermore, the process was simple enough that it did not require a third-party’s assistance. They were able to do it fine on their own, and they would get better at it as they practiced.

Pleased and a bit surprised by its effectiveness, I asked my long-time colleague, Amy Wu of Duende, to partner with me on these toolkits. We prototyped another version of the toolkit with four of last year’s Code for America accelerator companies, and once again, saw great success.

We’ve gone through eight iterations together, we’ve tested the kit with over a dozen groups and individuals (for personal and professional life planning), and we’ve added some complementary components. A number of practitioners have used the toolkit on their own to help other groups, including me, Dharmishta, Amy, Kate, and Rebecca Petzel.

I’m thrilled by the potential of toolkits like these to help build the capacity of practitioners to act more strategically and to design their aspired culture. As with all of my work, these toolkits are available here and are public domain, meaning that they are freely available and that you can do anything you want with them. You can also purchase pre-printed packages.

Please use them, share them, and share your experiences! Your feedback will help us continuously improve them.

Working Less (and Other 2015 Strategic Priorities)

Child Labor

For over a decade, my work has fundamentally been about creating a world that is more alive. My specific focus has been on building up society’s collaborative literacy — the muscles and mindsets we need to be and work together more effectively.

Every year for the past five years, I’ve carefully mapped out a set of goals and strategies that I think will put me on the best path toward realizing my vision. In each of those years, I’ve had three priorities, and the third priority has always been something around work-life balance. In each of those years, I’ve monitored my progress and made adjustments throughout, and at the end of each year, I’ve assessed my overall progress.

Every year for the past five years, I’ve seen a similar pattern. I do well on all of my goals except for the one on work-life balance. I’ve seen incremental improvement every year, but I continue to be far from my targets.

I spent a lot of time at the end of last year reflecting on this. Was this the right goal? Did I need to reframe what I meant by work-life balance? Or did I simply need to experiment with different strategies?

I decided that it was still a critical priority for both personal and professional reasons. I believe in the importance of slowing down, that balance and pace will make me a better practitioner and a better person. I believe that we as a society need to be better at this, and I want to model this practice.

So I kept it as a goal, but I made a few changes. I reframed it slightly, and I made it my top priority.

This year, my number one strategic priority is to work less.

Working less is a clear goal. I’m confident that my metrics (which are based on hours worked and some self-care indicators) are relevant, and I’ve got specific targets, which means that I can clearly and objectively see whether or not I’m achieving this goal. If I hit my targets, I’m confident that I will be happy and healthy.

The real question is whether or not working less will make me more effective at achieving my higher-level goals. I believe it will. If I’m forced to work less, that means I’ll also have to work smarter. I’ll have to make better decisions about how I use my time, which means saying no more often than saying yes. I believe I already have the muscles to do this. Constraints will give me the incentive to use these muscles.

Three months into 2015, I’m thrilled by the results so far. I feel like I have plenty of space to think about the big-picture and also to focus and get things done. I’m seeing the people I want to see, and I’m deepening my relationships and my practice. I’ve definitely had to take things off of my task list — it’s no accident that this is my first post here this year — but the tradeoffs have been worth it, and I think my focus will pay off in big ways.

To understand what this means more concretely, it’s important to understand my other two strategic priorities for 2015. First, I’m focused on building a platform for developing collaborative literacy. Second, I’m looking to engage with 1,000 changemakers.

Building a Platform

I believe that the best way to develop collaborative literacy is through lots and lots of practice.

I’m supporting practice in two ways. First, for the past two years, I’ve been developing and prototyping workouts under the auspices of my 15-week Collaboration Muscles & Mindsets program. I’m really excited about how the program has evolved, and I’m looking to document and distribute what I’ve learned more widely (and, of course, freely). I’m currently doing the program with Forward Together and some of its partners as part of a larger innovation process, and I’m looking for others who’d like to try it. (Contact me if you’re interested!)

Second, I’m trying to create the equivalent of balance bikes for changemakers. These have largely taken the form of DIY toolkits for developing strategy and culture, which I’ve been developing in partnership with Duende and many others and which will also be freely available.

I’ve been prototyping these with lots of groups over the past year, and I’m super excited by how effective they’ve been. Several practitioners have already incorporated these toolkits into their work, and demand has been high. I’m focused on continuing to refine and improve these toolkits and also documenting and distributing them in order to meet demand.

I care about chefs, not recipes, so I’ve been consciously focused on developing tools that support practice rather than writing things that are prescriptive. A number of colleagues have pushed back, suggesting that I’ve been too extreme about this. They’re right. Even though my frameworks are extremely simple, I still have them and ought to share them more proactively. I’ve written about some of them here, but they’re not easily findable. Part of the work of building a platform is weaving these frameworks together so that they’re widely accessible.

Engage with 1,000 Changemakers

Toward the end of last year, I sifted through lots of data to try to get a sense of how many people I engaged with. I came up with roughly 250. A surprising number of those were face-to-face or phone interactions, so 250 felt like a lot. But if my goal is to scale practices that will improve collaborative literacy, I need to reach a lot more than 250 people.

To some extent, creating a good platform — for example, simply documenting and publishing my aforementioned toolkits — will help expand my reach. However, simply hitting my numbers are not the point. The quality of engagement matters, which means going beyond simply making my work more accessible online.

Specifically, I’m focused on deepening my engagement with a core set of practitioners. I’ve been doing that with a small, local group of peers, which we call our “colearning group.” I’ve also been much more intentional about finding and working with emerging practitioners. All of this has helped my own practice tremendously and has also led to better toolkits.

It’s also been the best way to disseminate practices and mindsets for doing this work effectively. Every one of these practitioners are already taking what they learn out into their own communities, and a better platform will better support them in doing so. Furthermore, by modeling a culture of shadowing and mentorship, we are hopefully encouraging others to adopt similar learning practices.

This year, I hope to write less frequently, but more impactfully. I’m excited by what I’ve been doing and learning so far, and I’m looking forward to sharing more in the ensuing months.

The Secret to High-Performance Collaboration: Slowing Down

Run, Serena, Run!

At my previous consultancy, we used to spend a considerable amount of time debriefing every engagement, big or small. We were meticulous in our analysis, nitpicking every detail.

Over time, I started noticing a few patterns. First, I realized that our debriefs were largely ineffective, because we weren’t taking the time to integrate what we learned. We needed to be reviewing past debriefs before new engagements in order to remind ourselves of what we had learned and in order to hold ourselves accountable to improvement. Without that additional space, our debriefs were essentially exercises in self-criticism and generating lists, two skills we didn’t need to be practicing.

Second, a few things began to jump out at me as I reviewed our long list of things we could have done better. Almost without fail, when we had “bad” engagements, someone had slept poorly the night before. Or someone had been working while sick. Or someone had forgotten to eat breakfast that morning. (Forgetting to eat was my personal bane.)

We had spent hours and hours and hours debriefing, and this is what we learned:

  • When we didn’t take care of ourselves, our performance suffered.
  • When we didn’t take time to remind ourselves of past lessons, we repeated the same mistakes.

One of my mentors, Gail Taylor, is always encouraging me to seek the simplicity embedded in complexity. What I’ve realized over the years is that, when I find it, I often dismiss it. It seems too obvious. There has to be something else.

Slowly, but surely, I’m breaking this habit, and I’m starting to see more clearly as a result. Which brings me to my biggest insight over the past several months.

The best thing we can do to improve collaborative effectiveness is to slow down.

This has been coming up for me over and over again with all of my recent projects and experiments.

I’m currently doing an experiment with the Code for America incubator in trying to help new companies establish good collaborative habits right from the start. PostCode (the company with which I’m working) is working at a startup pace, and they’ve had inevitable challenges as they move through their storming phase.

Fortunately, when problems crop up, they deal with them quickly. In those situations, they’ve often reached out to me about possible toolkits to help them navigate their challenges. My answer has been consistent: Slow down. They haven’t found the time (beyond the work we’ve done with them, which has been too constrained) for critical conversations about organizational strategy, culture, and group dynamics. It’s understandable. They’re under a tremendous amount of pressure, and in those situations, conversations about strategy and group dynamics can feel like a nice-to-have, not a need-to-have.

Last week, I facilitated a practitioners workshop for the Garfield Foundation on collaborative networks. For one of the Open Space sessions, I led a group through the power workout I developed for Changemaker Bootcamp. We had a wonderful, nuanced conversation about power dynamics, and several people asked, “How do we make sure we have more of these conversations with our constituencies?” My response: “The first step is making the time.”

Telling others (or even yourself) to slow down is easy. Actually doing it is hard. We move fast because of external pressures, mindsets, habits, cultural norms, and so forth. We have little control over most of these things, and what little we can control is incredibly hard to change. But there are tricks that I’ve found helpful over the years.

Experiments. Changing habits is hard, and you will likely fail many times. Approaching the challenge of slowing down as a series of experiments helps. As I wrote previously, one of the keys to a successful experiment is to hold yourself accountable to the results. Failure is okay as long as you’re committed to the intention and are actively incorporating what you learn into new experiments.

If you are truly committed to slowing down, write it down. Write, “Slow down,” on a piece of paper, and put it up where you will see it. Actively devise and track experiments that will help you do this, so that you can monitor your progress and see what’s working and what’s not.

For important conversations — whether it be organizational strategy or a project debrief — schedule those in advance as part of your project plan, and track whether or not they actually happen. If they don’t happen, take the time to examine why, and devise another experiment. The beauty of applying an experimental framework is that simply the process of devising and tracking an experiment is an act of slowing down.

Checkins. My former business partner, Kristin Cobble, recently wrote a wonderful piece on the power of checkins. She describes them mostly in the context of meetings as a way to invite participation and to garner a sense of the collective whole. What I’ve learned over the past several months is that they also serve a much simpler, deeper function. They force you to slow down and reflect — even if just for a moment.

Starting last year, I embarked on a simple experiment with my friend, Seb Paquet, who’s based in Montreal and who, like me, works for himself. We decided to check in with each other once a week for an hour over Skype. We didn’t have any agenda. We would simply use that time to have an extended checkin.

We ended up doing two phases, and it served to be tremendously valuable. Not only did it deepen our relationship, it served several practical purposes. We both had an opportunity to give each other feedback on our respective projects. We supported each other when we faced challenges and cheered each other when we succeeded. The most interesting thing to happen was that, even when things got tremendously busy for both of us, we both stayed very committed to these checkins. They were not just nice-to-have; they were helping us work more effectively.

Inspired by these results, I invited my colleagues Pete Forsyth, Rebecca Petzel, Odin Zackman, and Amy Wu — who all work independently — to participate in a similar experiment earlier this year. We wanted to experiment with ways that we — as an informal network — could achieve the same (or better) benefits that people get from working in great organizations. In particular, we wanted to be more intentional about learning from each other. We called our experiment, Colearning 2.0, a play on the coworking movement.

We explored several things that we could do together, but we settled on doing weekly pair checkins, as Seb and I had done beforehand. There was some reluctance at first. One thing we all had in common was a frequent feeling of overwhelm, and taking an hour out of our week to “just talk” seemed burdensome. Not only did everyone end up finding the experience valuable, there’s a desire to continue the practice and take it to the next level.

I recently spoke with Joe Hsueh about his recent trip to Istanbul. One of the things that struck him the most about his trip was the adhan — the Islamic call to prayer. Imagine being in a bustling city of 14 million people where every day, at prescribed times, a horn sounds and the entire city goes silent. Imagine what it feels like to have that regular moment of collective, silent reflection.

I believe that checkins could be a powerful keystone habit that helps us slow down overall, which ultimately helps us collaborate more effectively. This is a hypothesis I continue to explore.

What helps you to slow down? What’s been the impact of doing so?