Dark Matter Matters
transparency
Love, hate, and memo-list
Top management experts are now acknowledging the importance of creating forums and contexts inside corporations that allow peer review, transparency, and powerful natural hierarchies to flourish. Here’s one great post by Gary Hamel from earlier this year that Iain Gray pointed out today. We’ve had an open forum exactly like this at Red Hat for a very long time. We call it memo-list.
The Greek agora at Tyre. It used to be a popular gathering place back in the day.
When any new employee comes into Red Hat, memo-list is one of the first great shocks to the system. Memo-list itself is not some technological marvel of a collaboration tool– it is just a simple, old skool mailing list where any Red Hat employee can post an email message that goes out to virtually every employee in the company. That’s 3000+ folks.
Memo-list has been a hot issue inside the walls of Red Hat since before I joined ten years ago. Folks tend to either love it or hate it.
Some people are shocked by the fact that any employee can publicly challenge a post by an executive or even the CEO in an email to memo-list (and they do). Some people are annoyed by the discussions that appear over and over, year after year. Some people view it as idle chitchat and a waste of time.
But some people view it as the backbone of the Red Hat culture. A place where the power of meritocracy is nurtured. Where the employees force transparency, openness, and accountability. Where peer review makes for better ideas (after all, given enough eyes, all bugs are shallow).
I love memo-list, warts and all (I think Gary Hamel would like it too). In my view, it is the single most important thing that differentiates the Red Hat culture from most other corporate cultures.
Brand tip: Call a duck a duck
Imagine this: You walk into a pet store, looking for a canary, because, i don’t know, maybe your coal mine is having dirty air issues or something. The salesman, eager to please, walks you over to a cage with a duck sitting in it.
I may be yellow, but I ain't no canary, yo.
He says, “Do I have just the thing for you, check out this canary. He is a new, better breed of canary. He has webbed feet, can swim, quacks rather than sings, he’s bigger. We call this the web-footed hydro ultracanary. You’ll love him.”
So you buy the “canary” and take him into your coal mine, where he quacks incessantly. In fact, he is still waddling around quacking about ten minutes after you and all of the other miners are lying dead from breathing poisonous air.
In this case, the brand promise (a canary) and the brand experience (a duck with strong lungs) did not match. If you had been looking for a duck, this little guy would have probably been perfect. But as a canary… not so much.
One of my favorite brand rules is to call your ducks ducks. What do I mean? Make things simple for your customers. Don’t make them learn your language or analyze your intent in order to understand your message. Be straight with them.
Jim Whitehurst: 20th century companies already hiring 21st century employees
Last night, Red Hat President and CEO Jim Whitehurst gave a talk to a group made up of mostly students and faculty at the NC State School of Engineering. Nice writeup of it in the student newspaper here. His ideas were very timely for me; just the other day, I wrote a post with some tips for companies with 20th century cultures trying to make the move into the 21st century.
Your future employee sez: I'm going to need a bit more collaboration and meritocracy up in here! (photo by D Sharon Pruitt)
Jim Whitehurst is in a rather unique position because he has managed both an icon of the 20th century corporation (Delta Airlines) and what we’d like to think is a good example of the 21st century corporation here at Red Hat.
Because of his experiences, Jim is able to clearly see and articulate the differences between the old model of corporate culture, based on classic Sloan-esque management principles, and the emerging model, based in many ways on the power of participation broadly (and in our case, the open source way specifically).
One very simple point Jim made that really struck me: Companies with 20th century business models need to realize that they are already hiring 21st century employees.
People coming out of school today have grown up in an age where the ability to participate and share broadly is all they’ve known. These folks have grown up with email accounts, the Internet, Facebook, and all of the other trappings of a connected world.
So when they graduate from school and take jobs working in old-style corporate cultures, where progressive principles like transparency, collaboration, and meritocracy lose out to the old world of control, power, and hierarchy, what happens?
Does transparency really have to start on day 1?
Open source folks often talk about transparency as a key part of the open source way. And if you ask most good open source folks when a project should start being open, they’ll say it should be open from the very beginning.
But what does that really mean?
Let’s look at the example of one of the most famous and successful open source projects (and one that is close to my heart), Linux.
Back in January, I wrote a post that broke down the first message Linus Torvalds ever sent out to the world about Linux into some of the key concepts that would become central to the open source way. Linus created a blueprint for the open source culture in the tone of his first email, long before the term “open source” was even coined.
Here again are the first few lines of his initial Linux post from August 25, 1991:
Jack Welch on transparency, meritocracy, and the death of hierarchy
On Tuesday I’m heading up to New York to share an open source perspective with GE marketing executives at the legendary GE leadership center in Crotonville. I wrote a post a few months ago praising GE Chairman Jeffrey Immelt’s compelling new vision for corporate America, and I have an enormous amount of respect for GE as an innovation engine. I’m excited about the opportunity to exchange ideas with the smart folks there.
In 2009, Forbes ranked GE as the world’s largest company, so I’ve figured before I went up to Crotonville it’d be a good idea to do some homework and see what elements of what we call the open source way are already in practice within one of the most successful companies in history. I’ve found some interesting stuff in my research.
One piece in particular grabbed me. Sitting on the beach today over the holiday weekend, I finished the 2001 biography of Jack Welch (the legendary predecessor to Immelt as Chairman of GE) entitled Jack: Straight from the Gut. I thought I’d share a Jack Welch prediction (written almost ten years ago) that fits right in with our open source view of what the 21st century organization looks like.
Save us, General Zinni! Teach us corporate folks some 21st century leadership skills
I happened to catch General Tony Zinni on The Daily Show a few weeks ago. This was the first time I’d seen him talk, and I found him to be an incredibly creative, thoughtful man. So this weekend, I sat down and read his recently published leadership book Leading the Charge: Leadership Lessons from the Battlefield to the Boardroom. If you want to learn more about General Zinni’s long list of accomplishments, both inside and outside the military, there is a really good Wikipedia profile of him here.
In this book, General Zinni describes an introspective, creative, and rapidly changing American military mindset. After reading, I’m convinced the subtitle should have been something like “Lessons from the New Military for a Corporate America Totally Blowing It.”
This book provides a crisp analysis of the failures of the 20th century leadership model still prevalent in most businesses today. It is an indictment of the post-economic-meltdown-state of American business, which he believes was caused in large part by a systemic failure of this traditional leadership model.
Like a true man of action, General Zinni brings his own ideas and experience of leadership methods that work in the high-pressure, high-risk world of the military to the table. He provides a vision for how we can fix what is broken, and shows what the leadership model for the 21st century organization could be.
Army training the open source way
Very cool article in the New York Times yesterday entitled Care to Write Army Doctrine? With an ID, Log On.
Pvt. Winger sez let's open source ARMY TRAINING, SIR!
The gist is the Army is running an experiment in mass participation, allowing any member of the Army, from five star general to latrine specialist, to edit a test group of seven Army field manuals using an online wiki. From the article:
“For a couple hundred years, the Army has been writing doctrine in a particular way, and for a couple months, we have been doing it online in this wiki,” said Col. Charles J. Burnett, the director of the Army’s Battle Command Knowledge System. “The only ones who could write doctrine were the select few. Now, imagine the challenge in accepting that anybody can go on the wiki and make a change — that is a big challenge, culturally.”
It sounds like the reaction within the Army has been all across the map, some viewing it as an extremely progressive step forward to others thinking the idea is totally crazy. But top Army leadership appears to be behind the idea. Again from the article:
The idea has support at the highest ranks. Lt. Gen. William B. Caldwell, the commander of the Combined Arms Center at Fort Leavenworth, Kan., wrote on the center’s blog on July 1, that “by embracing technology, the Army can save money, break down barriers, streamline processes and build a bright future.”
Here at Dark Matter Matters, we give this idea a huge +1. The army is employing some of the same principles we open source folks have employed to great success. A few key parts of the open source way applied here:
Red Hat culture tip: default to open
After 10 years at Red Hat, I’ll admit I am a little bit out of touch with what the corporate world looks like everywhere else. But after a recent conversation with someone out there in the non-Red Hat universe, I thought I’d pass on a quick tip they found helpful on how to create a more collaborative culture in your organization.
Tom Petty sez you should go "into the great wide open..."
The tip is simple. Default to open. Everywhere.
What does this mean? It means rather than starting from a point where you choose what to share, you start from a point where you chose what not to share.
You begin sharing by default.
A quick example. Our group was lucky enough to (thanks to our talented global facilities director, Craig Youst) have the opportunity to help design our own office space. As part of the space design, we determined that we wanted no offices– everyone would be in a large, open collaborative space.
Everyone had the same sized cubes, and it didn’t matter how much of a muckety-muck you were or weren’t. If you wanted to have a private conversation, the space design included a series of private alcoves, where you could go talk with your doctor, or yell at your wife, or whatever you didn’t want to do in public. But the key is that you had to actively decide when placing a call, do I want to take this in private? Which is counter than the old-skool office design where you had an office with a door, and all conversations were private by default.
Summer reading list for Dark Matter Matters
Ah, vacation… the time when the work shuts down for a few days and the Dark Matter Matters blog comes out of hibernation… 3 posts in 3 days!
A few months ago I wrote a post where I highlighted the top ten books behind Dark Matter Matters. In that post I promised to create a list of the books that didn’t make the top 10 cut, but are still pretty awesome.
So here, to celebrate the long holiday weekend, are some more books that have inspired Dark Matter Matters.
Books about how large-scale collaboration is pretty much the deal:
Wikinomics by Don Tapscott and Anthony Williams
The Wisdom of Crowds by James Surowiecki
The Starfish and the Spider by Ori Braffman and Rod Beckstrom
In the open source world, there’s a legendary quote attributed to Linus Torvalds (yes, he is the guy that Linux is named after) “Given enough eyeballs, all bugs are shallow.” The first two of these books are the extended dance remix of this quote. Each has a unique take, but both show how mass collaboration is changing everything about our society and the way we solve problems. The Starfish and the Spider is a interesting look at leaderless organizations and is a nice book for anyone trying to understand how the open source movement (and other leaderless organizations) work, and why open source is so hard to compete against. It is also a nice complement to the Mintzberg article I wrote about in my previous post.
Folks, we have transparency and it’s at data.gov
There was a short article in the New York Times the other day about a quietly launched new government website called data.gov. The purpose of the site is to collect the amazing wealth of information created in the agencies of the US government in one place and make it freely accessible to anyone.
We open source-minded folks think that is just swell. In fact, this subject has been of interest to me for a long time. When I was right out of college and working for the literary agent Rafe Sagalyn, we actually wrote two books intended to help people find the great information the government was putting together for us, but not doing a good job actually getting to us.
The first was a book called Uncle Sam’s Guide to the Great Outdoors, which told you how and where to write or call the government to get information sent to you before you planned a trip into the American wilderness: national parks, forest, wildlife preserves, and whatnot.
It was all great until this dumb Internet thing came along and made it easy for people to access this sort of information online. Now that book is a relic of a bygone era of phone calls and manila envelopes.
But actual government datasets… that’s a much more complicated issue. Until now, it’s been very hard to get broad, searchable access to these datasets without advanced knowledge or tools. And they’ve certainly never been in one place and one standard format before. Data.gov is just a start, but I love the philosophy of the site so much I’m including it here:
Hey, I Wrote a Book!
Available now in print and electronic versions.
Dark Matter Matters 