Productivity, Working Big, and Spatial Awareness

My colleague, Jeff Shults, has a saying: “Work big.” Jeff is a space guru, as many of you who have participated in a Blue Oxen Associates workshop know, as most of my events have been at his different spaces. The most glaring feature of his space are the huge, movable work walls.    (MQE)

Working big is important even when we’re working small — at our desks in front of our computers, for example. I’ve cited speculation and a study on the productivity gains from using larger screens. I recently ran across Clive Thompson‘s New York Times magazine article that cited a similar study by Mary Czerwinski at Microsoft.    (MQF)

On the bigger screen, people completed the tasks at least 10 percent more quickly – and some as much as 44 percent more quickly. They were also more likely to remember the seven-digit number, which showed that the multitasking was clearly less taxing on their brains. Some of the volunteers were so enthralled with the huge screen that they begged to take it home. In two decades of research, Czerwinski had never seen a single tweak to a computer system so significantly improve a user’s productivity.    (MQG)

Thompson makes a key point in his article: Productivity in an interrupt-driven world seems to be closely related to our ability to switch and remember different contexts. Bigger screens allow you to take advantage of spatial awareness to switch and remember different contexts.    (MQH)

There’s a corollary to this regarding complex problems. I’m convinced that the primary value of graphical facilitation is not the Visual Language used to capture ideas, but the relationship created between ideas and space. In other words, you’ll remember the discussion around an idea better if you remember that it was the conversation that was captured on the lower right hand side of the screen or wall. This belief has greatly eased my stress when Dialogue Mapping, as ultimately, I see my task as building spatial memory.    (MQI)

That’s not to say that Visual Language isn’t important. It is, and fortunately, there’s a fantastic community of folks who are exploring it. The better news is that many of these folks will be converging in San Francisco on January 27-29, 2008 for the VizThink conference.    (MQJ)

She’s Geeky, October 22-23

The tireless and talented Kaliya Hamlin is organizing a new gathering: She’s Geeky, coming October 22-23, 2007 at the Computer History Museum in Mountain View:    (MLA)

The She’s Geeky (un)conference will provide an agenda-free and friendly environment for women who not only care about building technology that is useful for people, but who also want to encourage more women to get involved.    (MLB)

It is designed to provide women who self-identify as geeky and who are engaged in various technology-focused disciplines with a gathering space in which they can exchange skills and discuss ideas and form community across and within disciplines.    (MLC)

Blue Oxen Associates just signed on as a sponsor. But, I’m not allowed to register. Why? Registrations are for women only. Am I okay with that? Absolutely.    (MLD)

Intimacy Gradients are critical for effective collaboration. I spend a lot of time teaching groups how to be more open; no one needs a lesson on how to be more closed. But there are times when being closed has value.    (MLE)

I’ve expressed my admiration for BlogHer many times. Their conference has been open to both women and men from the beginning, and I think it’s worked in their favor. But their ad network is for women bloggers only. Is that a bad thing?    (MLF)

Similarly, whatever gets blogged or recorded on the Wiki at She’s Geeky will be open to all. It’s just that only women will be allowed to attend.    (MLG)

Women are a huge minority in technology. Regardless of why that is, there are many good reasons why women in technology should collaborate more with each other. Sometimes, the best way to kick start that is to create a safe space. That’s what She’s Geeky is all about.    (MLH)

Speaking of women in technology, Lloyd Budd recently blogged about Leslie Hawthorn, another person whose praises I’ve sung on many occasions. Leslie is a classic Yellow Thread, someone who deserves much celebration.    (MLI)

Work Rhythms

I’ve been absent from this blog for almost a month, which is unusual for me. It started with my trip to Baltimore last month for Creating Space, the Leadership Learning Community‘s annual conference, and it ended with the Compendium Institute workshop last week here in the Bay Area. In the middle, I cranked away on my projects and spent some quality time with friends and family. I didn’t get much reading done, but I got a whole lot of good thinking done.    (M7Z)

Nancy White recently wrote of the challenge of balancing work and life, of the nitty gritty and the big picture:    (M80)

Because I fear that if I allow myself to be consumed by work, I will not achieve what I aspire from my work: to add value to the world. Work with a capital W. Some days lately I feel I’m tottering on a “check the box” mode of working. That is when learning stops and, to me, my ability to add value stops. It is a fuzzy line and easy to miss. It is when the quality of attention shifts. Diminishes.    (M81)

I want the shift to always be towards the side of learning, not just getting things done. Of attention and reflection, not forgetting.    (M82)

Her words resonated with me (as they often do). Last year was ground-breaking for me in this regard. For the first time since founding Blue Oxen Associates, I started to build in time for deep reflection about what I was doing and why, and about whether I was accomplishing what I wanted to accomplish.    (M83)

When I was in college, I used to lift weights with a buddy of mine who was an ex-football player. We were both intense guys, and when I’d get in one of my workout grooves (not that often), we’d lift almost two hours a day, five days a week. I got much stronger pretty quickly, but I also peaked quickly as well. I blamed it on the irregularity of these workout grooves.    (M84)

My junior year of college, I started lifting with a neighbor of mine, a big guy who was fanatic about fitness. In one of our early workouts, I complained that I never seemed to get any stronger. “How often do you lift?” he asked. Upon hearing my response, he told me to shorten my workouts — three days a week, no more than 45 minutes a day. I was extremely skeptical, but I tried it, and to my surprise, it worked amazingly well.    (M85)

I’ve written previously about the cycle of thinking and doing. When you’re designing for collaboration, you need to take these natural cycles into account. Doing so usually requires a lot of discipline, especially because it requires fighting workaholic instincts.    (M86)

One of my epiphanies last year was that I wasn’t doing a good job of practicing what I preached, of living what I knew. In particular, I was getting too caught up in the nitty gritty and not spending enough time reflecting. I was getting too deeply involved in too many things, and I was overscheduling and overcommitting.    (M87)

I decided to make four major changes. First, I was going to cut down on the number of projects I would take on simultaneously. That meant saying no more often, and fighting the instinct to get deeply involved in everything I did.    (M88)

Second, I was going to cut down on the number of events I attended, especially those that required travel. Because most of the events I participate in are intense experiences (I rarely participate in networking events), I decided that I would schedule an equal amount of time for reflection. In other words, for every three day workshop, I would need to schedule three days for reflection and processing.    (M89)

Third, I was going to go on more walks. Not only is this a great way to get exercise and think, it’s a great way to think with others. It’s no coincidence that Aristotle and his followers were known as Peripatetics. Instead of constantly meeting folks in coffee shops, I started telling people to join me on walks instead, a trick I picked up from Howard Rheingold. Fortunately, San Francisco has a number of gorgeous places for short, casual hikes.    (M8A)

Fourth, I was going to spend more meaningful time with people. This nicely aligned with my walking edict, but it also meant interacting with less people overall.    (M8B)

I’ve been good about doing all four of these things. Not great, but good. As with the weightlifting, doing less still feels counterintuitive. And just as with the weightlifting, doing less has generated the desired results. This has manifested itself in a number of ways. I’ve only gone on one work trip so far this year, whereas last year, I averaged a trip a month. I’ve blogged more consistently. I feel more connected with colleages and with friends. I’ve had time to really develop ideas and projects that are core to my mission. Most importantly, I feel Less Dumb, which is one of the main tenets of The Blue Oxen Way.    (M8C)

The Fractal Nature of Large-Scale Collaboration

Collaboration is a meta-discipline. It is usually the means, not the end. You don’t collaborate for collaboration’s sake; you collaborate to accomplish some bounded goal. Making the means the end is tricky business. When you eliminate the context, it’s easy to shift from thoughtful practice to ivory tower jibber jabber and suffer the consequences of Professionalization. All communities and networks centered around meta-disciplines are vulnerable to this, including Blue Oxen Associates. It would not be an exaggeration to say that this is my foremost challenge as a social entrepreneur and as a scholar-practitioner.    (M65)

Being meta also has its benefits, however. Over the past few years, I have been helping more and more groups with the conundrum of being a top-down, command-and-control organization in a heavily network-centric world. Sometimes, this takes the form of coaching, where I talk the organization through principles and provide encouragement through what can be a painful and frustrating process. My approach is to tap into the existing organizational instinct and experience as much as possible while challenging assumptions by identifying and asking deep, underlying questions.    (M66)

Other times, it takes the form of designing a convening. These convenings play the same role as my coaching does, except it accelerates Shared Understanding among the stakeholders and it leverages Wisdom of Crowds.    (M67)

Here’s where the meta-ness of the collaboration business becomes useful. The act of co-designing a highly interactive convening, then experiencing it first-hand is a smaller-scale representation of the steps an organization would go through to transform itself into something more network-oriented and collaborative. Even though these convenings are smaller than the large-scale challenges that these organizations face, the principles are the same, whether you’re dealing with 20 or 20,000 people.    (M68)

These convenings are never meta. They are always about something concrete that is directly relevant to the organization.    (M69)

They start with the principle that everyone has different worldviews, but shares strong values. They facilitate interactivity, artifact generation, and continuous resynthesis of knowledge.    (M6A)

They don’t try to control participants. Instead, they let the right path emerge. They allow subgroups to form, to be creative, and to explore their own ideas and interests, without losing The Red Thread of the network as a whole.    (M6B)

By helping organizations design, then experience these convenings, I am indirectly helping them understand how to transform their organization in an experiential way. That’s a direct result of both the fractal nature of large-scale collaboration and the meta-ness of being in the collaboration business.    (M6C)

Nexus For Change Observations

I’m about to comment on a conference that I reluctantly didn’t attend: Nexus For Change. Sure, I’ve read rumblings from the conference site as well as the blogosphere and Flickr, and I’m sure there’s more to come as folks recover from what was undoubtedly a mind-blowing two days. I’ll also happily use my absence as an excuse to touch base with friends and colleagues who did attend.    (M1G)

Despite my lack of complete information, what’s compelling me to comment is this picture that Nancy White took:    (M1H)

https://i0.wp.com/farm1.static.flickr.com/168/433799450_fd35e6de3e.jpg?w=700    (M1I)

I love the elephants that were identified. But the thing that really jumped out at me was the elephant on the upper right: “No youth present.” Disappointing, but not surprising. And frankly, probably a good thing… this year. This convening was already a coup, and it takes baby steps to make big changes in the world. But it will be a horrible thing if it becomes a trend.    (M1J)

About a month ago, there was a thread in Chris Messina‘s Flickr stream about the need for a book on unconferences. I commented:    (M1K)

There’s already an excellent book like this. It’s called The Change Handbook, and it documents a ton of great thinking and experience on group process and catalyzing transformation.    (M1L)

The Bar Camp phenomenon adds something new and vibrant to all of this, and is not represented in the book (AFAIK — I haven’t seen the second edition yet). So there’s still a need for that knowledge to be integrated into the larger body of practice.    (M1M)

This is a classic case of two communities with similar values and different demographics not talking to each other and certainly not collaborating. How do you get these communities to collaborate? You either wait for it to happen on its own, or you catalyze it.    (M1N)

At the Blue Oxen Associates 4th anniversary party last December, I said that I’d have some exciting things to announce this year. I was being dramatic then, and I’ll probably be dramatic again in a few months when I announce some new initiatives. In short, I’ll be describing a concrete plan for catalyzing collaboration between these communities. I’ve been preparing for months now, and I’ve still got a few more to go, but I’m already giddy. This has been the vision behind Blue Oxen Associates from day one. When I started the company, I had a five year plan for achieving this vision. It’s a good thing, too, because I’ve needed each and every one of the past four years to reach a point where I felt like I could make a significant difference. I’ve still got a ton to learn, but I also feel incredibly empowered, and I can’t wait to share and apply what I know with the rest of the world.    (M1O)