Intergenerational Spaces Benefit Everyone

A few weeks ago, my Winter cohort of Power and Love for Managers had its final session in Oakland. We closed the training with appreciations, and one participant said how much she valued being in an “intentionally intergenerational space.” That comment struck a chord for me. It was an accurate description, but I had framed my goals around diversity more generally and around experience rather than age. I’ve been pondering why I haven’t been more explicit about bridging generations in my work, when it’s been an important value for me from the beginning.

I started going down this professional path in 2002 when I was 27. The early days were rough, mainly because the economy was bad and I didn’t have a track record, at least not the kind most people were looking for. The professional field was also small and mostly ill-defined. Saying I was a “collaboration consultant” drew blank stares. There were a few similar job titles, such as leadership and organizational development consultants and facilitators, and although there was plenty of overlap, none of those things described exactly what I was trying to do or how I was trying to do it.

It was a struggle simply to survive the first few years, and I could not have done so without many mentors, including Doug Engelbart, Jeff Conklin, Gail and Matt Taylor, and many others. They were generous and encouraging, but they also didn’t treat me as a charity case. They valued my experiences and how I thought about the world and the work, and they wanted to learn from me as much as they wanted to support me.

These early experiences strongly influenced my theory of change as well as my personal practice. I knew what my mentors had meant to me, and I wanted to pay it forward. But I also recognized that we wouldn’t see better collaboration at a planetary-scale without many, many more skilled practitioners. Unfortunately, many who are drawn to this practice (often women and people of color) feel isolated and invisible. We don’t realize that trying to help groups collaborate more effectively is a “thing,” and that there are many others who are doing the same.

If we could make the practice more visible and connected, we would all benefit. This would also mean making it easier for new people to enter the field, not just by sharing wisdom, but by creating professional opportunities where people could make a living while honing their craft. If the path to doing this work professionally is as hard as it was for me when I was younger, it will deter folks we badly need.

Throughout my career, I’ve done my best to build the field through my work. I hire associates on as many projects as I can. Their roles are largely operational, not because senior practitioners are above this work (everybody on my teams “work the line”), but because I want them to value the importance of doing logistics well.

Associates are also part of the design team, which means they are in most of the meetings I have with clients. I encourage them to speak up in those meetings, explaining that there is no mistake they can make that I can’t fix and that I will be more upset if they withhold an important observation or insight.

Because I revoke all of my intellectual property, people who work with me are free to integrate any of our tools and practices into their own work without worrying about fees or credit. I also pay associates more than market rate, because I’ve realized that your previous paycheck has an outsized impact on how future clients see you and how much they’re willing to pay you, especially when you’re young.

I’ve tried to encourage my peers to adopt some of these practices, with mixed success. More than a few colleagues have told me, “I don’t have time to train younger practitioners.” My experience with associates is that any time I invest in my them comes back to me in spades. They add a useful dose of perspective, and they provide backup in case others have to step away. They also inject energy and joy into the work, and they bring their own unique skills and perspectives, providing the rest of the team fresh opportunities to learn.

More recently, as I’ve tried to shift more of my focus on training, I’ve had fewer opportunities to hire associates. I’ve tried to make up for this by making my trainings free to folks who are 26 years old or under.

Despite my emphasis on supporting less experienced practitioners, until recently, I didn’t think of myself as an “older” practitioner. I think what’s different now — besides turning 50 last year — is that many of the kids in my life are now young adults. Before, I didn’t really look at people in their 20s much differently than I looked at myself. Sure, I was older, but they were essentially still peers. Now, I can’t help seeing them and thinking, “Wow, that person is the same age as my nephew!”

I’m also acutely aware of how different the world is now from what it was a quarter century ago — darker, more volatile, more uncertain. I can only imagine what it must be like to have to face this as a 20-year old, and I feel a greater responsibility to support them. It was so much easier when I could just blame the Boomers!

Fortunately, the benefits of being in intergenerational spaces are bidirectional. In this month’s Staying Strategic workouts at my Collaboration Gym, I had two people in their 20s participate. They also happened to be children of friends and colleagues, one of whom I’ve known since he was 10. I loved having them. They were thoughtful, earnest, vulnerable, eager to learn and engage, but also willing to contribute. The energy was different with them in the room, and I could see how much everyone else loved working out with them. The same was true with my Winter cohort of Power and Love for Managers, where a third of our participants were in their 20s.

Being around younger practitioners lifts my mood, challenges my thinking, and gives me hope. If they are this smart, this curious, this good, then we have a fighting chance to make things better in this world. It behooves the rest of us to do whatever we can to help them. Intentionally creating and being in intergenerational spaces is a great way to do this.

Photo by Zoha Raza.

Remembering Gail Taylor

I’ve now officially been in the collaboration business for 23 years. Thinking out loud has been an important ethic from day one, and I managed to blog regularly about my work for the first 18 of these years. Then the pandemic happened, and I essentially took a four year break from thinking out loud. I was still working and learning and wondering. I just stopped writing. It wasn’t a conscious decision. I was just exhausted.

Earlier this year, I felt ready to write again. The world had changed dramatically, I had grown a lot, and I had learned things I wanted to share more broadly. But simply picking up where I had left off didn’t seem right. Given the social mission of my work, I didn’t feel like I could just suddenly appear after four years and share an observation about organizational power dynamics that I had observed in a client project without first saying something about the state of the world.

Several months later, I published “Good Energy,” the longest and most personal piece I had ever published on a professional space. I followed it last month with “Foraging for Ginseng,” another intensely personal essay. I’m almost ready to return to my regularly scheduled programming, but there’s one more personal professional piece I need to share.

On November 5, 2023, my friend and mentor, Gail Taylor, passed away. She was 83 years old, still playing, still working literally until the very end.

Gail and her husband, Matt, were instrumental in my growth as a practitioner. I first got to work with her in 2003, just as I was embarking on my first professional attempt at helping folks collaborate more effectively together. I was in my late 20s, and even though my resume didn’t reflect it, I felt irrationally qualified to do this work. In particular, I was steeped in the wonders of open source software development and early wiki communities, where people all over the world would come together and build sophisticated, complex systems together without ever having met in person. I had first-hand knowledge of the power and beauty of large-scale, open, participatory processes in largely virtual spaces, and I wanted to apply what I had learned to other groups.

What I was missing was experience, especially with large, in-person groups. At some level, this translated into designing and facilitating good meetings, especially large ones, but that was not my primary interest. I cared about systems as a whole. Collaboration doesn’t just happen in meetings.

Thanks to Gail and Matt, I didn’t have to figure this out on my own. Gail had just left MG Taylor, the company she and Matt had founded 20 years earlier. They were best known for their DesignShops, three-day, immersive gatherings where large groups could come together and tackle hard stuff. They had built large environments with their own furniture designed to maximize exploration, serendipity, alignment, and joy. They were already doing amazing work, but Gail wanted more. She wanted to spend more time experimenting and working with different kinds of groups, not just large companies.

Gail had the gentle, loving ferocity of the best kindergarten teacher you ever had. Not surprisingly, that’s how she got her start — teaching kids. She had a curiosity for learning and a passion for play that I think all children (and adults) relate and respond to, and she had an egalitarian energy that made you feel like she was your partner, not your authority, even when she was standing in front of the room. She also had a quiet power and presence that made you sit up at attention when it was time to get to work.

Gail completely shifted my view of what facilitation was. She helped me realize that facilitation was a leadership practice, not a position, and that everyone in the system played that role, even if you were the “official” facilitator in the moment. Recognizing your role as part of the system (as opposed to being outside of it) not only made you more effective as a facilitator, it made it less stressful, because it got you out of the “heroic leader” mindset. The whole system was holding the space, not just you.

Moreover, working with Gail made me see my role more as a systems designer than as a facilitator. You had way more power to shift the dynamics of a group by changing the physical environment — from how you arranged the chairs to the light and design of the space itself — or by carefully designing process than you did by just being a good facilitator. This didn’t just apply to meetings, it applied to every aspect of work.

All of this came intuitively to Gail. She loved teaching kindergarteners, but she thought that traditional institutions and pedagogy were at odds with their purpose of creating great learning environments for children. She continued to experiment, ultimately creating her own educational institution in Kansas City with her own approaches to learning, complete with custom furniture made of tri-wall cardboard. (If you’ve ever experienced any of my meetings with cardboard boxes, that trick came directly from Gail.)

As she saw what worked with kids, she wondered why the same principles couldn’t work with adults. That question led to her meeting Matt, and as they continued to learn together, they started pulling out principles of good system design. The more they played, the more people started recognizing their success, which gave them bigger and more complex opportunities to play. That included training and building a whole community of practitioners and an ecosystem in which they could thrive. They literally created job titles and descriptions that had never existed before and taught clients to seek folks to fill these roles, which helped sustain and grow the community.

While I was inspired by this community and consider many of its members close friends and colleagues, I never felt like I quite fit into this group as a whole. I felt like some of the practitioners in that community didn’t quite understand Gail and Matt’s core principles, and I was hungry to experiment and build on my own ideas and experiences. Gail not only understood this about me, she embraced and encouraged me, and she and Matt made me feel like I was part of the family anyway.

I learned many tangible things from Gail over the years, but the biggest impact she had on me was normalizing, “Why not?” I’m not afraid of following my instincts or my curiosity, to try things that might be outside of a group’s comfort level. I’m not afraid, because Gail was not afraid. Because I experienced this with her so early in my career, that became my norm. It took me many years before realizing what a huge gift that was.

I am so, so grateful for everything I learned from her, but more than anything, I am grateful for her guidance and her friendship. Spending a few days with her up in her then-home off the Mendocino Coast was a guaranteed salve when I was struggling or stuck. Here’s a little video I took of her on one of our walks back in 2011. The content of the conversation is somewhat representative of what we often discussed, but the vibe — the calm, the comfort, the wisdom — perfectly captures what it was like for me to be around Gail.

I last saw Gail in 2018. I was coming off an intense three-year project that had ended poorly, and I badly needed solace and wisdom. As always, time with them was both healing and inspiring. A few years later, they decided to move back to Kansas City. Other than exchanging some emails, I never got a chance to see Gail again, a fact that continues to pain me.

Gail was a prolific journaler. At her memorial in Kansas City last year, her son, Todd Johnston (not surprisingly another great practitioner), read this excerpt from one of her recent journals.

It was an exploration of her multifaceted identity, and it ended with the following statement:

Today I claim my self as a seeder… planting seed through all of my conversations — seeds that will grow and become strong over time. Oak trees.

I feel lucky to be one of her trees, still developing, but with a solid root system.

After the memorial, I rescued a small vase with three frogs from her. Todd explained that she used to like to place her animal-laden tchotchkes close to each other so that they could have conversations with each other. The vase now sits on my desk. I don’t facilitate meetings as much as I used to, but when I do, I always bring the vase with me, sometimes garnished with something from my garden, so that a little piece of her is there too, helping me and everyone else hold the space.

The Art of Thinking Really, Really Big

What does it mean to be driven by vision?

It’s easy to know what you’re against, what you dislike, what you don’t want. But what are you for? What do you love? What is the world that you want to create?

How do you stay inspired in the face of a stark reality? How do you inspire others?

Last year, I made it a priority to articulate the most important principles for helping groups achieve higher performance. I decided to start this weighty task by writing down everything I learned from my most influential mentors and colleagues. (I would highly recommend this exercise to everyone. It’s a great reminder of who you are and what you believe as well as of how lucky you are to have these special people in your life.)

One thing that stood out for me was how BIG my mentors’ and colleagues’ visions were and how much of an influence that’s had on me and my practice. While I constantly preach the importance of intentionality, I’ve spent far less time talking and thinking about the art and practice of visioning, especially as it pertains to other groups.

The one exception to this speaks to what my perspective used to be and how it’s starting to shift. Two years ago, I wrote a blog post entitled, “Rubber Bands and the Art of Visioning.” While I made reference to some of the really big vision that’s shaped who I am and how I practice, my emphasis for others was less on stretching your vision and more on grounding it, which is where many processes fall short. One of my mentors, Gail Taylor, left a comment challenging me on this point:

Ahhh, the creative tension! Rubber bands are a nice metaphor, stretch too far and the darn thing snaps! But, I have found most people under stretch but if they are willing to go to the edge they reach further and never quite shrink to their former state.

I’ve thought often about Gail’s words. For the past two years, I’ve been working with an inspiring group of social change leaders who are struggling with how to make their vision real. It’s a complex project, with many challenging nuances and not-so-subtle obstacles, but I’ve come to the conclusion that this group is stuck because its vision, while ambitious, is still too small and too cloudy and because it hasn’t figured out how to integrate that vision into its every day work.

Moreover, I have become convinced that this is fundamentally the challenge that ails this country and perhaps the world right now.

My job is to help these leaders get unstuck, to help them get better at the art and science of visioning, of fostering radical hope in a grounded, rigorous way. I’m not sure how to do this, but we’re going to try some things this year, and I’ll do my best to share what we learn. Maybe there will be something there that’s applicable beyond this group.

Last August, I was in the beautiful Michigan wilderness facilitating a retreat for another group of social change leaders. Internet access and cell phone coverage were spotty, so it took us awhile to learn about the hate-filled, white supremacy rally at Charlottesville and the tragedy that ensued. I felt fortunate to be able to process and mourn among such incredible leaders, but upon leaving the retreat a few days later, I felt depressed and demoralized.

As it happened, my next destination was Toledo, Ohio to spend a few days with one of my best friends. Our original plan was to spend a day in Detroit, but as soon as I arrived, my friend asked me if I wanted to go to a rally instead. The white supremacist who had rammed his car into counter protestors in Charlottesville was from nearby Maumee, and organizers were planning a march against hate there that afternoon.

I said yes immediately. It felt like fate that I was there when I was, and I thought it would be cathartic. But I still felt unsettled and nervous.

As we drove to Maumee, we listened to old Martin Luther King, Jr. speeches. (They’re available for free on Spotify.) I found them mesmerizing. Other than his famous, “I have a dream” speech, I had never heard him speak. I was particularly struck by his 1961 commencement speech at Lincoln University, which begins:

As you go out today to enter the clamorous highways of life, I should like to discuss with you some aspects of the American dream: For in a real sense, America is essentially a dream, a dream as yet unfulfilled. It is a dream of a land where men of all races, of all nationalities, and of all creeds can live together as brothers. The substance of the dream is expressed in these sublime words, words lifted to cosmic proportions: “We hold these truths to be self-evident — that all men are created equal; that they are endowed by their Creator with certain inalienable rights; that among these are life, liberty, and the pursuit of happiness.” This is the dream.

…

Very seldom if ever in the history of the world has a socio-political document expressed in such profoundly eloquent and unequivocal language the dignity and the worth of human personality. The American dream reminds us that every man is heir to the legacy of worthiness.

Listening to it settled me down, and I haven’t been able to forget the impact his words and his voice had on me that day.

I’ve kicked off 2018 thinking about what I’m trying to learn about visioning for this project, for myself, and for the world, and I decided to listen to this speech again, both to reflect on Dr. King’s craft and to find inspiration anew. It’s been working for me, and I hope it works for you as well. Happy New Year!

Coming out of Retirement

Looking Forward

I’m coming out of retirement.

When I left my consulting firm three years ago, I had a simple premise that I wanted to test: Anyone could get good at collaboration with enough practice.

I wanted to test this hypothesis aggressively and honestly, and I wanted to challenge every assumption I had about how best to do this work. In order to help others solve their own collaboration problems, I had to stop designing and facilitating custom processes for them, and instead focus on how to help them develop their own skills. I often had trouble explaining what I was doing and how it was different from my previous work, so I just told people that I was retired.

Retirement was fun and generative, but hard. Challenging my assumptions at times felt like my identity was unraveling, which was humbling and emotionally taxing. Moreover, few — even close colleagues — understood what I was trying to do.

Still, it was worth it. I am both a better practitioner and a better person. I learned an amazing amount, and I think I can have a much bigger impact on the world as a result. I’m excited to continue to build on what I’ve learned, and I have a growing community of practitioners who are also engaged with the work I’ve been doing. I also love the life balance I was able to achieve over the past three years, and I’m not about to give that up.

So why am I coming out of retirement?

One of my primary points of emphasis these past three years has been around field-building. When I decided I wanted to devote myself to collaboration professionally over a dozen years ago, I had amazing mentors who were incredibly generous with me.

Furthermore, no one expected anything of me, which was good, because I didn’t know anything. I spent my first four years trying stuff and failing, trying stuff and failing. I was able to come into my own on my own, which was an incredible luxury, and by the time I retired at the end of 2012, I felt like I was at the top of my profession.

My path was fruitful, but challenging. I made it because I was passionate, persistent, and very, very lucky. It was a good path for me, but if it’s the only path for people who care as much about collaboration as I do, we’re not going to have many people in our field.

For several years now, I’ve done whatever I could to make that path easier for anyone who was hungry and committed to learning, from sharing all of my templates to providing professional opportunities to promising practitioners. I’ve been able to help a lot of people simply by making time to talk with and encourage them.

However, at the end of the day, the best way to learn is to do the work, to try stuff and to fail over and over again. Before I “retired,” I was able to create safe opportunities for others to do exactly that by inviting them to work with me on real projects.

Those who shadowed me were able to see how I thought about problems and how my ideas manifested themselves in practice. They were able to experience and develop good preparation habits. They were able to practice on real problems without fear of failing, because I could act as their safety net.

Most importantly, they could watch me fail and understand that failing is simply part of the process, that we all do it, and that there is an art to doing it gracefully and successfully.

When I retired, I lost this platform. I was focused entirely on capacity-building, and while I could share stories and advice, I couldn’t show people how I approached process design and facilitation, because I wasn’t doing that work anymore.

This alone wasn’t reason enough to unretire. I know many great practitioners in this space, and I referred people to those who were willing to open up their work practices. I also devoted a lot of my own time to shadow these peers myself for my own learning.

While I learned quite a bit from shadowing, I was extremely disappointed overall by the quality of work I was seeing from some of the most well-respected people in this field. The standard for what it means to do this work well is very low, and it seems that many good practitioners are simply hopping over this bar, which they can do easily.

The problem is that simply clearing the bar does not lead to high performance. If we want to live in a world that is more alive, if we want to address the challenging, urgent problems that we all face, then we, as practitioners, need to raise the bar, not just clear it.

There were exceptions to my shadowing experiences. They tended not to be consultants, but rather people who were embedded in organizations, often younger practitioners who had skin in the game and a hunger to learn. I saw some excellent work from these practitioners, most of whom are largely invisible both in their organizations and in this larger field of collaborative practitioners.

Furthermore, even though I stopped designing and facilitating processes for hire, I actually got better at it during my retirement. I have a much greater understanding for how to integrate capacity-building into my processes, and I can design interventions that are more scalable and sustainable as a result. Also, because I’ve been doing my own workouts (as well as leading them for others), my own collaboration muscles have simply gotten stronger.

I wrote previously about how we need chefs, not recipes. In order to inspire great cooking, people need to taste great meals. I’m hungry to show what’s possible by taking on problems that are hard and meaningful. I want to raise the bar, and I want to do it in a way so that others can learn with me.

I’m still prioritizing my capacity-buiding efforts. I have more programs to offer and more things to give away. I am convinced that these are levers that have the best chance at improving our abilities to collaborate at scale.

At the same time, I’m open to taking on consulting work again. I will be extremely selective, and I will only take on one project at a time. I’ll use these projects as a way to model best practices and as a platform where other practitioners can learn with me. As it so happens, I already have a project, which I’m excited to share more about soon.

Chefs, Not Recipes: The Tyranny of Tools and Best Practices

Cooking

One of my favorite sayings is, “Chefs, not recipes.” It’s a phrase that I stole from Dave Snowden, and it perfectly encapsulates the approach I think we need to take (and aren’t) in the collaboration, networks, and organizational development space. I believe in this so strongly that I had it engraved on the back of my phone.

What exactly does this mean, and why do I find it so important?

One of the reasons I got into this field was that, over a dozen years ago, I experienced exceptional collaboration in open source software development communities, and I wondered whether similar things were happening in other places. If they were, I wanted to learn about them. If they weren’t, I wanted to share what I knew. I thought that developing shared language around common patterns could help groups achieve high-performance.

I still believe that a good pattern language would be useful, and there’s been some interesting movement in this direction — particularly Group Works and Liberating Structures. (Hat tip to Nancy White for pushing me to explore the latter.) However, I think that there’s a much bigger problem that needs to be addressed before a pattern language can become truly useful.

Collaborating effectively is craft, not science. There are common patterns underlying any successful collaboration, but there is no one way to do it well. It is too context-dependent, and there are too many variables. Even if best practices might be applicable in other contexts, most of us do not have the literacy to implement or adapt them effectively. We think we lack knowledge or tools, but what we actually lack is practice.

I’m a pretty good cook, but I still remember what it was like to be bad at it. I first tried my hand at cooking in college, and I was so intimidated, even simple recipes like “boil pasta, add jarred sauce” flummoxed me. I was so incompetent, a friend mailed me a box of Rice-A-Roni all the way from the other side of the country because she was afraid I would starve.

Back then, I followed recipes to the letter. I had no way of evaluating whether a recipe was good or bad, and if it turned out badly, I didn’t know how to make adjustments. I ended up defaulting to the same few dishes over and over again, which meant that I got better quickly, but I also plateaued quickly.

A few things got me over the hump. I had lots of friends who cooked well. I relied on them for guidance, and I especially enjoyed cooking with them, which allowed me to see them in action and also get feedback. But the turning point for me was challenging two of my less experienced friends to an omelette competition. (I suppose that speaks to another thing that helped, which was that I was brash even in the face of my incompetence.)

I cooked omelettes the way my parents cooked them and the way I assumed everyone else cooked them. But both of my friends cooked them differently, and I liked all three versions. The differences in approaches were more subtle than what was usually captured in a recipe, but the differences in results were clear.

That experience made me curious about my assumptions. Most importantly, it got me asking “why.” Why do things a certain way? What would happen if I did it differently? I also stopped using recipes, choosing instead to watch lots of cooking shows, cook with others (including people who worked in kitchens or were professionally trained), and experiment on my own. Recipes were a helpful starting point, but they were not helpful beyond that. While better knives and pans improved my ability to execute, they did not make me a better cook.

Recipes and tools have their place, but they are relatively meaningless without the literacy to wield and interpret them. Practice, experimentation, mentorship, constantly asking “why” — these are the keys to mastering any craft. This was my experience learning how to cook, and it’s also been my experience learning how to design and facilitate collaborative engagements.

What does approaching collaborative work as a chef as opposed to a set of recipes look like? It starts with asking “why” about everything. For example, if you’re designing and facilitating a face-to-face meeting:

  • What are your goals, and why?
  • How are you framing them to participants, and why?
  • How are you arranging your space, and why?
  • When are you breaking up your group, and why (or why not)?
  • What kind of markers are you using, and why?
  • Why are you having a face-to-face meeting at all?

I meet a remarkable number of practitioners — even ones with lots of experience — who can’t answer these questions. They’re simply following recipes.

Even if you have answers to all of these questions, don’t assume that your answers are the best ones. Experiment and explore constantly. Shadow other practitioners, especially those who approach their work differently. Intentionally do the opposite of what you might normally do as a way of testing your assumptions.

Finally, if you are a more experienced practitioner, remember that in professional kitchens, chefs have a supporting cast — sous chefs, line cooks, prep cooks, and so forth. If you yourself are not regularly working with a team, you’re not optimizing your impact. Most importantly, find a way to mentor others. Not only is it a gratifying experience, you’ll find that the learning goes both ways.

Photo by yassan-yukky. CC BY-NC.