People Matter

I spent the day processing everything that’s been happening over the past week, work-wise:

  • I spent two days at the Network of Network Funders meeting, thinking with and listening to a group of funders who are trying to apply network-thinking in the nonprofit space
  • I also spent a lot of time on my primary project these days, helping a Fortune 500 company understand how it can improve how it collaborates at a global scale

Here’s the irony:

  • The funders are thinking in terms of networks, but they’re struggling to let go of a more traditional organizational mindset
  • Meanwhile, the CIO of this company (the sponsor of our work) is thinking in terms of his organization, but his mindset and actions are all “post-organizational.” He has a very network-oriented approach in how he’s leading his organization, but he’s not mired in the language and complexity of networks

I’m working with Kristin Cobble on this project, and she had a similar take on our client, but entirely different language. She described him as “an organization learning consultant’s dream client.”

We discussed how we came to a similar conclusion through our different lenses and language. And what we decided was this: Call it whatever you want — organizational learning, networks, whatever. At the end of the day, it all boils down to the same thing: People and practice.

Grady McGonagill and I have an ongoing argument about paradigms. He thinks that the way the world is now — rapid, technology-induced change and an exponential rise in complexity — requires a new paradigm of leadership. It makes sense on the surface, but I disagree. I think the old paradigms of leadership are fine. We just need to be more intentional in practicing them.

This, to me, is the timeless paradigm in which we now — and have always — lived:

  • Trust matters
  • Relationships matter
  • Communication matters
  • Reciprocity matters
  • Space matters
  • Learning matters
  • Practice matters — way, way more than process
  • Feeling alive matters

If we just stripped away our tools and processes and frameworks and crazy language and simply focused on practicing everything on this list, the world would be a much better place.

Quick Thoughts from the Network Funders Gathering, Day 1

Yesterday was the first day of the Network of Network Funders gathering. It was my kind of gathering — great crowd, thoughtful conversations, strong design (a Diana Scearce staple), incredible stories.

Wanted to share three observations from yesterday:

Holding the tension. Working with networks from a position of traditional, institutional power is a tricky business. But doing it successfully is not about giving or wishing away that power. It’s about holding all the different tensions in balance: sharing control without losing it entirely, using your power to empower others, being open without putting your network at risk.

Fight the organizational mindset. The natural challenge for folks from foundations is fighting an organizational mindset. Folks here are doing pretty well, and they can do better. Focus on verbs, not nouns — network weaving vs network weavers, governing vs governance.

Own your power! There’s a psychological phenomenon known as the Dunning-Kruger effect. In short, people who are incompetent tend to overestimate their abilities; people who are highly competent tend to underestimate their abilities. Dunning-Kruger (the good kind) is rampant here.

The people in this room are really, really smart and well-versed in practice — moreso than many consultants I know. They need to step out of the mindset that they are only funders and step into their roles as thought leaders and action partners. Don’t pretend away the power dynamic. It will always be there. Channel it by sharing your knowledge in partnership with other stakeholders with humility, and continuing to do and to learn.

You can follow today’s conversation on Twitter by following the #netfunders hashtag.

Strategic vs Tactical Philanthropy

The best thing I read this week was Sean Stannard-Stockton‘s blog post, “An Investment Approach to Philanthropy.” In it, he articulated a favorite theme of his — strategic versus tactical philanthropy — in a way that felt very clear to me.

Here’s my two line summary:

  • Strategic philanthropy is about trying to solve social problems
  • Tactical philanthropy is about investing in organizations trying to solve social problems

Sean was trying to articulate the difference between the two approaches without passing a value judgement, a tough proposition considering the name of his blog — “Tactical Philanthropy.” I think many of the folks who commented on his post got caught up in that, which is too bad, because they’re missing out on a very provocative question:

Is it possible to do both effectively?

Sean states that the competencies required to do these things are very different, and he suggests that it is very hard (but not necessarily impossible) to do both effectively. I’m not sure why people would find this such a troubling proposition. It seems to me that this insight helps unravel a number of fundamental tensions that institutional philanthropy often faces.

One of those is around leadership. Foundations want to empower other leaders, but in doing so — through convenings, through research, through hiring very smart people — they often become leaders themselves. What follows is this awkward dance where foundations either avoid exerting their own leadership for fear of overpowering those they’re trying to empower, or they exert their leadership too strongly, unintentionally reinforcing a power dynamic that is very hard to circumvent.

Choosing to focus on either strategic or tactical philanthropy, but not both, could potentially resolve these tensions. For example, a funder could decide to focus exclusively on creating systemic, network-oriented change by funding convenings and research and not investing in organizations. That would allow those foundations to establish more open, authentic partnerships with people who might otherwise be depending on those same foundations for their livelihood and are behaving accordingly.

The Networked Nonprofit Board

I’ve served on the board of the Leadership Learning Community (LLC) for four years now, and I recently became the board chair. The thing I love most about LLC is how it models its principles. It doesn’t just talk about how leadership should be. It practices it, and it shares its learnings, both good and bad.

Deborah Meehan, LLC’s founder and Executive Director, recently wrote a blog post about our most recent board meeting, where we spent an afternoon thinking about what it would mean to the board if LLC were a more networked nonprofit.

Of course, simply talking about the idea among ourselves would have been interesting, but not as gratifying. Instead, we modeled the idea by inviting guests to think with us. (Beth Kanter, one of our guests, reposted Deborah’s post on her blog.) Even though I and other board members (notably Grady McGonagill) spend a lot of time thinking about networks, the truth is that the LLC staff deserves all the credit for moving us forward in this way.

At the end of her post, Deborah tells an anecdote about me, which I’ve heard her share often:

Two years ago, when we extended an invitation to our community to join the design team for our national meeting over 20 people responded and our board chair, Eugene Eric Kim, had the radical idea about selecting the team, take everyone! Well, that would be an interesting approach to board recruitment wouldn’t it?

She always refers to this idea as “radical,” which always amuses me. What was so radical about it? Organizing a national meeting is super hard, so why would you turn down help? The more the merrier, right?

Those who answer “no” are generally designing for the worst case scenario. If your group is too large, you might get sidetracked. You don’t want to accept a bad seed. Etc.

These are all valid concerns, but designing for the best case scenario is equally valid. You can do more work with more hands. The larger the group, the more likely you are to attract a diamond in the rough. Etc.

I prefer to design for the best case scenario, but I’m no pollyanna. I’ve seen processes get hijacked, even by people with the best of intentions. If you’re going to design for the best case scenario, you want favorable conditions. In my experience, you want the following:

  • Crystal clear goals
  • A strong core group of committed, facilitative individuals
  • A strong network with shared language

If you have these three things, you should be designing for the best case scenario, not the worst. In the case of the Creating Space conference two years ago, we had all three:

  • People knew exactly what the conference was about and what organizing it would entail. It was the ninth time LLC was organizing this conference, so there was plenty of experience
  • The LLC staff was fully committed, and it had hired one of the best facilitators in the business, Odin Zackman (who also attended our board discussion on networks). There were also a few committed, experienced volunteers we knew we could count on, regardless of who else ended up volunteering
  • As its name suggests, LLC’s biggest asset is its diverse community, which is full of brilliant people who are strongly aligned around its values and who have fostered strong relationships and shared language with each other over the years

Like I said, given these circumstances, the idea of accepting everyone who wanted to participate didn’t seem too radical to me.

How can we apply this thinking to boards on a networked nonprofit?

There are obvious places where this applies, and there are places where it’s extremely challenging. The obvious possibilities center around leveraging domain expertise. For example, nonprofits often choose board members who bring specialized knowledge in certain areas, such as finance, fundraising, or technology. In this capacity, board members are acting as advisors, but also network weavers — people who connect the organization to their networks. There’s no reason why you couldn’t open up this role to anyone in the network who was willing to play it.

The biggest challenge centers around governance. Nonprofit boards typically have fiduciary and oversight responsibility. How would you handle this in a more networked way? Network-oriented organizations (membership networks, for example) generally approach this by making some number of their board seats elected positions.

I think a more radical shift is possible. Jack Ricchiuto’s essay on going beyond consensus beautifully describes how to move from planning to activation. I believe there’s a model that builds on this thinking, delegating as much as possible to small groups, with the board acting as weavers.

That all sounds well and good, but the devil is in the details. I don’t know what that model looks like, and I realize that there are some huge obstacles, including some legal ones, that make this very challenging.

Technically, as Deborah notes in her post, LLC does not have this problem. It’s a project of the Tides Center, which means that our board is technically an advisory board, even though we operate as an oversight board. This gives us a bit more leeway to play.

And play we will! At the end of the day, we won’t get to the answer by sitting in a room and thinking really hard. We’ll get there by staying clear about the overall goal, taking small, concrete steps, and repeating the cycle, failing early and often.

Somatic Computing

A few months ago, I sat down to a meeting with Kristin Cobble, Gwen Gordon, and Rebecca Petzel. We were all on our laptops, pulling up notes and sending off last minute emails. As the meeting was about to start, we all closed our laptops with a deep breath, looked at each other for a moment, then burst out laughing.

We had all noticed the same thing at the same time, and we had communicated that to each other nonverbally. Closing our laptops had completely shifted the energy of the room.

Space matters. It affects our bodies and their relations with the things around them, and there is wisdom and energy inherent in that.

Most of our interfaces with digital tools were not invented with our bodies in mind. They were created to serve machines, and for the most part, they haven’t evolved much. We’re starting to see that shift now, with mobile devices, with touch, and with gestural interfaces. When our technology starts to augment our body’s natural wisdom, we are going to see a huge shift in its power.

My friend, Anselm Hook, gave a great talk at AR Devcamp last year, where he explored the notion of developing software somatically (what he’s calling the “Slow Code movement”):

The technology we need to build these sorts of interfaces exist today, and I think we’ll see an inflection point soon. But that inflection point won’t come because of enterprise-driven markets, despite the opportunity that these interfaces hold. Those markets simply aren’t big enough. It will come because of games.

This is no great insight, but I think that many of us are remarkably blind to it, and it’s worth reminding ourselves of this over and over again. It’s no accident that Kinect — one of the most remarkable and successful research-driven products for personal computing — came out of Microsoft’s Xbox 360 group and not one of its other divisions.