Connectedness: Network Centrality: Pros and Cons of Male Enhancement

Just in time for my last installment on network centrality, I have learned that Google now ranks Connectedness the #1 site on the Web for "pros and cons of male enhancement." It's tempting to take credit and say that this honor was the result of long, hard work on my part; but it was endowed upon me more by the fates of centrality than by anything I did. (Those who doubt my boast and are not afraid to look, click here: http://www.google.com/search?q=pros+and+cons+of+male+enhancement.)

Without taking anything away from the experts who have filled my blog with their thoughts on the topic, I now want to make perfectly clear my position on male enhancement: The field of collective leadership needs it bad, especially the non-profit/social-change sector.

I love working with collective leadership programs, and

I am fortunate to do so regularly. The recipe for this work adapts to the participants, but it almost always involves something like the picture at right. See W.K. Kellogg Foundation's Collective Leadership Framework and the D.C. Leadership Learning Community's Nature of Collective Leadership for more.

In other sectors, collective leadership draws less with crayons and uses other more dangerous sticks. Speaking of collective leadership in the field of science, John Ziman says that each individual's contribution is "merely a tiny tentative step forward, through the jungles of ignorance." I don't think his savage choice of setting --- where only the fittest survive, thanks to teeth, claws, and other weapons --- was any accident.

My Introduction to Web Programming class has filled up again for this fall. It's my personal collective leadership learning lab. How can I equip 75 computer-illiterate college kids with the wherewithal to make their own websites (like these)? I can't. But together, they can. I facilitate my students' learning by dropping them into the Internet jungle and encouraging them to trust their own most primitive hacking instincts.

In the spirit of crayons and group hugs, my first gift to my students each term is an online discussion forum where they are encouraged to share anything relevant to the class. Speaking to a ballroom-full of faculty about his experience, Will Mundel noted first and foremost that "Thanks to the online forum we used in CS-103, students stop being individuals in a class. Rather, they are all in it together."

I am honored by Will's comment, but that's not the whole story of how my students learn to build their own websites. Underlying the experience of the class is a curriculum I have modeled on the traditional male rite of passage: (1) Throw a boy out of society into the wilderness; (2) Let him suffer and learn; and (3) Welcome the transformed man back into society. (That's my paraphrasing. Here's what the American Psychological Association says about this method of transformational learning.) If you look closely at this gallery of student projects, you'll see a quote from another student that speaks directly to her painful but ultimately victorious journey alone through the wilderness.

After subjecting my students to this webified passage of suffering, I top it off with a month-long tournament of hand-to-hand combat. Within the cage of this special-built wiki, the students compete for Google-rank supremacy. This part of the class evolved from my desire to translate the inner workings of the Google centrality algorithm into the real-life experience of the kids.

Inviting students into this kind of centrality-based competition is not easy. My first attempt provoked class revolt because students perceived the rankings as an unfair system of grading their work. (The fact that the competition had no impact on actual grades was irrelevant to this revolt.) My second attempt went smoothly: I was careful to provide a fair system for peer reviews in parallel with the same centrality-based competition. With fair peer reviews in hand, the students no longer were bothered by the arbitrariness of centrality rankings.

Last spring was my third and by far most successful use of the centrality competition. Not only was there no resentment at the arbitrariness of centrality rankings, but there was a positive embracing of the system. Students discovered how to form alliances and deliberately manipulate the Google algorithm into boosting their own rankings. A flurry of new links and surprise defections preceded the day of our awards ceremony. Three alliances shared top honors. When I refused to award a prize to one of the alliances because their team leader had skipped class that day, his teammates/co-conspirators texted him and made him show up, 20 minutes late, so that they could receive their prize: a one-half of one percent boost in final course grade.

Technical postscript: For those wondering how it's possible to share top honors in a Google centrality competition, the answer is quite technical. From this more-or-less readable description of the Google algorithm, you can discover a "damping factor" that Google does not allow users to see or edit. I provide my students with a Google centrality calculator that allows them to edit this damping factor to whatever they want. Changing the damping factor can sometimes change the winner of the rankings; I award first prize to anyone who can find a damping factor value that puts them atop the rankings. In the following network, every single node with a label can win the Google centrality contest with the right damping factor: