Networks and Pickup Basketball

When I read about or listen to others talking about networks, I often find the examples people cite to be too narrow. They’re either Internet-mediated networks (which are interesting) or organizational networks (which are not). I wish that more people would consider things that look like the intersection of the two — networks that look similar to the Internet, but are not primarily mediated by the Internet.

One of my favorite examples of this also happens to be one of my passions: pickup basketball — casual, just-for-fun (but sometimes highly competitive) games that anyone can start or join. Not all games are open, but most of them are. You can find a pickup game pretty much anywhere in the world, and you’ll find that the rules and norms — mostly unwritten — are almost identical, with some common variations. Half court or full? Ones-and-twos or twos-and-threes? Winner takes ball? Win, you’re in?

Still, each game is made up of different people, and as such, has its own culture and practices. Some games are unapologetically meritocratic — as long as you win, you stay on the court. Other games are more inclusive — if you win two games in a row, you sit and let others play. In my game, we stop play when someone falls. There was never any up-front agreement about this. Someone started doing it in the early days, and it was highly appreciated by the older players (i.e. me).

I’ve had many regular pickup games over the years, some of which I’ve started, some of which I’ve joined. In some cases, I accidentally stumbled upon them and just kept showing up. In other cases, people would add me to their mailing lists or online forums.

One of my favorite organizing models was a game a colleague invited me to join in Menlo Park in the early 2000s. We generally played on Tuesdays and Thursdays during lunch. Someone had set up a mailing list, and on the morning of, someone — it could be anyone — would send an email to the list with the number, “1.” That meant they wanted to play. If you were up for joining, you would respond to the list and increment the number. In other words, the next person would respond, “2,” the next would respond, “3,” and so forth. If you hit, “4,” you had enough to play, and the game would officially be on.

I currently play every Sunday morning at Julius Kahn Park in San Francisco, a hidden gem with views of the Bay and the Presidio. We’ve been playing every Sunday for four years. Originally, a few friends and I invited others to come play. After a few sessions, someone started a Facebook group and invited more people that way. Initially, he would set up an event every week. One weekend, he was heading out-of-town. He didn’t tell anyone, but I noticed that he hadn’t set up the event as usual, so I decided to do it. For a while, I kept doing it. Then, I needed to head out-of-town. Sure enough, someone else stepped up and set up the event without anyone asking.

We also have gotten a good number of folks who accidentally came upon the game and kept showing up. Some of them are on the Facebook group, but many are not, not because we’re trying to exclude anyone, but because it’s largely unnecessary at this point. We’re consistent enough that if you show up, we’ll likely be there.

How is pickup basketball like the Internet?

First, there’s some basic infrastructure — a hard surface, a backboard, a basket, and a ball.

Second, there are protocols. Some of them are formal and unshakeable. For example, on the Internet, there’s the Internet Protocol, the base-level protocol that everything on the Internet uses. With pickup basketball, there are the basic rules of basketball — between 1-5 people per team, dribble with one hand only, once you stop, you have to pass or shoot, whichever team scores more wins, etc.

Some of them are informal and loosely enforced, such as the aforementioned pickup basketball variations. Most of the protocols on the Internet began as RFC’s (Request for Comments) — informal technical specs and design documents. Many — such as HTTP, the basis for the World Wide Web — were widely adopted before ever becoming officially standardized.

Third, they’re both decentralized and open, which leaves a lot of room for experimentation and different kinds of leadership (both good and bad). I’ve already mentioned the different cultures and kinds of organizing you’ll find at different pickup games. Another important form of leadership worth noting is the role the NBA plays. It can’t directly dictate what happens on the thousands of basketball courts around the world. However, its athletes and teams have been very intentional in investing in infrastructure — building and maintaining courts, for example — and for acting as ambassadors. The league as a whole has created many channels via media (both old and new) and on-the-ground work to create more exposure for the game all across the world. That ultimately enables the NBA to do what it does best — inspire people all over the world to watch and play the game.

The NBA doesn’t hold meetings for “representatives” of the pickup game network to try to align around a shared vision or to discuss pickup game governance. It doesn’t do social network analysis to try to demonstrate impact. It articulates its own vision of the game by stewarding and showcasing the best players in the world, it invests in infrastructure so that more people can play, and it invests in visibility so that more people are inspired to play.

Folks who are attempting to professionalize networks could learn a whole lot from pickup basketball.

The Practice of Generosity

Jessica and Christy

I spent this past weekend spectating while friends and family achieved acts of extraordinary physical exertion. On Saturday, I watched my friend, Greg, complete a full Ironman in Sonoma County — a 2.4-mile swim, followed by a 112-mile bike ride, and ending with a full marathon (26.2 miles). On Sunday, I watched my sister, Jessica, run her first marathon, which might seem modest next to an Ironman, but is well past the threshold of sanity in my mind.

I will never truly understand what compels people to push their bodies to such extremes. What I have come to understand is the important role that community plays.

My sister runs regularly with friends, a few of whom also participated in the marathon. Those who decided not to run the whole thing volunteered to act as running buddies for parts of the race. My sister had someone running with her for the last 12 miles — no small thing at that point in the race, when your body is constantly telling you to quit. (She’s pictured above with her friend, Christy, who ran the last six miles with her.)

I ran with her from miles 14 through 18. I’m in decent shape, but I’ve never run in an organized race or for more than nine miles (I consider five miles a long run), so I had a hard time relating to my fellow runners at that point. What I could plainly see was that most of the runners were in a lot of pain. Many ran with a labored gait, and many others stopped repeatedly to walk. All along the way, several people had stopped to catch their breath or stretch.

It felt surreal to be running with so many people at once and to feel strong and fully conscious while everyone else seemed to be in pain and slightly unaware. I was in awe of the grit and perseverance of my temporary companions, even while questioning their sanity. Then again, while it was meaningful to experience this viscerally, I wasn’t altogether surprised by it. After all, they had all chosen to run 26.2 miles.

What surprised me was the overwhelming generosity — from the people cheering on the runners every step of the way to the volunteers to the runners themselves, who were constantly looking out for each other, gladly sharing their water and other aids to those in need. There was a bond of mutual support between the runners that was unmistakable, extending well beyond specific actions. I saw knowing nods and glances that seemed to acknowledge the hundreds of hours and miles of perseverance that they all knew each other had experienced. There was no faking it. You couldn’t be there if you hadn’t put in the time.

Everyone cared about each other, and everyone rooted for each other. It felt pretty awesome to experience that first-hand, and it made me wonder what the world would be like if we were all like these runners, if we could all feel that constancy of mutual support.

Upon further reflection, I decided that we are already all like that. We do fundamentally care about each other, and we are fundamentally generous with each other. We just aren’t necessarily conscious about it, nor are we conscious about practicing it. Running brings it out in people, but there’s no reason why we couldn’t be more like that in other aspects of our lives.

My friend and colleague, Renee, is constantly asking about the principles of effective collaboration, a framework upon which we can build and practice. I find these requests challenging, because I feel like these principles have already been articulated by many people, that the framework already exists and is widely understood. Having Renee is a useful foil, because it forces me to challenge and test my assumptions, and it’s surfaced lots of places where I’ve been wrong.

However, I have one nagging belief that has not yet been disproven. I believe that the main reason that it feels like there’s no clear framework for effective collaboration is that the suggested principles seem too simplistic, too obvious.

For example, generosity is a clearly an important principle in effective networks. “Of course!” you might say. “But there must be something else! That can’t be it!”

Are you sure?

At Leadership Learning Community’s Creating Space conference last May, there was a brainstorming session on modules for developing network leadership. We had a number of smart, creative minds in the room, but we got stuck almost immediately. People seemed overwhelmed by the complexity of it all.

I suggested that we focus on one thing and encouraged folks not to censor themselves. Simple, “obvious” ideas were more than okay. They were great!

We chose to focus on generosity as a practice. The group generated a slew of good, interesting ideas. One of them was a generosity award, which anyone could award to anyone else. All they needed to do was to fashion the award out of pipe cleaners and give it someone. It was so simple, we decided to test the idea right then and there.

People started fashioning awards to give to their peers, and three things became immediately apparent.

  1. There were some highly skilled pipe cleaner artists in the room.
  2. People had no problem identifying acts of generosity that had happened over the course of two days among a group of people who largely did not know each other.
  3. Simply naming the generosity that was already happening in the room was itself an act of generosity, one that created a stronger bond and greater sense of community among the group.

Many of the principles of effective collaboration are simple and obvious, but that doesn’t mean they’re wrong or insufficient. If we’re going to make progress in the world, we need to start with the simple, the timeless, the human. We need to commit to these things, to practice them unrelentingly, and to give them time to work before we give up on them and seek something new.

Fortunately, while we may forget these principles in our every day work and lives, there are plenty of good models that remind us of their simple, yet critical importance as well as their strong desirability. Running with my sister, watching her, my friend, and their people persevere, and experiencing their community firsthand was a wonderful reminder of what the world would be like if we were all more generous with each other.

A Funny Thing Happened the Other Day on the Internet…

This past week, I spent two days in Tiburon supporting my former colleague and bootcamper, Dana Reynolds, who was facilitating the Code for America staff retreat. Any time spent with the good folks at Code for America is going to be inspiring time, and I couldn’t help expressing this sentiment on Twitter after the retreat was over:

Total time spent tweeting this: Maybe 30 seconds.

Then a funny thing happened. Someone named Jang from Korea responded to my tweet with a question:

I didn’t know Jang, so I glanced at his Twitter profile, and I saw that my friends, June Kim and SeungBum Kim, followed him. That was a good sign, so I responded, resulting in the following exchange, each message less than 140 characters:

I was planning to send an email to some folks at Code for America to follow up, but it wasn’t necessary. Conversations on Twitter happen out in the open, and Cyd Harrell, Code for America’s UX evangelist, saw the thread and responded. This is what happened:

I don’t know what’s going to emerge from this whole interaction, but something good will. At worst:

  • I learned something new about an issue I care about in a country I care about
  • I made some new connections
  • I facilitated some new connections
  • I strengthened some old connections

All from simply tweeting how I was feeling one evening.

This is what can happen when you have ways to communicate with lots of people transparently and with very little friction. But it’s also critical to recognize what underlies the technology that makes this sort of thing possible: people, trust, relationships, and literacy.

Bottom line: This sort of thing makes me very, very happy.

Changemaker Bootcamp: An Experiment in Practice and Mentorship

Starting today, I will be embarking on a new experiment, which I’m calling, “Changemaker Bootcamp.” I’ll be creating a space for changemakers in organizations to:

  • Get clear about the kinds of shifts they’d like to see in their groups (be they their own organizations or broader)
  • Get clear about how to facilitate those shifts
  • Practice the skills necessary to facilitate those shifts

I have two wonderful guinea pigs co-learners, who responded to a quiet call on this blog last month and who will be embarking on this journey with me. (I’ll be saying more about them later, and they’ll be saying plenty about themselves and their projects on a group blog.) We’ll meet for 90 minutes once a week for the next four weeks, at which point we’ll all reflect on what we’ve learned, and we’ll figure out what happens next.

Why Am I Doing This?

The Brief Summary:

  • I am passionate about figuring out ways to boost the world’s collaborative literacy, which will result in a world that is more alive.
  • The biggest barrier to changemakers developing these skills are finding productive opportunities to practice them.
  • I’ve had the unique opportunity to learn and practice these skills for the past 10 years. I’d like to create similar opportunities for others who are similarly motivated.
  • I am anxious to explore ways to create “balance bikes” for changemakers — structures that help changemakers learn these critical group skills. This bootcamp is a first experiment in this.
  • I love this stuff, and I’m excited to try something new, challenging, and potentially impactful.

The Longer Summary: I devoted the past 10 years to practicing skills for helping groups work more skillfully together. I had to carve out my own path, and while it was meaningful and gratifying, it was also painful and arduous. While I was tremendously motivated (some might say obsessed) and worked hard, I was also very lucky. I had amazing mentors, peers, and partners, people who believed in me, encouraged me, offered me amazing opportunities to try stuff and to learn (despite lots of stumbling), and provided me with critical feedback.

I want to give back, but I want to give back bigger than I got. I want to leverage what I’ve learned over the years, my wonderful network of friends and colleagues, and whatever reputation I might have in this space to give other changemakers safe opportunities to practice, stumble, and learn.

When I left Groupaya at the end of last year, I thought the best way to share what I learned would be through writing. I’ve changed my mind. I have some good stories and I might have a unique spin on how I articulate what I’ve learned, but I don’t have much to say that hasn’t been written a thousand times already. There are already lots of books and articles on collaboration, collective intelligence, learning, openness, participatory processes, and facilitating change. Lots of them are decent, some of them are very good, and some are even extraordinary.

What’s missing are safe opportunities to practice these critical skills. My friend, Jon Stahl, wrote a provocative blog post about social change movements two years ago, where he summed up the problem as follows:

Social change work is hard, long-term work.

Like most hard work, it takes a lot of practice to get really good at it. Malcolm Gladwell in Outliers claims that it takes about 10,000 hours (10 years) of practice to really master something.  I don’t see why social change organizing/campaigning should really be any different.

People who have the skills to be outstanding social change activists have lots of choices and opportunities in their professional life — they have the leadership, analysis and “getting things done” skills to be valuable in many fields.

So, given these realities, are social change movements structuring themselves to attract highly skilled potential superstars and to retain them for the 10 years it takes to attain mastery… and beyond, into the most highly productive years that follow?

Creating opportunities for others to practice skills for effective changemaking will be far more impactful (and frankly, far more enjoyable) than writing a book.

What Will I Be Doing?

“Bootcamp” isn’t simply a marketing term. I’m loosely modeling this after fitness bootcamps, with an emphasis on building core strength, creating good habits, and doing rather than discussing. This will not be a “training” in a traditional corporate sense, as my emphasis will not be on delivering content, but on learning through practice.

I had lots of interesting conversations as a result of my call for co-learners, but I decided to focus on San Francisco-based changemakers embedded in organizations who had specific projects on which were embarking.

I limited it to San Francisco to keep this first experiment simple.

I’m focusing on changemakers embedded in organizations and who are not formally leading their organizations because I think that’s where the biggest opportunity for impact is. It is the opposite strategy of when I was a consultant, where we only took on projects that were sponsored by C-level leaders. We did this because we felt it would give our projects the greatest chance to create sustainable change and, frankly, because C-level leaders were generally the only people with budgets big enough to afford us. That was good for business, but it also increased the chances for impact, because it meant the organization had more skin in the game. It was the right strategy as a consultant, but it’s not the most impactful strategy from a systems perspective.

I also favored changemakers who had specific projects in order to keep the work grounded. I think the skills they develop will be applicable to everything they do, but I want to have specific goals in mind to create a sense of urgency as well as to tie this development process to their everyday work needs.

I will be doing the same exercises as my participants, since I myself am a changemaker based in San Francisco, and I have a specific project (this one) that I’m working on. We will all be working transparently, blogging about what we do and what we learn, because working transparently is a critical changemaker skill, something that we all need to practice.

I’ll also be sharing all of my “workout plans,” along with the metrics I plan on using to track my progress. I would be thrilled if others “stole” the idea and the plans, because we need a lot more people doing this kind of thing, experimenting with ways to do it more effectively, and sharing what they learn so that we can all benefit from it.

What Do I Hope to Learn?

  • Is this a model that helps changemakers learn the skills they need to be learning?
  • What are the actual and potential impacts of such a process?
  • How can I tweak the model to make it even more impactful?
  • How can I get better at implementing the model?
  • Is this a service that changemakers want?
  • Is there an opportunity to build a business around this?
  • Is this something I enjoy doing?

How Do I Follow This Crazy Experiment?

We’ll all be sharing our experiences on a group blog, where I’ll also be sharing annotated “workout plans.” I’ll also likely be writing some stuff here on this blog.

If you’re interested in following along and perhaps even participating in future experiments, please subscribe to my mailing list by filling out and submitting the following form:

* indicates required

// 40) return;
mce_preload_checks++;
try {
var jqueryLoaded=jQuery;
} catch(err) {
setTimeout(‘mce_preload_check();’, 250);
return;
}
try {
var validatorLoaded=jQuery(“#fake-form”).validate({});
} catch(err) {
setTimeout(‘mce_preload_check();’, 250);
return;
}
mce_init_form();
}
function mce_init_form(){
jQuery(document).ready( function($) {
var options = { errorClass: ‘mce_inline_error’, errorElement: ‘div’, onkeyup: function(){}, onfocusout:function(){}, onblur:function(){} };
var mce_validator = $(“#mc-embedded-subscribe-form”).validate(options);
$(“#mc-embedded-subscribe-form”).unbind(‘submit’);//remove the validator so we can get into beforeSubmit on the ajaxform, which then calls the validator
options = { url: ‘http://eekim.us1.list-manage.com/subscribe/post-json?u=4bdca8ff4c02cbf0342cc9f71&id=1f46f4182c&c=?’, type: ‘GET’, dataType: ‘json’, contentType: “application/json; charset=utf-8″,
beforeSubmit: function(){
$(‘#mce_tmp_error_msg’).remove();
$(‘.datefield’,’#mc_embed_signup’).each(
function(){
var txt = ‘filled’;
var fields = new Array();
var i = 0;
$(‘:text’, this).each(
function(){
fields[i] = this;
i++;
});
$(‘:hidden’, this).each(
function(){
var bday = false;
if (fields.length == 2){
bday = true;
fields[2] = {‘value’:1970};//trick birthdays into having years
}
if ( fields[0].value==’MM’ && fields[1].value==’DD’ && (fields[2].value==’YYYY’ || (bday && fields[2].value==1970) ) ){
this.value = ”;
} else if ( fields[0].value==” && fields[1].value==” && (fields[2].value==” || (bday && fields[2].value==1970) ) ){
this.value = ”;
} else {
if (/\[day\]/.test(fields[0].name)){
this.value = fields[1].value+’/’+fields[0].value+’/’+fields[2].value;
} else {
this.value = fields[0].value+’/’+fields[1].value+’/’+fields[2].value;
}
}
});
});
return mce_validator.form();
},
success: mce_success_cb
};
$(‘#mc-embedded-subscribe-form’).ajaxForm(options);

});
}
function mce_success_cb(resp){
$(‘#mce-success-response’).hide();
$(‘#mce-error-response’).hide();
if (resp.result==”success”){
$(‘#mce-‘+resp.result+’-response’).show();
$(‘#mce-‘+resp.result+’-response’).html(resp.msg);
$(‘#mc-embedded-subscribe-form’).each(function(){
this.reset();
});
} else {
var index = -1;
var msg;
try {
var parts = resp.msg.split(‘ – ‘,2);
if (parts[1]==undefined){
msg = resp.msg;
} else {
i = parseInt(parts[0]);
if (i.toString() == parts[0]){
index = parts[0];
msg = parts[1];
} else {
index = -1;
msg = resp.msg;
}
}
} catch(e){
index = -1;
msg = resp.msg;
}
try{
if (index== -1){
$(‘#mce-‘+resp.result+’-response’).show();
$(‘#mce-‘+resp.result+’-response’).html(msg);
} else {
err_id = ‘mce_tmp_error_msg’;
html = ‘

‘+msg+’

‘;

var input_id = ‘#mc_embed_signup’;
var f = $(input_id);
if (ftypes[index]==’address’){
input_id = ‘#mce-‘+fnames[index]+’-addr1′;
f = $(input_id).parent().parent().get(0);
} else if (ftypes[index]==’date’){
input_id = ‘#mce-‘+fnames[index]+’-month’;
f = $(input_id).parent().parent().get(0);
} else {
input_id = ‘#mce-‘+fnames[index];
f = $().parent(input_id).get(0);
}
if (f){
$(f).append(html);
$(input_id).focus();
} else {
$(‘#mce-‘+resp.result+’-response’).show();
$(‘#mce-‘+resp.result+’-response’).html(msg);
}
}
} catch(e){
$(‘#mce-‘+resp.result+’-response’).show();
$(‘#mce-‘+resp.result+’-response’).html(msg);
}
}
}
// ]]>

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.