John Lilly

A community-building perspective on the Gap logo controversy

Over the last week, a handful of folks have reached out and asked me what I think about the events surrounding the launch, then crowdsourcing, then full repeal of the new Gap logo (if you haven’t already heard the story, catch up here).

Honestly, I’d been hesitant to comment at length, partially because so many articles were hitting the best angles already (take your pick of this one, this one, this one, this one, or this one for starters), and partly because somewhere inside I secretly wondered whether the geniuses behind the Gap brand are simply playing us as pawns in a New Coke-esque scheme of diabolical marketing genius (on that point, I still don’t think I know the answer).

While most articles have focused on the aesthetics of the logo itself or on issues surrounding crowdsourcing a logo effort (note to self: must… avoid… commenting… on… crowdsourcing… so… tempting), I’ve been wondering more about the strong reaction of the Gap community.

Specifically, why did the community of customers surrounding the Gap brand have such a visceral negative reaction to the logo change? Is it really that bad? The firm in charge of the redesign has a great reputation and deep understanding of the Gap brand. How did a project run by experienced brand professionals working with one of the largest consumer brands in the world go so wrong so quickly?

For me, the answer can be found in a quote I really love from outgoing Mozilla CEO John Lilly:

“Surprise is the opposite of engagement.”

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

Community-building tip: surprise is the opposite of engagement

In the interview with Chris Blizzard I posted last week, near the end of the article Chris attributes a phrase to Mozilla CEO John Lilly:

“Surprise is the opposite of engagement.”

This may be one of the most simple, brilliant things I have ever heard someone say when it comes to creating engaged, active communities.

When we talk about building communities the open source way, we often mention transparency and openness as critical elements of any community strategy. But when I saw this quote, it reminded me why transparency and openness are so important.

When we are open with people, we avoid surprising them. We keep them in the loop.

Nothing kills someone’s desire to be an active contributor in a community more than when they feel like they’ve been blindsided. By a decision. By an announcement. By the introduction of a new community member.

Few things help a community get stronger faster than simply engaging community members every step of the way. Asking them for input first. Ensuring they are “in the know.”

When thinking about the community you are trying to create, maybe start asking yourself questions like:

[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]