What I’ve Learned About Building Collaboration Muscles

It’s now been seven years since I first started exploring a simple hypothesis:

  • Collaboration is a muscle (or, rather, a set of muscles)
  • You strengthen these muscles by exercising them repeatedly (i.e. practice)

Our current orientation toward collaboration is knowledge-centric, not practice-centric. No one expects anyone to get good at playing the guitar by handing them a book or sending them to a week-long “training,” yet somehow, this is exactly how we try to help folks get better at communicating or navigating hairy group dynamics.

I’ve spent the past seven years trying to change this. I’m currently on the fifth iteration of my experiments, which I’m currently calling Collaboration Gym. The other iterations (slightly out of order) were:

  1. Changemaker Bootcamp (2013)
  2. Collaboration Muscles & Mindsets (2014-2015)
  3. Habits of High-Performing Groups (2018-present)
  4. “Personal” Training for Organizations (2016-present)
  5. Collaboration Gym (2020-present)

I’ve failed a lot and learned a ton with each iteration, and I thought it would be fun to summarize what I’ve been learning here. I’ve also been having provocative conversations with Sarna Salzman and Freya Bradford about what a Collaboration Gym (or, in their case, a “Systems Change Dojo”) might look like in their community of Traverse City, Michigan. We’ve stayed mostly big picture so far, but recently decided that it was time to get real and specific. With their permission, I’ve decided to do my thinking out loud so as to force me to write down these scattered thoughts and also get some early feedback from a broader set of folks. That means you, dear reader! Please share your thoughts in the comments below.

Changemaker Bootcamp (2013)

The first iteration of this experiment was Changemaker Bootcamp, a face-to-face workout program that met for two hours every week for six weeks. I designed a series of exercises focused on developing muscles I considered to be critical for effective collaboration, such as listening actively, asking generative questions, navigating power, and having challenging conversations.

My participants — all of whom enrolled individually — generally found the exercises valuable and appreciated the practice-orientation. They also got along well with each other and valued the peer feedback. I designed the workouts to feel like physical workouts, only without the sweating and exhaustion. They consisted of warmups followed by intense exercises, with “just enough” explanations for why we were doing what we were doing. Most found the experiential emphasis refreshing. A few found it slightly dissatisfying. Even though they trusted me, they still wanted me to explain the why of each workout in greater detail.

These initial pilots helped me test and refine my initial set of workouts, and they also helped build my confidence. However, there were three key flaws.

  1. We weren’t repeating any of the exercises. In order to do this, I needed more of my participants’ time and I needed to focus my workouts on just a few core muscles.
  2. I needed an assessment. This would help me figure out the muscles on which to focus, and it would also help participants sense their progress.
  3. I was having trouble explaining the specific value and impact of this kind of training to people who didn’t already know and trust me.

Collaboration Muscles & Mindsets (2014-2015)

I tried to address these flaws in my next iteration, Collaboration Muscles & Mindsets. I almost tripled the length of the program from six to 16 weeks to create more space for repetition and habit-building. I created an assessment that folks would take at the beginning and at the end of the program, which helped me focus the workouts and also enabled the group to track their progress. Finally, I made it a cohort training rather than a program for individuals, which also helped with focus.

I also shifted the trainings from face-to-face to a remote, decentralized model, where I paired people up and made them responsible for scheduling their workouts on their own. After each workout, folks would share one takeaway on an online forum. This created group accountability by signaling that they were doing the workouts, but it itself was also a workout focused on muscles for sharing early and often. Every four weeks, everyone would get together for a full group workout.

Not being face-to-face meant I couldn’t (easily) do somatic workouts and that the instructions had to be clear and compelling. Not leading the pair workouts meant that I couldn’t make real-time adjustments. These constraints forced me to be more rigorous in designing and testing my workouts. In return, doing them remotely made it easier to participate and shifted agency away from me to the participants, which was in line with my desire to de-guru-fy this work.

I consistently faced early resistance from folks about the time commitment. I tried to explain that the workouts were in the context of the work that they were already doing, so they weren’t actually doing anything “extra,” but reception to this was mixed. Even though people got the metaphor around practice and working out, they didn’t have their own felt experiences around what this might look like, which made my description of the program feel abstract.

In the end, I asked participants to trust me, explaining that they would be believers after a few weeks. Most folks are hungry to talk about their work with someone who will empathize, be supportive, and offer feedback. Talking with the same person regularly enables people to get to the point faster, because their partners already know the context. Even if folks ignored my instructions entirely and just talked, I knew that they would get value out of simply having regular conversations with other good people.

This almost always turned out to be true. After the first week of workouts, folks would generally report having an excellent conversation with their partner. After about six weeks, people would often start saying that their workouts with their partners were the highlights of their week. Even though people generally had a felt sense of progress by the end of the program, they especially loved the final assessment, because they could point to and talk about the progress they had made in a concrete way.

Collaboration Muscles & Mindsets was a vast improvement over Changemaker Bootcamp, but people were still not practicing enough to see the kinds of dramatic, persistent improvement I wanted to see. I needed to focus the workouts even more and find ways to get people more repetitions.

I was also still having trouble explaining how doing these workouts would lead to the promised impacts. People understood the theory, but without felt experience, it felt too abstract. If you think about it, telling folks who are out-of-shape that they could be running a 5K in two months simply by running a little bit every day also feels abstract and far-fetched. The reason people are willing to believe this, even without felt experience, is that they know that many others have done it successfully. I probably need to get to the same place before folks truly believe the story I’m telling about collaboration muscles and practice.

Habits of High-Performing Groups (2018-present)

In 2018, I decided to shift the frame of my trainings to focus on four habits of high-performing groups:

Throughout the course of my work with groups of all shapes and sizes, I noticed that the best-performing groups do all four of these things consistently and well. These also serve as keystone habits, meaning that doing them regularly often unlocks and unleashes other important muscles and habits. Regularly trying to align around anything, for example, forces you to get better at listening, synthesizing, and working more iteratively. Only having four habits made focusing my workouts much easier.

My monthly Good Goal-Setting Peer Coaching Workshops was an attempt to help people strengthen their muscles around the first habit — aligning around success. Participants were asked to fill out a Success Spectrum before the workshop, then they got two rounds of feedback from their peers and optional feedback from me afterward. People could register for individual workshops, or they could pay for a yearly subscription that enabled them to drop into any workshop. The subscription was priced low to incentivize regular attendance.

Almost 30 percent of registrants opted for the subscription, which was wonderful. However, only 40 percent of subscribers participated in more than one workshop, even though their evaluations were positive, which meant that the majority of subscribers were essentially paying a higher fee for a single workshop. One subscriber didn’t show up to any of the trainings, which made my gym analogy even more apt.

Another subscriber attended four trainings, and watching her growth reaffirmed the value of this muscle-building approach. However, not being able to get more folks to attend more regularly — even though they had already paid for it — was a bummer.

I think I could leverage some behavioral psychology to encourage more repeat participation. One trick I’m keen to try is to have people pay a subscription fee, then give them money back every time they attend a workout. I also think cohort models, like Collaboration Muscles & Mindsets, are better at incentivizing more regular attendance.

The most negative feedback I got from these trainings was that some participants wanted more coaching from me as opposed to their peers. I designed these trainings around peer coaching as part of my ongoing effort to de-guru-fy this work. Just like working out with a buddy can be just as effective for getting into shape as working out with a personal fitness instructor, I wanted people to understand that making time to practice with anyone helps develop collaboration muscles. Still, I think there’s an opportunity to strike a better balance between peer feedback and feedback from me.

In this vein, this past year, I started offering Coaching for Collaboration Practitioners as a way to help leaders and groups develop the four habits of high-performing groups. This has been my most effective muscle-building approach to date, which makes me somewhat ambivalent. On the one hand, I’m glad that acting as a personal trainer is effective at getting people to work out. On the other hand, not everyone can afford a personal trainer. We need more gym-like practice spaces if we’re going to help folks at scale.

“Personal” Training for Organizations (2016-present)

Finally, over the past five years, I’ve been experimenting with customized organizational workouts focused on specific needs, such as strategy and equity.

I’ve found decent success at convincing potential clients to let me take a muscle-building approach toward their work. For example, rather than help a client develop a strategy, I will lead a client through a series of workouts designed to strengthen their muscles for acting strategically. Still, I often have to strike a tricky balance between more traditional consulting and this workout approach.

I’ve gotten much better at striking this balance over the years. In the early days, I tried partnering with other consultants to handle the more traditional work so that I could focus on the training. That almost always failed, especially with more established partners, because they didn’t fully get and believe in my approach, and in the struggle to find the right balance, the workouts would usually fall by the wayside.

Working by myself allowed me to be more disciplined in my approach, but I still struggled to maintain the right balance, and I failed a lot. I feel like I’ve only begun to turn the corner in the past few months. One thing that’s helped is getting much clearer about what clients need to already have in place in order for the muscle-building approach to succeed, specifically:

  • Alignment around the what, why, and how
  • Structures, mindsets, and muscles to support their work

For example, attempting to help a group develop muscles when they don’t have the right structures in place can cause more harm than good. To help demonstrate what happens when you’re missing one of these critical ingredients, I created a model inspired by the Lippitt-Knoster Model, to which Kate Wing introduced me:

Alignment Structures Mindsets Muscles = Performance
Alignment Structures Mindsets Muscles = Confusion

“Why are we doing this?!”

Alignment Structures Mindsets Muscles = Frustration

“We can’t succeed in these conditions.”

Alignment Structures Mindsets Muscles =

Resistance

“I don’t want to be doing this.”

Alignment Structures Mindsets Muscles =

Anxiety

“We’re not capable of doing this.”

Collaboration Gym and Future Iterations

I’m mostly resigned to more “personal training” work, if only to accumulate more Couch-to-5K-style success stories, so that people can develop more faith in the muscle-building approach. (If you or your organization would like to hire me for coaching or to design a custom workout program, drop me an email.) But I continue to be committed to experimenting with more scaleable and affordable approaches to muscle-building than hiring personal trainers. I’m hoping to unveil the Collaboration Gym early next year, and I’ve already successfully piloted a number of new workouts that will be part of it.

Epic success for me is to see others participate in similar experiments on their own and to share what they learn. A Collaboration Gym is only useful if there are lots of gyms all over the place. I give away all of my intellectual property so that others can copy and build on it, and I will continue to share my learnings here to further encourage replication.

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?

Repetition Is the Key to Learning

de Young Museum Observation Tower Grating

Todd Pierce, a former client of mine, loves to say, “Repetition is the key to learning.” I thought I understood this already before I first heard him say it, but watching him model it made me realize otherwise. He said it so often, it became engrained in my head. I find myself repeating it often, and whenever I do, I think of him. Apparently, it works!

Repetition is the key to learning.

Learning is hard. It’s easy to hear things, to believe them, and to even say them to others. It’s hard to do them, to put those beliefs into action, to live those beliefs.

Repetition is the key to learning.

The challenge with most group work is that everybody in the group needs to own the results. Goals, for example, aren’t useful if no one can remember what they are. My main tool for addressing this challenge is to make sure that everybody plays a role in creating those goals. If you make it, you’re more likely to remember it.

This is true, but it’s not necessarily enough.

At my previous company, we had an extensive conversation about our organizational values, and we co-created a list of six. About a month later, I was troubled. I couldn’t remember what those values were. I was the leader of the company, and these were supposed to embody our organizational identity, and yet I couldn’t name them all. I asked my business partner if she could list them. She couldn’t do it either. Only our associate, who had facilitated the process, could remember all six.

We had a followup conversation, and we decided that we still believed that list represented what we were about. We just needed to remind ourselves what they were. We tried different things. We listed the values on the front page of our internal wiki. We encouraged everybody at our weekly checkins to share a story that embodied one of those values. Every so often, I would simply ask people to name the values. Some of these practices worked, others didn’t, but we were persistent. Over time, we all knew those values by heart.

I left my company a little over a year ago. Just now, I tried to name all six. I could only remember four.

Repetition is the key to learning.

I’m particularly proud of Changemaker Bootcamp’s three ground rules:

  • Be nice to others
  • Be nice to yourself
  • Don’t be nice

I love how simple and provocative they are. I find myself referring to them often, not just in bootcamp, but in all my work. There are only three, and they are such a big part of bootcamp culture, they’re even on the T-shirts.

In the past few weeks, I’ve had conversations with two past bootcampers where the ground rules came up. Neither of them could remember what they were. Both of them seemed embarrassed, but they shouldn’t have been. I realized that I could be doing even more to make sure people remembered them — simple things like reviewing them at the beginning of all of our sessions, not just the first, and having them up on the wall for all of our sessions.

The ground rules came up with one of my bootcampers, because she was telling me that she did not always feel like she had permission to speak up. I gently reminded her of our third ground rule — “don’t be nice” — which she had forgotten. Maybe the ground rule alone wouldn’t have corrected the problem, but it would have helped.

Repetition is the key to learning.

A big part of my work has been about designing and facilitating meetings where people have powerful learning experiences. I’m pretty good at it, as are many of my colleagues. But those experiences are of limited value if the lessons from those meetings are not constantly reinforced afterward. Designing great collaborative engagements requires thinking beyond meetings — figuring out ways to continue and to reinforce learning.

The way to do this is through repetition. That repetition can come in many different forms, but it needs to happen.

Repetition is the key to learning. It’s a message that bears repeating.