culture

Why is this blog called Dark Matter Matters?

Over the past couple of weeks, I’ve had a few people ask me why my blog is called Dark Matter Matters, and since I haven’t told that story in a while, I thought I’d share an excerpt from The Ad-Free Brand explaining it (and appending some more recent information). Here goes:

In late 2008, I was struggling mightily with the question of how you measure and quantify the value of brand-related activities. As someone whose father is an amateur astronomer, I’d long been intrigued by the concept of dark matter in the universe. If dark matter is new to you, Wikipedia describes it as “matter that neither emits nor scatters light or other electromagnetic radiation, and so cannot be directly detected via optical or radio astronomy.”

In other words, it is matter out there in the universe that is incredibly difficult to see, basically invisible, but that has a large gravitational effect. What’s particularly interesting about dark matter is that, apparently, there is a lot of it. Again according to Wikipedia:

“Dark matter accounts for 23% of the mass-energy density of the observable universe. In comparison, ordinary matter accounts for only 4.6% of the mass-energy density of the observable universe, with the remainder being attributable to dark energy. From these figures, dark matter constitutes 83% of the matter in the universe, whereas ordinary matter makes up only 17%.”

I find this fascinating.

And dark matter is still a theoretical concept. Again from the Wikipedia entry: “As important as dark matter is believed to be in the cosmos, direct evidence of its existence and a concrete understanding of its nature have remained elusive.”

But it was actually reading about all the problems with the Large Hadron Collider in 2008 (at the very same time I was having my own problems figuring out how to measure the value of brand-related work) that helped me make the connection between what I do for a living and this concept of dark matter.

The Large Hadron Collider is the world’s largest particle accelerator. It was built on the border of France and Switzerland and is about 17 miles wide. One of the things that particle physicists hope to prove with this enormous project is the existence of dark matter.

I’m no physicist, but as I understand it, the accelerator shoots protons at super-high speeds around the collider, and, if these scientists are lucky, the collisions eventually might produce a few particles that will exist for only a few milliseconds and then disappear again. And these particles might prove that dark matter isn’t just a theory.

Might being the key word. In fact, noted physicist Stephen Hawking bet $100 that they won’t find anything (a bet which he may soon win). The cost of building a collider to maybe prove the existence of dark matter? About $9 billion dollars. (And as of this post, written in September 2011, three years since its was first fired up, we are still looking for evidence.)

Another attempt to prove the existence of dark matter used the Hubble Space Telescope. This image below (which I also used for the header of the blog) was taken by Hubble and first shown by NASA in May, 2007.

In this picture, you are looking at many galaxies a really, really long way away. But you can also see fuzzy gray areas all over that look like clouds. When the astronomers first looked at this photo, they thought the fuzzy areas were a problem with the image. But after analyzing it for over a year, they realized that the fuzziness might actually be evidence of dark matter.

Their reasoning? The fuzziness is actually a gravitational distortion of the light rays from distant galaxies that are being bent by dark matter on their way to Earth. The effect you see is kind of like looking at the bottom of a pond that is being distorted by ripples on the surface.

So finally, scientists had discovered some real visual evidence of dark matter.

I believe the type of activities I talk about in the book and on this blog—those related to building brand, culture, and community—are the dark matter within organizations. Often brand, culture, and community are extremely difficult to measure well, and sometimes accurate measurement is simply impossible.

That’s not to say we don’t try anyway. I’ve seen and even tried many formulas, processes, and products that attempt to measure the value of brand, community, and culture-related efforts. Some of them can provide valuable information.

Others, not so much.

Yet here’s the kicker: brand, community, and culture are having a huge impact on your organization, whether you can effectively and cost-effectively measure that impact or not.

Just as dark matter is a strong gravitational force within the universe even though it is notoriously hard to see and measure, so are many of the things that will lead to the long-term success of ad-free brands.

So that’s how the blog got the name.

One last thing: I’ve been toying with the idea of changing the name at some point down the road, perhaps re-naming it The Ad-Free Brand and simplifying things. If you have any thoughts on that, or if you like the dark matter analogy and think I should keep it, I’d love your opinion. Feel free to comment below or send me an email at chris(at)newkind.com.

Mozilla: A study in organizational openness

My theme this week is organizational openness and transparency and today I’d like to highlight a fantastic example of an organization that has built a culture with openness at its core: Mozilla.

Most of you probably know Mozilla as the organization famous for its open source Firefox web browser. But what you may not know is that open source is more than just a technology decision for Mozilla; the open source way is deeply ingrained in every aspect of its culture.

Last week, Mozilla Technology Evangelist Paul Rouget wrote a post on his blog entitled Mozilla Openness Facts. In it, he attempts to capture as many examples of openness in action at Mozilla as he can.

Here are just a few of the examples Paul shares (read his post if you want to see the rest):

1. An open door office policy: open source contributors are welcome to drop by Mozilla offices and hang out. In fact, Paul notes that he first met current Mozilla CEO Gary Kovacs (before he joined Mozilla) when Gary visited the Paris office where Paul works.

2. Transparent financials: Sure, many companies publish their financial results publicly… because they are public companies. Mozilla isn’t, but still does.

3. Open meetings: No strategy behind closed doors here. Not only are many of Mozilla’s meetings open to the public, they often post the phone numbers (and even video conference URLs) on their wiki.

4. Public product roadmap: Want to know Mozilla’s future technology direction? No need to hire a private investigator, you can find the product roadmap on the wiki too.

Not all of these examples are unique to Mozilla and some of them are simply a part of being a responsible member of the open source movement. But what is unique is that someone took the time to catalog the openness examples.

It’s a fantastic idea, and perhaps something that every company that bills itself as open should attempt to do in a public forum.

I reached out to Paul to ask him a few questions about openness and what motivated him to compile the list of examples. Here are some highlights from our conversation:

First, I asked him about some of the challenges that come with openness and transparency. One of the points he made that resonated most with me is that “being open is not a passive task.” It isn’t enough just to make information open—you must be active about helping people find it.

“Open meetings are meetings where anybody can come. But you have to promote these meetings. Make sure the contributors hear about them. Same for mailing lists and IRC channels, open channels, but you need to find them… Just keeping the doors open is not enough,” says Paul.

Paul also pointed out another crucial lesson of organizational openness, that being open doesn’t mean everyone has the right to vote on everything.

“Being transparent and open doesn’t mean we are a democracy. We listen to everybody, but we believe that the most skilled people should make the most important decisions. And you don’t have to be an employee to be a decision-maker.”

Finally, I asked him why he took the approach of “showing vs. telling” in writing the post (which I loved, very esse quam videri). Here was his response.

“I was trying to define openness. I failed. Much easier to show. Everybody is talking about how transparent and open they are. Even big and closed companies. I say b$%^&*!t, they are not. They just use openness as a new buzz word and a new marketing thing. If you are open, show me your meeting notes, show me your source code, let me be part of your team conference calls, let me look at your metrics, and let me work with you.

I wanted to show that being open is much more than just being open source.”

Well shoot, that sounds a lot like what we are trying to show with opensource.com:)

Nicely done, Paul. Nicely done, Mozilla.

[This post originally appeared on opensource.com]

How open and transparent can a public company really be?

On opensource.com, we often talk about the benefits of an open, collaborative approach, and I see new stories every day that help showcase the benefits of an open organizational model.

But for public companies, the benefits of an open approach are often overshadowed by the risks. During my time at Red Hat (a publicly-traded company for much of my tenure), our approach was traditionally to “default to open,” sharing as much information as we could, both inside the company and with the outside world.

Yet, as a public company, there were many financial and legal obstacles that stood in the way of openness. It was challenging to find the right balance between being open with our thinking and information, yet respectful of the legal and financial responsibilities that come with being a public company.

So it was with great interest that I read Scott Weiss’s recent post about corporate transparency on Ben Horowitz’s blog (also posted at AllThingsD). Scott is now a general partner of Andreessen Horowitz, but was previously the CEO of IronPort, an Internet security company that was acquired by Cisco in 2007.

In his post, Scott talks about making the decision to build an open culture at IronPort, despite the risks:

“…the more that I thought about it, the more I believed that sharing absolutely everything would create massive advantages and that we should live with whatever consequences resulted.”

So he went ahead and did it. Yet, as soon as IronPort began to prepare for its IPO, the company was forced dial back the transparency. I’d encourage you to go check out the post for the full details of how they handled this transition. But the key takeaway at the end of Scott’s piece is one that I could not echo more strongly.

“I believe it was much healthier to set the default to full disclosure while we were private. When you prepare for an IPO, it’s definitely a high-class problem to have to work backwards with concrete reasons to withhold information from the employees. And when that time comes, they totally understand.”

Scott’s right. People totally understand. When you level with them and share as much information as you can by default, then apologize and explain why when you can’t share a piece of information, in my experience, almost everyone will be cool with it.

So if you are working for a company that is thinking about going public one day, and the more conservative folks in your organization are using this as an excuse for not having a more open, collaborative culture, show them Scott’s post.

While complete openness might never be possible in your organization, a respectful, thoughtful default-to-open approach may give you the benefits of an open culture while minimizing the risks.

[This article originally appeared on opensource.com]

In a tough job market, your open source experience may be an asset in more ways than one

Does this describe you?

You’ve been using open source software or contributing to open source projects for a long time. Perhaps you are in a job where you utilize open source tools regularly, or maybe you are just fooling around with them for fun or to learn new skills.

You’ve been known to tell (possibly true) stories that highlight how long you’ve been a part of the open source world (from “I remember downloading the first version of Fedora” to “I was in the room when the term open source was coined”). But, most importantly, you consider yourself an active member of one or more open source communities.<img title=”” src=”http://opensource.com/sites/all/modules/wysiwyg/plugins/break/images/spacer.gif&#8221; alt=”” />

Did you ever consider that your time spent participating in these open source communities might be more than just good technology experience? That it might prepare you for jobs completely unrelated to using or making software?

In college, I studied history and political science. Not because I wanted to be a political scientist or a historian but because, well… actually I’m not really sure.

But in retrospect, I’m really happy I studied these fields.

Why? They gave me plenty of experience doing research, writing, and learning to articulate my thoughts and ideas effectively. While I don’t remember how Alexander the Great defeated the Persians at the battle of Issus and I can no longer compare and contrast the views of Rousseau and Locke effectively, I use many skills I learned when studying these subjects on a daily basis.

At the risk of sounding like an advertisement for a liberal arts education, let me get to the point.

While you’ve been happily participating in open source communities because you have a need for a piece of software or want to help make it better, you may also be the beneficiary of an important side effect. You may be getting experience in how organizations of the future will be run.

Over the past few years, I’ve had an opportunity to work with organizations in many different industries, including finance, education, service, hospitality, even in the government and non-profit worlds. Many of these organizations are busy exploring how they can better compete using techniques that many of us in the open source world have already successfully put into practice.

For example, some are interested in testing large-scale collaborative projects involving people outside their organizations. Others want to know how to create internal meritocracies where people feel empowered and the best ideas can come from anywhere. Others want to begin to form more meaningful relationships with the community of people who care about their organizations. If you’ve been reading opensource.com, you’ve seen us highlight many examples in business, government, education, health, and elsewhere.

These organizations have a lot to learn from those of you who already have real experience using these practices in real communities.

In his book Outliers, Malcolm Gladwell introduced the idea that those who became world-class practitioners at their craft (he uses examples like Mozart, Steve Jobs, and the Beatles), have done so in part because they were able to get an inordinate amount of practice before others in their field. According to the research Gladwell cites in the book, a person needs about 10,000 hours of practice to achieve mastery.

How close are you to putting in 10,000 hours participating in the open source world? If you’ve spent 40 hours a week working in open source communities for 5 years, you may have your 10,000 hours in already.

But even if you don’t yet have 10,000 hours, my guess is you’ve already learned quite a bit about how open source communities work.

So if you believe that the organizations of the future may be run using many of the same principles that are currently being used to great effect in open source communities, and you already have plenty of experience working within those communities, could you be an asset to an organization that is looking for better ways to compete? And could you be an asset not just because of your open source technology skills, but also because of your open source thinking skills?

An example: My friends Dave Mason and Jonathan Opp, who each have well more than 10,000 hours of experience in the open source world, recently entered the joint Harvard Business Review / McKinsey M-Prize contest on the Management Innovation Exchange with a hack deeply inspired by their open source experience.

Their idea? Take the principle of “forking” as practiced in open source development projects and apply it to the way organizations are managed (read the full details of their hack here). Their “Free to Fork” hack was recently selected from a pool of almost 150 entries submitted by people from around the world as one of 20 finalists for the M-Prize. Pretty impressive.

So think about it: Beyond your technology experience, what else have you learned from working in open source communities that might be valuable to a potential employer? Are there hidden skills or ways of thinking open source has taught you that might be worth highlighting in a job interview or in making the case for a promotion or new assignment?

Start thinking of your open source experience as a new set of thinking and working skills that may be very much in demand in organizations hoping to remain competitive in the future.

By doing so, you might open yourself up to interesting opportunities you wouldn’t have considered before.

[This post originally appeared on opensource.com]

Thoughts from the HCI Engagement and Retention Conference in Chicago

Yesterday I had the privilege of participating in two panel discussions at the Human Capital Institute’s Engagement and Retention Conference in Chicago.

I moderated the first panel on behalf of my friends at the Management Innovation Exchange. This panel featured the winners of the first Human Capital M-Prize: Lisa Haneberg of MPI, Joris Luijke of Atlassian, and Doug Solomon of IDEO. The Human Capital M-Prize competition, run jointly by HCI and the MIX, was designed to find bold ideas, stories, and innovations highlighting ways to unleash the passion of people within our organizations.

Lisa began by presenting her winning hack, entitled Start with a better question to create a better talent management system: the Talent Management Cloud. She made the case that the “old kind” model where engagement and retention are owned within the HR function is fundamentally broken. Because there are so many factors well beyond the control and influence of HR alone, responsibility for talent management must be the responsibility of the whole organization. I’d encourage you to go take a look at Lisa’s winning hack if you are interested in learning how to put her more holistic model into practice.

Next, Joris, who came in all the way from Sydney for the conference, took on the performance review– something he described (accurately in my book) as universally hated by both employees and HR people around the world. Joris shared his story of how Atlassian designed a kinder, gentler, more humane performance review system and rolled it out within the organization. You can read Joris’s original story Atlassian’s Big Experiment with Performance Reviews on the MIX.

Finally, since I make no secret of being an IDEO fanboy, I was excited to share the stage with Doug Solomon, CTO of IDEO. Doug shared his winning story, entitled The Tube: IDEO Builds a Collaboration System That Inspires Through Passion. Frustrated by so-called collaboration systems that IDEO found desperately lacking, they took on the challenge of designing their own, using a model based on facilitating person-to-person interaction more akin to Facebook than your typical knowledgebase or database-driven collaboration system. Doug also shared that a company called Moxiesoft has taken The Tube and turned it into a product, which I can’t wait to go check out.

At the end of the session HCI announced a new M-Prize, which will run from now through December 9th. This M-Prize is called “Encouraging the Gift of Leadership” and will be an effort to discover innovative ideas for how we can stimulate and support the development of “natural” hierarchies, where influence comes from the ability to lead, rather than from positional power within organizations. Have a great idea? You should go enter it on the MIX.

Later that afternoon, I participated in another panel where Katie Ratkiewicz of HCI shared the results of a recent survey regarding the relationship between career development efforts within organizations and overall employee engagement. I was joined on the panel by Stuart Crabb, Head of Learning and Development at Facebook, Russell Lobsenz, Director of Talent Development at Orbitz, and Cathy Welsh, SVP of Leadership Consulting at Lee Hecht Harrison.

I was particularly interested to hear Stuart’s comments regarding Facebook’s approach to career development. Basically, his thinking is that career development is primarily the employee’s responsibility (not the company’s) to drive, something that I expect was fairly controversial to many in the room (judging from the data shared in the survey), but which I couldn’t agree with more fully.

While I was excited to hear him say it out loud (because I wasn’t sure whether I’d be driven from the room tarred and feathered if I’d done it on my own), I did acknowledge that there were prerequisites for an approach where employees are accountable for their own career development to work. In my view, there has to be an entrepreneurial culture in place in the organization where employees have the freedom to explore new opportunities. I certainly felt we had those sort of opportunities while I was at Red Hat and it sounds like there is a culture based on freedom and personal accountability at Facebook as well.

I want to thank my new friends at the Human Capital Institute for a great day and some wonderful hospitality. Also thanks to my friends in the MIX community and especially Lisa, Joris, and Doug for participating on the panel. I’ll see all of you again soon!

Want people to embrace the open source way? Don’t talk, do.

The June issue of Harvard Business Review features an interesting article by Roger Martin (one of the leading management minds of our time and author of the just published book Fixing The Game). The article tells the story of how Scott Cook, founder and current Chairman of Intuit, kicked off an effort to reinvent Intuit as a design-driven company.

I’ll leave it to Roger and HBR to share the story of how this initiative played out (hint: a very good case study of how to embed design thinking in the corporate world), but one particular lesson stood out for me that I’d like to highlight here.

When Cook kicked off the initiative, he did so by hosting two-day offsite event for the company’s top 300 managers. As part of this event, Cook gave a five-hour (wow!) PowerPoint presentation, during which he “laid out the wonders of design and how it could entice Intuit’s customers.”

As you might expect, the PowerPoint marathon didn’t go so well. From the article:

“But although the main event fell flat, the one that followed did not. Cook had met a young consulting associate professor at Stanford named Alex Kazaks, whom he’d invited to present for an hour at the offsite. Like Cook, Kazaks began with a PowerPoint presentation, but he ended his after 10 minutes and used the rest of the time for a participatory exercise: The managers worked through a design challenge, creating prototypes, getting feedback, iterating, and refining.

The group was mesmerized…”

This story illustrates something I saw over and over during my time at Red Hat and in many of the projects I’ve worked on since:

No matter how eager you are to get people to embrace the open source way fully—running projects in an open, collaborative, meritocratic way—you’ll have more success convincing people to try doing things the open source way when you stop showing slides and instead get them to experience the benefits in action.

The best way to learn about collaboration is to collaborate.

The best way to learn how to operate openly is to participate in a project run openly.

And the best way to see the power of meritocracy is to participate in a project where the ideas actually do come from everywhere.

So before you spend two weeks preparing a detailed PowerPoint (or OpenOffice) presentation to convince your management team to embrace the open source way, stop and think.

Is there a way you could show the benefits of the open source way in action? Could you run a hands on-project the open source way and invite those you are attempting to sway to participate?

In my experience, people will nod their heads at a presentation espousing philosophy. But you won’t really have their minds until they’ve experienced the open source way in action, and you won’t have their hearts until they’ve thoroughly enjoyed the journey as well.

[This post originally appeared on opensource.com]

What does Google’s management change say about the open source way?

Last week, Google CEO Eric Schmidt announced in a post on his blog he was stepping aside and Google co-founder Larry Page would take on management of Google’s day-to-day operations as the new CEO. Although Schmidt is staying on as Executive Chairman for now and will continue to have an ongoing role in the company, many including myself, were surprised by the news.

I see Google and Red Hat both as fantastic poster children for openness as a successful business strategy. I’ve written many times about how the open source way deeply impacted our work at Red Hat even beyond building software. I’ve also written about Google and the open source way, and pointed to this famous post from Google’s Senior VP of Product Management Jonathan Rosenberg explaining Google’s commitment to openness.

But what does Google’s management change say about the open source way?

Before you answer, here are a few things I’ve read this week and found interesting:

[Read the rest of this post on opensource.com]

BetterMeans: a new app for running your organization the open source way

Last week I received a heads up about a new web application launching today from a company called BetterMeans with an impressive goal: to build the infrastructure (processes, technology, governance, etc.) to make an open organizational structure like we talk about here on opensouce.com a reality.

From their website:

BetterMeans.com is a web platform where people can start and run companies in a new decentralized way.

– Teams self-form, self-organize, and self-manage using an issue-tracking tool
– There is no management class, only natural hierarchies.
– Leadership emerges organically by users earning other users’ confidence
– Compensation is based on contribution
– Strategy and ideas are crowd-sourced
– There’s full accountability and transparency. Relationships are built on trust.
– Ownership is distributed
– Capital allocation and decision-making are decentralized

If a traditional company was a network architecture, it would be client-server.

We’re building a platform for peer-to-peer companies that are more agile, resilient, and innovative.

The video below explains what they are doing and why.

[Read the rest of this post on opensource.com]

My newest hobby: hacking management

My first blog post went up today on the Management Innovation Exchange (MIX).

The MIX is the brainchild of Gary Hamel, author of one of my favorite management books of the last 10 years, The Future of Management, and the guy who the Wall Street Journal ranked as the most influential business thinker in the world.

The thesis of the MIX is that management itself has been a fantastic innovation— the “technology of human accomplishment” to use Hamel’s words. Yet for all management has done to improve the world we live in, it is technology invented over 100 years ago, and old skool management practices are becoming increasingly outdated in the modern world (Gary Hamel explains this all better than I do, watch his short introduction to the MIX below).

The MIX is an open, collaborative effort to reinvent management built around 25 management “moonshots” (see the full list here). In addition to Hamel, there are some amazing folks contributing to the site, including famous visionaries like Terri Kelly of W.L. Gore & Associates and John Mackey of Whole Foods.

But perhaps the most exciting part of the site for me has been to see that it is built as a meritocracy of ideas, where anyone can add a story, a hack, or a barrier. And many do. I’ve seen some amazing ideas as I’ve begun to participate in the MIX over the last few months and can’t wait to point some of them out in my role as a Moonshot Guide.

In particular, I’ll be tackling the moonshot “Enable communities of passion” building on my experiences at Red Hat and here at New Kind as we continue to build a company around the concept of being community catalysts.

So if you have ideas for things you think I should cover, drop me a line, I’d love to hear them.

The open source organization: good in theory or good in reality?

On occasion I get the opportunity to speak publicly about some of the things I’ve learned over the years applying the open source way in organizations.

In almost every case, when the Q&A session arrives, I’m greeted with at least one question from a poor soul who loves the idea of applying the open source way to management and culture, but doesn’t think it would ever work in his/her specific organization. Usually the comment is accompanied by some horror story about an evil co-worker, hierarchical boss, crappy HR policy, or some other impediment that would cause the open source way to fail.

And the sad truth? These folks are probably right. Many of these concepts wouldn’t work in their organizations.

So why do I waste my time talking about things that may not work in many organizations? Two reasons:

1) hope

2) the wind

Hope

Let me be honest. I’ve never run into a perfect model of the open source way in practice (if you have, please point it out to me!).

There are clearly some organizations that have figured out how to build open source principles into their DNA better than others. Wikipedia is a good example. The Fedora Project is another. Still, my guess is the people who are deeply involved in those projects on a daily basis would probably be able to show you some warts, places where old-skool practices are still evident.

We’ve set our company New Kind up as a corporate lab for the open source way. But we can’t make a case for perfection here either. We are still learning and prototyping.

So why not be more realistic? Why not give up and accept that some of these principles work better in theory than they do in practice?

Simple: I have hope.

What gives me hope? Two things. First, I have seen first-hand many examples of great things that happen when open source principles are applied within organizations. From the collaboratively-designed mission of Red Hat to the work of Fedora marketing team, I’ve personally witnessed the power of open source principles in action.

Second, I believe in the pursuit of perfection. Why not aspire to create better companies than we have today? What do we have to lose? I don’t know that we will ever see a perfect open source company. But by pursuing perfection, we are likely to get a heck of a lot closer than where we are today.

[Read the rest of this post on opensource.com]