Magic Johnson – Eugene Eric Kim

A friend posted a video clip of his favorite basketball play ever on his Facebook page, and invited others to do the same. It made me curious if mine was online, so I did a quick search on YouTube for, “Magic no look pass nobody Portland.” The play I was looking for was the first to pop up. (The Internet is an amazing place.)

It’s from Game 7 of the 1991 Western Conference Finals between my Los Angeles Lakers and the Portland Trail Blazers. There’s 12 seconds left. The series is tied 3-3. The winner will go on to play the Chicago Bulls, Michael Jordan’s first NBA Finals. The Lakers are up by one. Portland is inbounding the ball. Portland gets the ball to Terry Porter for a jumper to win. He misses.

Magic Johnson rebounds the ball with two seconds left. The only thing Portland can do at this point is foul. Magic is very good at shooting free throws — he made over 90 percent of them that season — but even if he makes both of them, Portland would have a chance to advance the ball to half court and get a three off to tie the game. Three seconds is all the time in the world.

What happens next is still clearly emblazoned in my brain, as it showed Magic’s preternatural brilliance as a basketball player. As soon as Magic gets the rebound, he throws a cross-court, no-look pass over his head. To nobody. The ball slowly trickles out of bounds on the opposite side of the court with 0.1 seconds left on the clock. The game is sealed. Now there’s no way for Portland to come back.

If you look at the other players from both teams in that first split second, they have no idea what Magic has done. Then they see the ball trickle out of bounds, and stunned realization spreads across their faces.

Who even thinks of doing anything like this? I’ve never seen anything like it since.

In retrospect, that game was loaded with history. It was Magic’s first season playing without Kareem Abdul-Jabbar and Pat Riley. (Hello, Vlade Divac and Mike Dunleavy.) It would be his last playoff series win ever, as he and Byron Scott would bow out of the next series with injuries, allowing Michael Jordan to win his first NBA championship. (That’s right, I said it. Allowing.) The following year, he would make his stunning announcement that he had HIV and would be retiring immediately.

I can’t believe that game was almost 30 years ago. I can remember it like it was yesterday, and I love that this clip is on YouTube.

In other hoops news, ESPN just announced that its 10-part documentary on Jordan’s last championship season, The Last Dance, will now debut in April instead of June, thanks to everyone being cooped up inside without any sports to watch. That was only 22 years ago, and I can also remember that series like it was yesterday. Damn, I’m old.

I spent this past Saturday in Sebastopol “tutoring” Gail Taylor, Todd Johnston, and Tiffany Von Emmel on online Collaborative Tools. I lured Matthew O’Connor into helping by boasting of Gail, Todd, and Tiffany’s deep thinking about and practice of collaboration. (LVC)

One of our exercises was to walk through all of our respective digital workspaces, demonstrating how we read and wrote email, and worked with online tools. I had gotten some idea of how Matthew worked when we paired at the Wikithon earlier this month, but I was still blown away by his walkthrough. He’s really thought deeply about his work processes and has optimized his online workspace accordingly. (LVD)

Matthew expressed surprise that he was the only one who had done this, especially since I had proclaimed these folks to be gurus. I didn’t have a chance to discuss this with him on Saturday, so I thought I’d post some thoughts about that here. (LVE)

To be good at collaboration, you have to treat it as a system. That system includes things like communication, community, Knowledge Management, learning, and leadership. (LVF)

Most Collaborative Tools companies are either in the communication or the Knowledge Management business. They’re usually selling pipes, PIMs, or document management tools. All of those things have something to do with collaboration, but they are not in and of themselves collaboration. Then again, no tools are. A hammer is a tool for hammering, but it is not itself hammering. (LVG)

When I think about High-Performance Collaboration, I envision groups with excellent Group Information Hygiene. Ideally, you’d also like every member of the group to have outstanding Personal Information Hygiene (like Matthew), but it’s not a prerequisite. You’d like to see every member to be past a certain threshold of competence for all aspects of the system, but I don’t think it’s necessary for everyone to be great at all those things. On a great basketball team, you’d like everyone to be in good shape and have good fundamentals, but some players are going to be superior shooters while others will be great rebounders. It’s not necessary, nor realistic, nor possibly desirable to have 12 Magic Johnsons on a team. (LVH)

Implicit in my One Small Change post is that there is no one thing. I can think of a number of small, concrete changes that could result in significant improvements in collaboration. This is one of the main reasons why Pattern Languages — collections of named, concrete patterns — are fundamental to The Blue Oxen Way. (LVI)

Personal Information Hygiene is a critical pattern, because it fosters trust. My advice to groups with trust issues would be to eschew squishy exercises and look at people’s Personal Information Hygiene instead. However, past a certain level, I don’t see great Personal Information Hygiene as being the primary hallmark of a great collaborator. (LVJ)