From the we’ll-all-be-working-for-him-someday files:
Former Red Hat intern and project manager Tim Hyer has been working on a new startup company named Rentcycle. Last night, Techcrunch picked up their story here. Tim worked for us here in the Brand Communications + Design group at Red Hat from 2005 to 2007 and then moved out to the west coast. He is the person most responsible for the hard work of making David Burney‘s design thinking vision come true at Red Hat.
Rentcycle a pretty neat idea– sign up rental businesses around the country, and then let people rent stuff from one website. See what is in stock at many stores at once, without having to run around a dusty warehouse looking in rusty bins full of candelabras and fine silverware.
Some other folks have tried similar things, but many have tried the Craigslist style approach of one consumer renting to another. Tim’s approach is more B2C (in non-marketing-speak, that means he wants to partner with businesses selling to regular folks), which should make it easier for him to achieve scale without as much pain. My view? Someone’s going to do this right, and knowing Tim, it’s a pretty good bet it will be him.
Follow them on Twitter here or watch their video pitch of the concept (nice stick figure, Tim):
My colleague John Adams, reporting from the World Business Forum in New York, wrote on Twitter yesterday that during his speech, management guru Gary Hamel called open source one of the greatest management innovations of the 21st century (coverage of Gary’s speech here and here).
I love it. Gary Hamel is a hero of mine, and many consider him one of the greatest business minds on the planet. I’ve written about him, well, too much (start here, here, and here), and I follow him via his website, his non-profit called MLab, and his Wall Street Journal blog.
I knew Gary was familiar with open source after reading his book The Future of Management (one of the top ten books behind Dark Matter Matters). He spends five pages (205-210 in the hardcover) discussing open source and at one point says the following:
The success of the open source software movement is the single most dramatic example of how an opt-in engagement model can mobilize human effort on a grand scale… It’s little wonder that the success of open source has left a lot of senior executives slack-jawed. After all, it’s tough for managers to understand a production process that doesn’t rely on managers.
Here’s his analysis of why the model works so well:
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.
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.
On Twitter yesterday, my friend Chris Blizzard mentioned to someone that I often say “brands are like sponges.” When I saw this, I realized that a) I haven’t said this in a while and b) I should say it more often because it is a freakin’ awesome way to think about brands. So I’m saying it again right now. Right here.
It’s actually not my line. I got it from the Scott Bedbury book A New Brand World (one of the top ten books behind Dark Matter Matters). Near the beginning of the book, Scott, who is one of the masterminds behind the good ol’ days of the Nike brand in the 80s and the Starbucks brand in the 90s, provides one of my favorite definitions of what a brand is:
A brand is the sum of the good, the bad, the ugly, and the off strategy. It is defined by your best product as well as your worst product. It is defined by award-winning advertising as well as by the god-awful ads that somehow slipped through the cracks, got approved, and, not surprisingly, sank into oblivion. It is defined by the accomplishments of your best employee– the shining star in the company who can do no wrong– as well as by the mishaps of the worst hire that you ever made. It is also defined by your receptionist and the music your customers are subjected to when they are placed on hold. For every grand and finely worded public statement by the CEO, the brand is also defined by derisory consumer comments overheard in the hallway or in a chat room on the Internet. Brands are sponges for content, for images, for fleeting feelings. They become psychological concepts held in the minds of the public, where they may stay forever. As such, you can’t entirely control a brand. At best you can only guide and influence it.
Those last two lines have stuck in my mind since I first read them. First, the idea that a brand is a sponge, soaking up everything, both good and bad. And second, that you cannot control a brand, you can only guide and influence it.
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?
When I talk about the culture that we’ve built at Red Hat over the years around the principles of the open source way, one of the most popular questions I get is something along these lines.
That’s great and all, Chris. But Red Hat built its culture from scratch. My company culture has been the same for over 50 years. Can you change a deeply entrenched 20th century culture?
It’s a great question. Clearly there is a big advantage to being able to organically build a corporate culture from scratch. But, with support from the top levels of management, it is not impossible to change an entrenched culture, too.
Where do you start? Here are three tips:
Picture this: You are sitting in a meeting, and someone from another department is beating you up because you won’t go along their vision. They’ve never asked your for your opinion, they didn’t involve you in their process, and now you are sitting there getting railed because you are not sure what they are pushing is the right thing to do.
And then it comes. You get accused of not being collaborative.
You were just a victim of clobberation.
Clobberation [klob-uh-reh-shun] (n)
The art of beating someone into submission under the guise of collaboration.
I first heard this term from my friend Todd Barr a few years ago, and it’s stuck with me ever since.
Especially for us open source folks, who think of true collaboration as something almost holy, getting clobberated is really, really painful. And the hard part? It is sometimes difficult to articulate how someone clobberated you, but you almost always know it when you feel it. You feel anxious, cheated, even guilty.
So what’s an honest collaborator to do?
At Red Hat, I often get questions about how we name stuff. It is usually not just idle curiosity, mind you, in most cases someone has a new program or product and would like to call it something like Supersexyshinyfoo. Our team has to play the bad guy role and explain that we don’t usually create new brands like that at Red Hat.
The response is typically something like “Let me get this straight… You guys think long, boring names like Red Hat Enterprise Linux, Red Hat Enterprise Virtualization, and JBoss Enterprise Application Platform are better than Supersexyshinyfoo?”
My answer? We already have a Supersexyshiny… it’s the Red Hat brand.
We’ve spent years building the Red Hat brand into something that people associate with (according to our surveys) value, trust, openness, choice, collaboration, and a bunch of other neat things. Studies have shown that Red Hat brand karma is pretty positive. And the logo looks great on a t-shirt. Our brand is one of our most valuable assets.
This is why most Red Hat products have very descriptive (some would say boring…) names. The equation probably looks something like this:
(Supersexyshiny + Foo) = (Red Hat + descriptive name)
This brand strategy is often referred to as a “branded house” strategy. Take one strong brand, plow all of your brand meaning into it, while differentiating each product with descriptors instead of brand names.
These days, many automobile manufacturers do things this way. Remember when Acura used to have the Acura Integra and the Acura Legend? Honda simplified the branding strategy by moving to RL, TL, TSX, etc. as descriptors for their cars, pointing all of the brand energy back at the Acura brand. Many other auto manufacturers follow similar principles.
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:
Last week I was on a panel with Chris Brogan, author of (with Julien Smith) the NY Times bestselling book Trust Agents. Also on the panel were Robert Cook (founder of Freebase and Metaweb), Gary Slack (Chairman of Slack Barshinger and head of the Business Marketing Association), and June Arunga (partner at Black Star Lines and one of Fast Company’s 100 Most Creative People in Business). The panel was moderated by Sree Sreenivasan (Dean of Student Affairs at Columbia Journalism School and regular TV commentator).
After looking up the kickin’ credentials of each of these folks, I figured I’d better get my act together and do some research so I wouldn’t immediately out myself as the weak bulb. As part of my homework, I picked up a copy of Trust Agents to read on the plane.
Now I must admit, I’m not a big fan of most books about social media stuff. I think I may be allergic to what I call social media meta-marketing: people using social media to show others how much they know about social media. If all the people using social media to talk about social media just shut up for a minute, we’d probably save Twitter some serious bandwidth expense. But I digress…
So I buy this book, sign up for Chris’s Twitter feed, all the normal stuff. It turns out Chris has almost 100,000 followers on Twitter, and almost every post on his blog gets like 50 or 100 comments (and most of them seem really nice and friendly, us open source folks aren’t used to that).
His Twitter feed almost looks like a breathing rhythm, with tweets coming in and out every few seconds. You could probably even calculate how much sleep he gets by putting the times of his first and last tweets of the day for a month in a spreadsheet and averaging out the results. If I hadn’t seen him sneaking some tweeting in under the panel table via his phone, I’d guess TweetDeck was directly wired into his brain.
OK, cut to it. The book is great. I really dug it. It turns out it isn’t so much about social media as it is about building relationships, building trust, being helpful, being useful, being nice, and a bunch of other stuff your mom told you to do when you were younger. After reading the book and spending an afternoon with Chris, it’s pretty obvious how he’s been so successful. He’s just really, really freaking nice.
From the book, here is his strategy: