Last week, I watched The Power of Introverts, an excellent TED Talk by Susan Cain (she also has a book out on the same subject called Quiet: The Power of Introverts in a World That Can’t Stop Talking).
In her talk, which has been viewed almost two million times since it was posted last month, Susan makes a compelling case that the open, collaborative world we embrace today is not always set up to harness the best work from introverts.
As we’ve moved toward more open office plans, collaborative processes like design thinking, and into a digital world now dominated by the word “social,” Susan wonders who is looking out for the introverts? Should introverts feel guilty about wanting to do their thinking and working alone? And can introverts do great work in group settings?
I spent more than a decade working in the inherently collaborative world of open source software. I regularly lead brand positioning and strategy projects as open, collaborative, social exercises involving entire communities of people in the process. So Susan’s talk made me ask myself a tough question:
By emphasizing a collaborative, social process am I risking leaving introverts—and their best ideas—behind?
It’s no secret that I am a life-long introvert myself. I am much more comfortable writing or reading a blog post in my living room and discussing it via comments or Twitter than I am sitting and talking about it with someone over coffee or, worse, at a social gathering like a party or a conference.
So I get where Susan is coming from. Deeply.
In her TED Talk, she at one point pleads, “Stop the madness for constant group work.” When she said this, it hit me pretty hard. The first thing that came to my mind was the one gazillion design thinking ideation sessions I’ve either run or participated in over the last 7 or 8 years.
I’ve personally never had much trouble speaking up during ideation/brainstorming sessions. But I also suspect I am a relatively mild introvert compared to others I know. I started to wonder what the hard-core introverts were thinking during these sessions (and if you were one of them, feel free to tell me below in the comments).
Did they feel like they were being talked over by extroverts? Did they feel like they were out of their element, or needed more time to process their thoughts before blurting them out and having them recorded on the wall? Would they have preferred to contemplate on their own instead of thinking socially as part of a group?
Then another thought stuck me: I’ve met a lot of software engineers over the years, and while not all of them are introverts, many of them are. Frankly, I don’t think too many extreme extroverts could stand to sit in their office and stare at a computer screen all day. But for some introverted software developers, this is bliss.
Yet open source software is developed in a collaborative, social process… run in many cases by introverts.
Why does that work?
For me at least, the answer comes down to the difference between virtual and in-person collaboration. Open source software developers do much of their collaborating online. Often this is because they are geographically dispersed around the world. But I’ve also seen developers sitting two feet away from each other communicating via instant messages or email.
Online collaboration has two key advantages over in-person collaboration for introverts:
1) It allows them to avoid stressful in-person social interactions.
2) It allows them to take their time, contemplate, and think deeply before responding.
Over the past two years at New Kind, I’ve personally been doing less and less in-person design thinking ideation sessions, instead hosting more open, collaborative sessions online. Sometimes they are efforts like the hackathons I’ve run for the Management Innovation Exchange that involve hundreds of people collaborating from all around the world. Other times they are client projects where the collaborating happens via Basecamp or another online tool.
I’ve found I enjoy facilitating sessions online much more than in-person sessions, and I think it suits my personality better. Because the collaboration happens asynchronously, I can take my time crafting thoughtful responses and generating ideas. I can wait until I’m in the right frame of mind to participate, and most importantly, I can work with others, yet be alone at the same time.
I suspect some of these same advantages also translate to participants in online group sessions as well. And for this reason, perhaps many introverts are more comfortable in collaborative projects online than in person. Some of the best ideas I’ve seen emerge from online collaborative exercises come from people who usually remain completely silent in meetings.
In many cases, online collaborative projects provide the best of both worlds—you can collaborate and build off the ideas of others, but still take the time to process your thoughts before you add them (and as a special bonus, you don’t have the stress of in-person social interaction).
If you consider yourself an introvert, I’d love to hear about your experiences participating in collaborative projects online vs. in person. Do you agree with Susan Cain’s assessment that collaborative group projects are not designed to get the best out of introverts? Do you find yourself making better contributions and contributing more in online projects? Or are online collaborative groups just as bad for you as in-person sessions, and you’d rather just work completely on your own?
I’d love to hear what you think.
Once you’ve identified the key communities you think it is important to engage with, the next step is to identify the people you’d like to represent your brand within these communities. For simplicity, I like to refer to these folks as brand ambassadors.
How to find brand ambassadors
Start by identifying the people inside your organization who have the best relationships with each community. These people are the best candidates to become your brand ambassadors. The ideal brand ambassador is already an actual community member, actively participating in conversations and projects with other community members.
While an employee of your organization, this person shares common values, interests, and experiences with other community members. It is less important what position they hold within your organization and more important how they are viewed by the community itself.
After you’ve identified possible brand ambassadors, reach out to them to see if they are willing and interested in expanding their personal roles in the community to include being representatives of your brand as well. Some might already be playing this role, others might be playing this role and not realizing it.
Don’t force or pressure people. The ideal candidate will be excited to be considered and will be passionate about the opportunity, so if your best candidate doesn’t seem interested, try to find someone else who is.
Creating brand ambassadors from scratch
If you don’t have anyone in your organization who is already a member of the community, you’ll need to have someone join. Choose someone who understands your organization’s story and positioning well but also already shares interests, values, and experiences with the community in question.
Have this person attend meetings, join mailing lists, participate on forums, and otherwise begin to contribute to the community first as an individual. It will take a little longer to get started, but it will be worth it if your brand ambassador has a deep contextual understanding of the community before they dive right in officially representing your organization.
Brand ambassadors as faces of the brand
You should ensure that your brand ambassadors deeply understand your brand positioning so they can live it (not just speak to it) in their activities within these external communities. If you are developing many brand ambassadors at once, consider hosting a brand ambassador bootcamp where new ambassadors can practice telling the brand story and get aligned on the overall positioning of the organization. Also use this as an opportunity to emphasize the key role of these ambassadors in developing the brand experience and keeping relationships with the community healthy and productive.
You may have some communities where there is a whole team of ambassadors, not just one. For example, at Red Hat, a large team of developers represented Red Hat (and themselves) in the Fedora community. Invest as many ambassadors as you need in order to provide the best possible support for and adequately communicate with the community.
As you recruit brand ambassadors, you extend the internal core of the brand. Although it is wonderful to see your core group getting bigger, extending your reach is also an important time to ensure consistency. Be very careful to take the time to educate all brand ambassadors well so the entire brand orchestra stays in key.
Brand ambassador philosophy
Wikipedia defines an ambassador as “the highest ranking diplomat who represents a nation and is usually accredited to a foreign sovereign or government, or to an international organization.” Usually an ambassador lives and operates within the country or organization where he is assigned.
Your brand ambassadors should channel the same philosophy. While they are members of your organization, they should “live” within the communities they are assigned to as much as possible while representing your organization within that community.
Great brand ambassadors are loyal to the organization and to the community at the same time. They develop relationships of respect, honesty, and trust within the community, which allows them to clearly and openly communicate the priorities, desires, and needs of both sides.
Brand ambassadors are not just mouthpieces for the organization, but should also maintain their own personality, interests, and opinions in the community—often distinct from those of the organization. In places where they are representing their own opinions and ideas, they should provide the proper disclaimers. With a little practice, this is not nearly as difficult as it might sound. The key is maintaining an authentic personal voice while being open, transparent, and human in their communications.
Don’t think someone in your organization has the right makeup to be a good ambassador based on what you see here, even if he or she has good relationships within the community? Don’t make him or her an ambassador. The brand ambassador is a representative of your brand to the outside world, and the job carries a lot of responsibility and requires a high emotional intelligence and diplomatic sensibility to do well.
So take the time to find, train, and support brand ambassadors within your organization. With some attention and focus, you may soon find that your network of ambassadors becomes one of your organization’s most valuable assets.
If so, you can find more tips about how to extend your brand effectively in my book, The Ad-Free Brand (not an advertisement, mind you, just a friendly suggestion:).
It’s been a week now since Steve Yegge of Google fired the shot heard ’round the tech industry. In case you missed it, Steve wrote a thoughtful, yet highly charged rant intended to begin an internal conversation about Google’s failures in learning how to build platforms (as opposed to products).
In the post, he eviscerates his former employer, Amazon, and in particular CEO Jeff Bezos (who he refers to as the Dread Pirate Bezos), but doesn’t pull any punches with his current employer either. It is an extremely passionate, well-written piece which, my guess is, will change the conversation internally at Google in a positive way.
But there was one problem:
When posting it to Google+ (which he was admittedly new to), Steve accidentally made his rant public, where the whole world could see it.
And over the past week, pretty much everyone has.
This prominent re-post (Steve took his original piece down, which I’ll get to in a second) has generated, as of this writing, 487 comments and over 11,000 +1s on Google+.
The comments are spectacular and largely supportive. Some have referred to this as Steve Yegge’s Jerry McGuire moment.
But my post isn’t about Steve. He’s received plenty of attention in the past week, poor guy.
It’s about the Google PR team that, in a time of crisis, made the tough decision to stay true to the spirit of openness that Google Senior VP of People Operations Laszlo Bock described in his recent piece in Think Quarterly. From Laszlo’s piece:
“And if you think about it, if you’re an organization that says ‘our people are our greatest asset,’ you must default to open. It’s the only way to demonstrate to your employees that you believe they are trustworthy adults and have good judgment. And giving them more context about what is happening (and how, and why) will enable them to do their jobs more effectively and contribute in ways a top-down manager couldn’t anticipate.”
So if “default to open” is the overall philosophy at Google, how does it play out in practice? As it turns out, Steve Yegge’s rant provides a pretty good data point.
In a Google+ message explaining his decision to take down the original post, Steve described the reaction of the Google PR team this way:
“I’ve taken the post down at my own discretion. It was kind of a tough call, since obviously there will be copies. And everyone who commented was nice and supportive.
I contacted our internal PR folks and asked what to do, and they were also nice and supportive. But they didn’t want me to think that they were even hinting at censoring me — they went out of their way to help me understand that we’re an opinionated company, and not one of the kinds of companies that censors their employees.”
This is not, in my experience, the kind of support that most PR folks would have given Steve in this situation:) And because of it, this episode, however traumatic, serves as one piece of proof showing that Google’s “default to open” approach is not just aspirational bullshit.
I’m sure there are plenty of places where people could argue that Google is not being open enough, or could stand to be more open than they are today.
But in this particular case, in a moment of crisis—where many weaker leaders would have given in to the frightened urge to attempt a cover up—Google stood by its core beliefs and defaulted to open.
While openness is sometimes ugly and painful (as it certainly is in this case), it often allows great opportunities to emerge that would otherwise never see the light of day.
I suspect that when the waters recede, this authentic, beautiful, and raw piece of communication might be the starting point toward something better, not just within Google, but in the tech industry as a whole.
And for supporting openness, even in its most painful form, Google PR team, I salute you.
Almost every time I’ve turned on the television in the past week, I’ve seen an ad for Google Chrome. What started earlier this year as a sprinkling of ads here in the United States has become a torrential downpour.
For me, Google has long been one of the poster children for a new breed of company born in the age of the Internet that doesn’t need to rely on traditional advertising to build its brand.
So, as I’m sure many of you have, I started asking myself, why exactly is Google doing so much television advertising?
It’s no secret that Google has historically not been a fan of traditional advertising. In fact, it wasn’t so long ago (2006) that Google Chairman Eric Schmidt called advertising “the last bastion of unaccountable spending in corporate America.”
And Google is certainly an interesting paradox: a company that historically does little paid advertising itself, yet makes billions of dollars selling advertising to others.
I did a little research and pieced together some history about Google and television ads.
In May, 2009, the first ad for Google Chrome appeared on television in the United States. In the blog post announcing the new spot, Google sounded almost apologetic, saying the ad was originally just developed in Japan as a web video, but it sparked a conversation and received good feedback. So Google decided to run it as a TV ad, in part as a test of the new Google TV Ads program.
The next year you may recall that Google actually bought an ad on the Super Bowl, which they called Parisian Love.
Eric Schmidt announced the spot on the Google blog, justifying it by saying “we liked this video so much, and it’s had such a positive reaction on YouTube, that we decided to share it with a wider audience.” But his Twitter announcement of the ad acknowledged that this was quite a unlikely strategy for Google:
Earlier this year, Google began developing the current set of ads for Google Chrome in partnership with advertising agency BBH.
The work is compelling, as advertising goes (here’s a link to all of the spots on YouTube, if you want to check them out). Perhaps the most thoughtful one highlights the It Gets Better Project, which has resulted in thousands of videos being created for YouTube that are intended to give hope to LGBT youths.
The Dear Sophie spot has been viewed on YouTube over 3 million times, and there are ads featuring Lady Gaga (4 million page views) and Justin Bieber (almost 2 million pages views) as well. The newest pieces highlight The Johnny Cash Project (where artists are collaboratively developing a tribute music video for Cash’s song “Ain’t No Grave”), Frank Restaurant in Austin, TX (mmm…. so delicious… don’t pass up the waffle fries), and Angry Birds.
From a branding perspective, the ads make sense–as stories. By telling these stories, Google and BBH are invoking the transitive property of branding to associate Google Chrome with some incredibly innovative collaborative efforts. The math looks something like this:
Lady Gaga = open, collaborative, innovative.
Google Chrome = open, collaborative, innovative.
Therefore, if you like Lady Gaga, you’ll like Google Chrome.
Certainly getting ten million combined pageviews on YouTube for the campaign is pretty awesome—and free—so why spend the big money to put these ads on television too? Isn’t the beauty of the Google / YouTube model that it can be effective at eliminating the need for traditional advertising?
Perhaps Google is trying to expand its brand awareness with people it can’t reach via YouTube? But why spend the money on Google Chrome, a web browser (and a term Google itself has shown that almost no one understands), rather than the Google brand itself?
My first thought was that perhaps Chrome was losing the browser wars and the television ads were a desperate attempt to keep the Chrome ship afloat.
It turns out that is about as far from true as you can get. Chrome is killing it. According to StatCounter, Chrome is rapidly gaining new users at the expense of Internet Explorer and Firefox both.
In fact, some predict Chrome usage will actually exceed Firefox usage by the end of this year.
A victory for traditional advertising?
Not so fast. Here’s a good post from late this summer highlighting Chrome’s rapid ascent and documenting the reasons for it. From the post:
“Online, Google of course has a huge marketing advantage over basically everyone else since it can recommend its Chrome browser on its web properties such as Google Search, YouTube, etc. Not even Facebook can compare with Google when it comes to sheer web presence, reaching over a billion users.
That said, Google has clearly built a very good and highly popular product. If people didn’t like Chrome, the browser wouldn’t be able to retain users to the extent it seems to be doing.”
So the two reasons for Chrome’s success come down to:
1) the browser is good
2) it can leverage the power of Google’s online advertising engine (yes, the same engine that millions of companies have raided their traditional media advertising budgets to spend more on, causing the rise of Google in the first place).
But I didn’t see Google’s television advertising strategy mentioned here, or in any other article I read, as an explanation for Chrome’s rapid ascent.
Let me sum things up:
I get why Google is making the effort to create stories like these and share them with the world. Storytelling is an extremely powerful tool for building brands the open source way.
And overall, I like the approach Google is taking—many of the stories are really well told, and the focus on open, collaborative projects and artists (not to mention tasty hot dogs) sits well with me.
But I can’t for the life of me figure out why Google spending so much of its shareholders’ money putting these ads on TV.
If you have the answer, I’d love to hear it.
[This post originally appeared on opensource.com]
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]
In my last few posts (here and here), I shared some tips for collecting and synthesizing the brand research you will use to design positioning for your brand. In this post, I’ll share three approaches to designing brand positioning I believe will work for the majority of brands:
• The lone designer approach
• The internal community approach
• The open community approach
Each of these approaches has strengths and weaknesses, and they can also be mashed up into a hybrid that better suits the culture of your organization.
The Lone Designer Approach
Are you a small organization or an organization of one? Perhaps you are attempting to position a website or simply get a small company off the ground on a foundation of solid positioning. If you found during the research phase that you were doing most of the work yourself and don’t want or can’t afford to bring others into the positioning process, you may be a good candidate for the lone designer approach.
The lone designer approach is exactly what it sounds like: a positioning process run by one person alone or by a very small group. The advantage of this approach is that you have complete control over the process. You won’t have to spend much time arguing with others over the exact words in your brand mantra; you won’t need to conduct time-consuming collaboration sessions; and you will only go down rat holes of your own choosing. The lone designer approach can be very efficient and is the least resource-intensive of the three approaches.
The downside of the lone designer approach is that it gives you no head start on rolling out your positioning to your brand community. By making your positioning process a black box and revealing only the finished product, you are taking some risks. First, the positioning you design might not resonate or, worse, might be ignored because you didn’t include input from others beyond the initial research. Second, you may have trouble getting others to help you roll it out or take ownership over its success because they had no role in creating it.
Usually I recommend the lone designer approach only to small or new organizations with no access to a preexisting community of employee or community contributors who care about the brand. If you already have a community of supporters around your brand—even if it is small—strongly consider one of the other two approaches (internal community or open community).
The Internal Community Approach
You understand the powerful impact that engaging members of your brand community in the positioning process might have on your brand. You believe your organization is progressive enough to allow employees to help with the brand positioning process. But you just don’t think your organization is ready to open up the brand positioning process to the outside world. If this sounds like your situation, the internal community approach might be the best option for your brand.
The internal community approach opens up the positioning process to some level of participation from people inside the organization. It may broadly solicit contributions from every employee, or it can simply open up the process to a hand-selected group of people representing the employee base.
The internal community approach to brand positioning is a smart, safe approach for many organizations. It makes brand positioning a cultural activity within the organization, allowing you to collect a broad range of interesting ideas and begin to sow the seeds for future participation in the brand rollout down the road. In addition, it can become a compelling leadership opportunity, helping develop future leaders of your brand as well.
While this internal approach is still community-based, it is usually perceived as less risky than an approach involving external contributors. You might find it easier to sell the internal approach to executives who fear opening up the organization to the outside world or think doing so will give the external community the perception the organization is confused or doesn’t know what it is doing because it is asking for help.
The Open Community Approach
Even though I’ll be the first to admit that it is not right for every brand, the open community approach is by far my favorite approach (as you can probably tell by now) and is a very effective one for ad-free brands. The open community approach opens the positioning process to contributions from members of both the internal and external brand communities. Running an open community brand positioning project is similar to running an internal community one. Both approaches have the advantage of bringing in a variety of viewpoints.
Both can create valuable brand advocates who will be helpful down the road. The open community approach just takes things as step further and allows people outside the organization to contribute as well. The benefit of this approach is that it can usually form the beginning of a constructive dialogue with all the people who care about your brand—not just those who work for your organization. It can help you build relationships based on trust, sharing, and respect with people in the outside world. And it can save you money and time by revealing flaws in your positioning much earlier in the process.
The downsides of an open approach? If the project is poorly organized or badly communicated, it really will realize the fears of some executives and show the outside world you don’t know what you’re doing. An open positioning approach requires a deft, highly skilled, effective communicator and facilitator. It requires coordination between different parts of the organization that are in touch with the outside world to ensure communication is clear and consistent.
But although the risks of opening up your positioning process to the outside world are higher, the rewards can be much bigger as well. By transparently opening a relationship between your brand and the outside world, you are embracing the future of brand management, accepting the role of your brand community in the definition of your brand, and proactively getting your community involved in a positive way.
You are beginning a conversation.
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]
I believe almost all great brands are built on a foundation of great positioning.
I feel so strongly about positioning that one of the core elements of this blog is a series of brand positioning tips I learned over the years as an eager student of classic brand positioning.
Sometimes great positioning is led by a branding genius such as Scott Bedbury (who helped grow the Nike and Starbucks brands); sometimes a great leader and communicator with a very clear vision (like Steve Jobs at Apple) drives it into the organization; sometimes people stumble on great positioning by pure luck; and more and more often, organizations are developing positioning by collaborating with the communities of people in and around the organization who care most passionately about the brand.
This last way is the ad-free brand way of developing brand positioning.
1. Great positioning helps people understand the brand
The best brand positioning is always simple and clear. The greatest product or organization in the world won’t be successful if people can’t or don’t bother to comprehend why they should care about it. Your story must be able to break through the clutter.
2. Great positioning helps people value the brand
Getting people to understand the brand is the first step, but no less important is ensuring they value the brand. The best brands stand for things people care about or desire.
3. Great positioning helps people identify with the brand
Once people understand and value the brand, they must also understand how they fit in and how they can engage with the brand. They need to see some of themselves in it.
4. Great brand positioning helps people take ownership over the brand
It may sound like a brand’s worst nightmare to lose control and have the brand community take over. But the most self-actualized brands of the twenty-first century allow the communities of people surrounding them to take some ownership of and responsibility for the brand. Essentially, the brand owners become in command and out of control of the brand.
In 1981, when Jack Trout and Al Ries wrote Positioning: The Battle for Your Mind (the book that really defined the discipline of brand positioning) traditional advertising was still a dominant force. In fact, as you glance through their book, you’ll notice that most of the examples they use to illustrate positioning concepts are classic advertisements or advertising campaigns like the Avis “We’re #2, so we try harder” or the 7-Up “Uncola” campaign.
In the book, Trout and Ries define positioning as follows:
“…positioning is not what you do to a product. Positioning is what you do to the mind of the prospect. That is, you position the product in the mind of the prospect.”
The Trout and Ries definition is a perfect way to achieve the first three of the four benefits above; it helps people understand, value, and identify with the brand.
Where the Trout and Ries model of positioning is all about what you do to the mind of the prospect, ad-free brands are less interested in creating meaning for a brand in people’s minds and more interested in creating meaning for a brand with the help of people’s minds.
By giving the communities of people who care about a brand some ownership over its future direction, we begin to build relationships based on trust, respect, and a mutual exchange of value.
Where 21st century brands will really shine is by mimicking the open, collaborative, meritocratic model of the open source software movement (and the Internet itself) in their positioning work. In my view, without beginning to engage the communities of people who care about a brand as co-owners, classic brand positioning by itself will continue to be less and less effective as traditional advertising and PR continue to be less and less effective.
The secret? Marrying those classic brand positioning principles to a 21st century way of collaborating with the communities of people who care about a brand. By doing both together, we’ll be able to build stronger, more resilient brands than ever before.
Last week, Google Senior Vice President of Product Management Jonathan Rosenberg resigned after almost 10 years at the firm. While the comings and goings of tech industry executives aren’t typically that interesting to me, I found this news fascinating for a couple of reasons.
First, Rosenberg says that one of the things he plans to do is write a book with ex-Google CEO (and current Executive Chairman) Eric Schmidt. The subject? According to an article in the Mercury News, they’ll be writing about “the values, rules and creation of Google’s management culture.”
Now that is a book I’d like to read. Google is in many ways an ideal case study of the open source way as applied to management practices, and, while many have written books about Google already (notably this one by Bernard Girard and this brand new one by Steven Levy), I’d love to see Schmidt and Rosenberg’s take (and I hope we can corral one of them for a webcast on opensource.com when the book comes out).
I’m especially interested in their view of how the existing Google culture changed (or didn’t change) during their tenure. Especially since it has been reported that Rosenberg’s top-down management style didn’t mesh well at first with the existing engineering-led culture.
But what I find to be the even more interesting question in the short term is, with Rosenberg leaving, who will be the new face of openness at Google?
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]