Interesting article in Forbes the other day about the way Threadless, the awesome t-shirt company, thinks about community-building. For those of you who aren’t familiar with Threadless, they do about $30 million in revenues with a unique cultural/business model that merges a community of t-shirt creators and consumers into one happy family (you can read more about them in the Forbes article).
This quote from Cam Balzer, the Threadless VP of Marketing, in particular, caught my eye:
“Crowdsourcing is antithetical to what we’re doing. That’s because crowdsourcing involves random sets of people who suddenly have a say in how the business works, but that’s not how Threadless operates. We’ve got a close-knit group of loyal customers and have worked hard to build that. The people who submit ideas to us, vote and buy our products aren’t random people, and they aren’t producing random work. We work closely with our consumers and give them a place on our site, the Threadless forum, where they can exchange ideas with one another–ideas that go beyond designing T-shirts. We have consumers who have voted on 150,000 designs, which means they’ve spent hours interacting on our site. People who do that aren’t jumping into a random crowd. They’re part of the community we’ve cultivated.”
This really hit the nail on the head for me. I often see the word crowdsourcing being used in the same sentence with open source or community building. But the word crowdsourcing doesn’t describe the type of community I like to be involved in. Here’s why:
Well folks, there are gonna be some changes around here in 2010. So let me cut to the chase.
After 10 1/2 years, I’m leaving my full-time position with the greatest open source company in the world later this month.
This was no easy call. Red Hat has been a fantastic ride. I’ll spare you the trip down memory lane, but Red Hat has been the defining job of my career.
I certainly wouldn’t leave Red Hat to join another big company. In fact, thanks to DeLisa Alexander, my wonderful boss, and Jeff Mackanic, my long-time partner in running the Brand Communications + Design group, I’m going to continue to work with Red Hat– just in a different capacity. More on this later.
I’ve always wanted to start my own company, see how entrepreneurship fits, and have never had a good opportunity before. In 2010 I believe we are entering one of the most exciting opportunities for entrepreneurs in decades. I aim to give it a go.
As folks who’ve been reading Dark Matter Matters know, I have a deep interest in seeing how the lessons of open source might be applied to companies outside of the technology industry. I’m excited about taking some of the principles we’ve used to build brand, culture, and community the open source way at Red Hat and finding other companies who could use them too.
To that end, the news that won’t be a surprise to folks who know me well: I’ve decided to join up with two of my best friends, David Burney and Matt Munoz, who have spent the last year building a new kind of communications firm– New Kind.
David and I have worked together for almost 10 years, first when he owned Burney Design and was Red Hat’s creative agency partner, then as my boss at Red Hat for 4+ years. And, of course, he and I still play together in our band The Swingin’ Johnsons.
Matt and I first met while he was working on the Red Hat account at CapStrat. He was an early architect of the modern Red Hat brand identity, leading projects like the Red Hat brand book and the Fedora logo design.
As for New Kind, we have a lot of ideas.
So rather than stretching this post too long, I’ll promise to continue to share my ideas here at Dark Matter Matters if you promise to continue to read.
Thanks to my amazing Red Hat family, especially my brothers and sisters in the Brand Communications + Design team, for 10 great years. The hardest part of this decision was knowing I would no longer be sitting beside you five days a week.
Happy new year, and thanks to each of you for making the first year of Dark Matter Matters a special one.
A New Kind awaits!
On the heels of last week’s White House Jobs and Economic Forum, President Barack Obama announced a series of job creation ideas today in a speech at the Brookings Institution.
As I mentioned in my last post, Red Hat’s Jim Whitehurst was one of two technology industry CEOs who attended the White House forum last week, the other was Eric Schmidt from Google. Two things Red Hat and Google have in common? We are both strong supporters of open source and we are both hiring.
But this morning I had another thought– beyond the jobs at Google and Red Hat, are we– and other companies in the open source community– helping create jobs at a broader level? Meaning, are the products, services, and innovations of open source companies creating job opportunities for people who use what we make?
To find some data, I turned to Indeed.com, a search engine for job seekers that also has a fascinating job trends tool you can use to search on how often a particular term appears in job listings.
As a baseline data point, I looked at the chart for “receptionist,” a common job that might be a decent bellwether for job trends. The chart looks pretty much like you might expect:
Not great news for any receptionist looking for work. This term had once appeared in almost 2% of job postings, now it is hovering right below 0.8%.
Next, for some overall industry perspective, I looked at their page on Information Technology job trends. Not a lot of good news here either, unfortunately. These two pieces of information were disturbing:
Our video called the Red Hat Way starts:
“Your mother was right. It’s better to share.”
There’s more proof that your mom was right in the business world every day. Today in Orlando, experts from around the world are gathering for the inaugural Open Innovation Summit, highlighting companies like Proctor & Gamble, Mozilla, Xerox, and Johnson & Johnson who have seen success with collaborative innovation. My company, Red Hat, has also done pretty well with this approach.
Now, in a new working paper released yesterday entitled Modeling a Paradigm Shift: From Producer Innovation to User and Open Collaborative Innovation, Eric von Hippel and Carliss Baldwin examine the body of research to draw some conclusions about why more people are moving away from simple producer/consumer models to open collaborative innovation models.
You may have heard of Eric von Hippel, one of the world’s leading experts on open innovation. I like that he’s written about open source many times before, including in his 2005 book Democratizing Innovation and in his 2002 HBR paper Customers as Innovators.
In this paper, von Hippel and Baldwin argue that the number of places where traditional 20th century “producer” innovation (companies making products for users without collaborating with them) makes sense is rapidly shrinking. Why? From the paper:
When I first started this blog, my hope was to create a home for an open source perspective on brand, culture, and community issues in communications and business.
I figured there might be some people out there in business-land who don’t really understand all this open source stuff too well, and would like to hear more about how the open source way might apply to the issues they face in their work. After all, lots of folks are writing about open source in the macro business context (Chris Anderson, Malcolm Gladwell, Gary Hamel, Tom Peters among many others), but not too many of them work inside an open source business.
I have a sense from the comments I get that there are quite a few readers who have already drank the open source kool-aid too (thank you, friends!). I may not always have as much to offer you, but I love getting your comments and ideas because they make me work harder, give me new ideas, and they often force me to challenge my thinking about open source.
I definitely want to understand who is coming here a bit better. So today, a simple question– who are you?
Thanks for responding, hopefully it’ll help me make this a more interesting place!
Over the past few weeks, Gary Hamel has written two posts on his Wall Street Journal blog about his next book (the posts are here and here). The catch? He’s decided that he isn’t going to write another book. So instead, he published the CliffsNotes version of what he’d write if he was going to write a book, and started what he refers to as an “open source project” about the ideas, inviting people to add their thoughts and comments.
I thought I’d share some of my favorite bits that fit in really well with a Dark Matter Matters world view.
On what it means to be an adaptable company:
An adaptable company is one that captures more than its fair share of new opportunities… An enterprise that is constantly exploring new horizons is likely to have a competitive advantage in attracting and retaining talent. When a once successful company runs aground and starts to list, its most talented employees usually don’t stick around to bail water, they jump ship. A dynamic company will have employees who are more engaged, more excited to show up to work every day, and thus more productive… Adaptability didn’t rate very highly as a design criteria when those early pioneers set out to invent Management 1.0 a hundred years ago. But it’s essential now…
On the problems with big organizations:
Big things aren’t nimble. That’s why there aren’t any 200-pound gymnasts or jumbo-sized fighter jets… In a company comprised of a few, large organizational units, there tends to be a lack of intellectual diversity—since people within the same unit tend to think alike. Within any single organizational unit, a dominant set of business assumptions is likely to emerge over time. One way of counteracting the homogenizing effects of this groupthink is to break big units into little ones. Big units also tend to have more management layers—which makes it more difficult to get new ideas through the approval gauntlet. In addition, elephantine organizations tend to erode personal accountability.
Earlier this summer at the Sasquatch Music Festival, someone captured the three minute video I’ve pasted below. One guy dancing to M.I.A. (we love her!) starts what becomes a massive dance mob by the end of the song. The video became an YouTube sensation, with over 2,000,000 views.
Many folks have written interesting posts analyzing the event (here are a few of my favorites) and at some point you’ve gotta stop analyzing and realize this man just needed to DANCE and maybe the rest of us do too. But before we do that, a couple of observations from the place where open source community-building intersects with Sasquatch guy dance mob-building.
Over the past month or so, I’ve been having a conversation with Iain Gray, Red Hat Vice President of Customer Engagement, about the ways companies engage with communities. I’ve also written a lot lately about common mistakes folks make in developing corporate community strategies (see my two posts about Tom Sawyer community-building here and here and Chris Brogan’s writeup here).
One idea we bounced around for a while was a mashup of community thinking and Maslow’s hierarchy of needs. For those of you who slept in with a bad hangover the day you were supposed to learn about Maslow in your intro psych class (damn you, Jagermeister!), here is the Wikipedia summary:
“[Maslow’s hierarchy of needs] is often depicted as a pyramid consisting of five levels: the lowest level is associated with physiological needs, while the uppermost level is associated with self-actualization needs, particularly those related to identity and purpose. The higher needs in this hierarchy only come into focus when the lower needs in the pyramid are met. Once an individual has moved upwards to the next level, needs in the lower level will no longer be prioritized. If a lower set of needs is no longer being met, the individual will temporarily re-prioritize those needs by focusing attention on the unfulfilled needs, but will not permanently regress to the lower level.”
Now granted, the needs of a company are very different than the needs of a human being. At its very basic level, a company has a “physiological” need to make money. If that need is not being met, little else will matter. But in an ironic twist, this basic need to make money can actually hinder the company’s ability to make money if it is not wrapped in a more self-actualized strategy.
To explain what I mean, think about the last annoying salesperson who called or emailed you. Why were you annoyed? Probably because it was very clear to you that the salesperson was badly hiding his basic motivation to make money. He wasn’t talking to you because he valued you– he was talking to your wallet.
Now think about the best recent sales experience you’ve had. Mostly likely, this salesperson was being motivated by a higher purpose, perhaps something as simple as a desire to make you happy. Sometimes the most effective salespeople aren’t even in sales at all– like a friend who tells you about a new album you should buy, for example. Or sites like Trip Advisor, where you can learn about where to go on vacation from other folks like you.
When it comes to community strategy, most companies have trouble finding motivation beyond the simple need to make money– and the communities they interact with can tell.
Yet if you look at the greatest companies out there, you’ll find that they usually have a strong sense of identity and purpose– just like Maslow’s self-actualized people. Read anything by Jim Collins and you’ll see what I mean.
For a recent presentation, Iain developed a chart that looks a lot like the one below. And to embarrass Iain, let’s call it the Gray hierarchy of community needs.
Most Twitter users have probably heard of the Twitter tradition of Follow Friday, where you take time on Fridays to introduce your friends to some folks they should be following. Well, I’m lucky to be working alongside some awesome people here at Red Hat, and I thought today I’d introduce you Dark Matter Matters readers to ten Red Hatters who say some pretty smart things online.
First, meet three members of the Red Hat Community Architecture team. If you are interested in the Red Hat approach to community-building, check out these three rock stars. When it comes to understanding how to build an effective architecture of participation, very few people have more experience or good ideas than Greg, Max, and Karsten.
1) Greg DeKoenigsberg: Blog | Fedora page | Twitter feed
2) Max Spevack: Blog | Fedora page
3) Karsten Wade: Blog | Fedora page | Twitter feed
As a special bonus, I’m going to introduce you to the newest member of the Community Architecture team, Mel Chua. From what I can tell, Mel may be teaching those three old guys a thing or two about how the next generation will be building community.
Red Hat has a quite a few folks with a deep passion for open source, but when Michael Tiemann, Jan Wildeboer, Venky Hariharan, and Gunnar Hellekson enter the room, their passion takes your breath away (example: I think Jan got a Red Hat tattoo last night– that is passion, man). These guys are great ambassadors for Red Hat, but also for the entire open source movement. Don’t expect any of these four to just toe the corporate line, though– each of them has interests and ideas that extend well beyond the corporate walls.
5) Michael Tiemann: Blog | Web page | Wikipedia entry
6) Jan Wildeboer: Blog | Identi.ca | Twitter
7) Venkatesh Hariharan: Blog
8) Gunnar Hellekson: Blog | Twitter
And finally, closer to home, I want to point you to a couple of folks in the Brand Communications + Design team that I think are doing some really great stuff online. First, my friend and 10-year Red Hat colleague Jonathan Opp, who has begun actively posting on his blog about brand, voice, design, and culture. You will not meet a more talented writer.
9) Jonathan Opp: Blog | Twitter
The last person I want to point out today is BC+D designer Adrienne Yancey. But it’s not her Red Hat work I want to point you to– instead, it’s a really cool blog she writes about food in her spare time. Her photography is beautiful, and it is worth visiting just to drool over the pictures of edamame salad and okra.
10) Adrienne Yancey: Blog
OK, that’s it for today. I’ll try to highlight some other Red Hat folks doing cool stuff online in a later post. After all there are over 3000 of us now working in about 30 countries around the world– there are plenty of great people and ideas to show you.
At lunch today, I sat in on a presentation by Red Hat community architect Karsten Wade about open source community-building best practices. Karsten referenced a concept he attributed to Greg DeKoenigsberg, who I believe may be the most talented community architect on the planet. The idea was crazy simple, and it was the first time I’d heard it:
Think of good community work as money you’d put in a bank.
Do really helpful things in the communities you participate in, things that make those communities more successful. If you continue to make these positive karma deposits for a long period of time, the balance in your community karma account will go up. Why do you want a lot of good karma in your account?
For a rainy day, of course!
Every company has times when, for one reason or another, they can’t (or don’t) put their best foot forward. Even the best community citizens (and Red Hat is one of the best, according to Matt Asay “Red Hat is considered the paragon of open-source virtue.”) have bad days.
That is precisely when you make a withdrawal from your community karma account.
If your balance is high, you are more likely to get the benefit of the doubt when trouble arises. If your balance is low or you have a negative balance, well, not so much. If you start making too many withdrawals (i.e. doing a lot of dumb stuff) and don’t make enough deposits, you will start having problems effectively engaging in that community.
I don’t know how that could be any simpler. Or more true. Nice one, Greg.