open source

Five questions about authenticity and the open source way with Jim Gilmore

A few months ago, I had the opportunity to meet Jim Gilmore, co-author (with Joseph Pine) of the book Authenticity: What Consumers Really Want. I first read the book a few years ago, and it really struck a nerve for me—these guys were on to something.

So I convinced Jim to subject himself to a Five Questions interview about the place where authenticity and the open source way intersect.

CHRIS: After joining the open source world ten years ago, it didn’t take me long to figure out that most open source folks despise marketing as it is traditionally practiced. Is there something inherently inauthentic about the language of marketing? Perhaps open source folks have a low tolerance for inauthenticity?

JIM: I often quote from a letter-to-the-editor that appeared in the Harvard Business Review following the publication of our article, “Welcome to the Experience Economy.” In this letter, Robert Jones of Wolf-Olins shared his definition of a brand as “the promise of an experience.”

Joe Pine and I responded by saying Amen to that, but added that so often the actual experience fails to fulfill against the promise.  Indeed, marketing in general, and advertising in particular, has become a giant phoniness-generating machine.  And not just the language of marketing, but the very practice of marketing so often serves to erode the perception of authenticity among consumers—by making promises that bear little resemblance to the actual experience encountered.

So much creative talent today is engaged in making promises as marketing instead of being employed to create compelling experiences as actual output.  The experience itself should be the marketing.

My friend Robert Stephens, founder of the Geek Squad, is fond of saying, “Advertising is the tax you pay for being unremarkable.”  I feel that way about most marketing.  I’d like to see creative talent diverted from making messages about goods and services and used instead to help create truly remarkable experiences, ones so compelling that they command a fee as product.

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

Toyota gives customer-driven design the green light

A few weeks ago, Red Hat CEO Jim Whitehurst wrote an article for BusinessWeek suggesting that Toyota might benefit from doing things the open source way when it comes to building the software inside its automobiles.

From Jim’s article:

Open source is about leveraging the power of participation to solve complex problems such as manufacturing, health care, and government. This advantage is why numerous 21st century successes—from Google to Facebook to Wikipedia—are all based on open-source software and principles. It may also be how Toyota can improve its vehicles and ultimately regain consumer trust.

Toyota may be listening.

Last week, Associated Press reported that Toyota has opened a new Design Quality Innovation Division. The new group will be led by Kiyotaka Ise, formerly of Toyota’s Lexus subsidiary, and will be tasked with more quickly reflecting customer feedback in automobile design.

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

BusinessWeek turns an eye to open source beyond technology

On opensource.com, we aspire to take principles the open source software movement has applied to building better software faster and find more uses for them in business, education, government, the law, and generally in our lives.

So a few weeks back, I was excited to see that BusinessWeek (now Bloomberg BusinessWeek) ran a special report called Eye on: Open Source that also embraced the wider usage of open source principles in technology and beyond.

My personal opinion? I think a few of the articles in the special report confuse true community-driven open source innovation with concepts like user-driven product design, crowdsourcing, and design competitions. But it was still neat to see BusinessWeek recognize the applicability of open source principles beyond software.

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

Brand positioning tip #10: repetition is the secret ingredient

When I was at Red Hat, I sometimes got questions from folks who wanted to know the secret to Red Hat’s brand success. First off, I’d always say you don’t grow a $1 billion technology company on brand alone. We sold great products. We treated our customers and developers well. We had a revolutionary business model. Those kinds of things are the bedrock of a successful brand.

But if I was to point to one “secret” thing I think had a big impact on the brand it would be a very simple one:

We said the same thing. Over and over. For years.

For me personally, sometimes I said things so many times I was just as sick of hearing myself as others were.

When people would come to me and ask if they could make a tan hat to give away at tradeshows rather than a red one, I would always repeat: “But we are Red Hat.” We brand folks would always be the ones to bring up the company mission, values, and culture. We’d steer conversations back toward the open source way when they went astray. When my colleagues and I would speak about the culture and brand in orientation, we’d tell the same stories, show the same videos of Bob Young and Matthew Szulik to new employees year after year after year.

When it comes to brand positioning, the biggest mistake you can make is to invest your time, money, and energy in discovering your optimal brand position… and then give up on it before it has a chance to do its magic. Building a great brand has to be done over time and, to paraphrase Jeff Bezos of Amazon, there are no shortcuts.

I’ve worked with a lot of creative types over the years, and most of them love to come up with new ideas. Heck we all do. But sometimes the thing that makes you stand out when everyone else is saying something new is to say something… well… old.

Continue reading →

Is the word “community” losing its meaning?

Poor words. As they get more popular, as we give them more love, we also keep trying to shove in new meaning to see if they can take it.

In the technology industry, this happens over and over. Take “cloud computing,” which used to mean something pretty specific and now means essentially “on the Internet” as far as I can tell. Outside the technology industry, take “news,” which also used to mean something, and now is a muddy mess of news/editorial/advertising.

We’ve even been accused of muddying the term “open source” here on opensource.com (a debate I love to have—there are smart opinions on both sides: protect the core vs. extend the audience).

So when I read a recent post by Gartner analyst Brian Prentice entitled Defining & Defending The Meaning Of “Community” – An Open Source Imperative, I was familiar with the lens he was looking through already.

Brian’s argument? According to his post, community used to mean “a collection of people whose defining characteristic is shared participation.” I might add “and a common purpose or vision.”

But now the word community is often being used to refer to any ol’ collection of people. From the article:

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

Why the open source way trumps the crowdsourcing way

A while back, I wrote an article about why the term crowdsourcing bugs me. Another thing that drives me nuts? When people confuse crowdsourcing and open source. My friend David Burney wrote an interesting post on this subject a while back highlighting the differences.

It finally hit me the other day just why the open source way seems so much more elegantly designed (and less wasteful) to me than what I’ll call “the crowdsourcing way.”

1. Typical projects run the open source way have many contributors and many beneficiaries.

2. Typical projects run the crowdsourcing way have many contributors and few beneficiaries.

It’s such a simple concept, it seems obvious. Let’s look at a few examples to illustrate why this simple difference means so much.

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

Five questions about building community with Chris Blizzard of Mozilla

I’ve always been a fan of the Mozilla Foundation, and not just because of the Firefox web browser. As catalyst for some of the great communities in the open source world, Mozilla is something of a recipe factory for what to do right when it comes to building community. As it turns out, Mozilla’s Director of Developer Relations, Chris Blizzard, is a long time friend of mine.

In fact, this is not the first time I’ve interviewed him– my first Blizzard interview experience was back in 2002 when Mozilla 1.0 came out and he and I both worked for Red Hat.

I spent some time with Chris to discuss his experiences and learn more about community-building the Mozilla way.

1. When I first met you ten years ago, you were a Red Hat employee with a day job keeping the redhat.com website up and running, and, even then, you were hacking on Mozilla for fun in your spare time. Now you run developer relations for Mozilla, and you’ve had some other amazing experiences, including working on the One Laptop Per Child project, along the way.

It strikes me that you are a great case study of someone who has achieved success in the meritocracy of open source by doing good work. Knowing what you know now, if you were starting from ground zero as a community contributor, how would you get started?

That’s kind of a tough question because I don’t have that perspective anymore. I know too much about how these communities operate to be able to answer that with the fresh face of someone new to a project. But, honestly, I think that that if I were to guess I would say find something that you’re passionate about and just start working on it. My own case is instructive.

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

Is Jaron Lanier just a hater, or should we be paying attention?

Last week, my friend Greg DeKoenigsberg posted an article about Jaron Lanier’s negative comments regarding open textbooks. At almost very same time, I happened to stumble upon an article Jaron wrote back in 2006 criticizing Wikipedia.

The common theme is Jaron taking issue with what he calls “online collectivism,” “the hive mind,” and even “digital Maoism” (ouch!). You might call this same concept “crowdsourcing” or “the wisdom of crowds.” It’s all in the eye of the beholder, but the guy clearly does not have much love for wikis or the works of collective wisdom they create.

So I had to ask myself: Why so negative, Jaron?

Is Jaron really a hater of free culture, as Greg claims in his article? Is he an enemy of the open source way? Or is he just a smart dude warning us about the risks of taking the wisdom-of-crowds concept too far?

Fortunately for us, Jaron published a book earlier this year entitled You Are Not A Gadget. So I took a few hours and read it last week to see if I could answer some of these questions.

At times, the book is scary smart, with precise analysis from a man who clearly questions everything, and is in a better intellectual position to do so than most (the section on social media and its redefinition of friendship is especially interesting).

At other times it read like a college philosophy term paper. And occassionally, especially toward then end, it devolved into nearly unintelligeble (at least by me) ravings about things like “postsymbolic communication” and “bachelardian neoteny” (Michael Agger’s review in Slate calls him out for this too).

But wait! Right near the beginning of the book, I found this paragraph:

“Emphasizing the crowd means deemphasizing individual humans in the design of society, and when you ask people not to be people, they revert to bad, moblike behaviors.”

Hey… I kinda agree with that…

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

Five questions about the future of music with David Pakman

Traditional media companies are in big trouble. You may have noticed. You know who else has noticed? David Pakman, currently a partner at the prestigious Venrock venture capital firm. You may also know David as the former CEO of eMusic—a fairly disruptive media company in its own right. David has over 300,000 Twitter followers and regularly blogs here about the “undoing of big media.”

Today, we ask him five questions about where the future of music intersects with the open source way.

1. One of the beautiful things about the open source software revolution is it lowered the barrier to entry for developers who wanted to create useful software. Meaning, without going to fancy schools or working for big Silicon Valley tech companies, people in any part of the world with any level of experience could contribute, and if their code was good, they were in. Is the barrier to entry for artists trying to make it in the music industry getting lower too? It sure doesn’t feel like it sometimes.

I think the barrier to entry to write or make music has always been pretty low. Provided you can learn how to play an instrument, you can write songs. The encroachment of technology into every facet of music making has lowered this barrier even further. An entire album can be recorded at great quality in a basement with a Mac and some bundled software. DJ equipment isn’t even needed anymore — you can do it all on your Mac.

The challenges have always been around marketing and distribution, and the internet changed all that. Anyone can launch a site or a myspace page and offer downloads of their music. In 2008, more than 38,000 new records were released. This was the most ever.

Becoming commercially successful by selling music or touring has never been harder, and that is because fewer people are buying music and consumers have more entertainment choices than ever before. So while it’s easier to make music, it’s harder to make a living making music.

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

What if politicians innovated the open source way?

In the discussions around some of my previous articles, I’ve noticed a trend: we seem to be focusing on cultural changes that need to be made for the open source way to be effective in contexts beyond technology. One cultural context I think could really use some help is politics.

I read an interesting post last week by Morton Hansen (author of Collaboration: How Leaders Avoid the Traps, Create Unity, and Reap Big Results) entitled Obama’s Five Collaboration Mistakes. In the comments below the post, some folks interpreted his words as an attack on the Obama administration. Me? I’d probably interpret Hansen’s words more broadly. Perhaps something like:

Politicians are pretty darned bad at collaborating a lot of the time.

I think many folks would agree with this statement no matter where they sit politically. No matter where they live around the world.

In fact, the word “political” has become almost synonymous with anti-collaborative behavior in many contexts. Certainly in the business world.

But there is a lot a stake here. The economic downturn has hurt our businesses badly. And this has affected many of us in even more personal ways. Jobs. Homes. Security.

We need innovation in the political world to help solve the problems of the business world. Which means we are going to need better collaboration across political boundaries, both inside and between our countries.

Could we open source folks help?

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