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” 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]
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]
A few years back, a good friend recommended I pick up a copy of Designing Brand Identity: an essential guide for the whole branding team by Alina Wheeler. Now in its 3rd edition, it’s a beautiful book, well designed and easy to read or to use as a reference. I recently caught up with Alina, who is finishing up work on a new book entitled Brand Atlas: Branding Intelligence Made Visible with designer Joel Katz. I asked her some questions about where branding and the open source way might be beginning to intersect.
CHRIS: I have heard that you often begin the continuum of branding with the 17,000 year old cave paintings in Lascaux, France. Now that’s historic branding! What are one or two key concepts in designing branding identity that have stayed constant and endured from a world of cave paintings to a world of Twitter, Facebook, and open source?
ALINA: Since the beginning of time, the need to communicate emerges from a universal set of questions: Who am I? Who needs to know? How will they find out? Why should they care? Whether you are on Facebook or in Shanghai or Charlotte, these questions are the same.
Mankind has always used symbols and stories to express individuality, pride, loyalty, and ownership. Individuals, communities and organizations express their uniqueness through their identity. Brand is identity. Competition for recognition is as ancient as the heraldic banners on a medieval battlefield. The battle for physical territory has evolved into competition for share of mind. The competition is fierce.
The power of symbols remains elusive and mysterious–a simple form can trigger recall and arouse emotion–whether it is emblazoned on a flag or embedded in an email. There is significant research about the purpose of the images in the caves of Lascaux. For me they are a reflection of what we are all thinking about now: communication, community, culture, meaning, survival, and navigation.
CHRIS: Now the opposite question: as we begin 2011, are there core branding principles you think have shifted significantly since you wrote the first edition of the book in 2003?
ALINA: The tools have changed. The fundamentals have not. Whether you are the CEO of a global consumer brand or a social entrepreneur, I believe that there is a universal set of principles that are fundamental to increasing awareness, attracting prospects/opportunities, transcending the clutter, and building customer loyalty.
The brand conversation has changed. We all know that now. The challenges have increased exponentially. The tools have become so provocative that they reduce our attention to the fundamentals: being customer centric, staying aligned with your vision and values, and staying differentiated in a world that is overwhelming in sameness and clutter.
The pressure to constantly update and innovate has polarized the world of brand builders. For some, it is an exhilarating time and for others a treadmill where you are running faster to stay in place. There are those who embrace marketplace dynamics and ignore brand fundamentals, and those who are stuck in their legacy infrastructures and business models refusing to embrace change and speed. Success requires embracing both.
CHRIS: Here on the opensource.com business channel, we often talk about how core open source principles like community, collaboration, meritocracy, and rapid prototyping can help businesses of any type–not just those building software. I love the detailed case studies you did in Designing Brand Identity. In your studies of leading brands, have you seen examples of these principles being applied in the branding world?
ALINA: I am eager to learn about new brands that are co-created with the customer or end-user. I believe that open source is the most meaningful and relevant methodology that will help us prepare for a new world: i.e. build communities that matter, collaborate more effectively toward outcomes that matter, and innovate because for survival, that matters.
Although open source is a fairly new idea to most brand managers that I know, it embodies the branding process ideal from an organizational development perspective. The biggest challenge on revitalizing an existing brand is frequently busting through the silos. How do we get IT to work with customer support and marketing to work together on behalf of the customer? How do we get different departments with radically different agendas to be part of the campfire around the brand? It is so powerful when there is a cross-departmental, cross-disciplinary collaboration to build the brand, and to deliver on the brand promise.
B Corporations are a new class of certification and classification for companies that want to collectively redefine success and to leverage the influence of their businesses to solve social and environmental problems. B Corps connect their executive teams with peers from mission-aligned companies.
The Charleston Parks Conservancy has a unique network of community volunteers called the Park Angels, who literally help care for Charleston’s 120 + parks. They have become the public face of the organization. The long-term benefits are for the entire city: building community and improving the quality of life, health and economic strength. Park Angel’s brand is visible on numerous platforms that connect people to people, people to the parks and to the bigger ideal of making a difference. This movement has instilled a sense of ownership and pride.
I believe that IDEO uses open source methodology in their product development work, although I don’t think they call it open source. They are renowned for letting customers/users be part of the product development process and routinely use rapid prototyping. Certainly their culture of creativity and innovation is a meritocracy. The Ripple Effect is a project done in partnership with the Acumen Fund and the Gates Foundation. IDEO collaborated with 22 organizations in India to develop new methods for safe transportation and storage of drinking water in India’s villages.
CHRIS: I can tell design means more to you than just a pretty logo. What is the strategic role of design in building brands today?
ALINA: Lou Danziger said it best, “Design is intelligence made visible.” The best design is a result of strategic imagination, an ability to understand and align business goals with creative strategy and expression. While brands are about emotional connection, brand identity is any tangible expression of the brand. We can see it, hear it, watch it move. Designers play an essential role in building brands and creating unique and memorable experiences. Designers work to fuel recognition across platforms, amplify differentiation, and make big ideas accessible and understandable.
The best designers have an ability to imagine what others can’t see and to show what it looks like and what it feels like. Design is often overlooked in brand strategy meetings where rapid prototyping could benefit and accelerate the decision making process. Having designers shoulder to shoulder with researchers examining user experiences could jumpstart new solutions.
CHRIS: One trend we discuss regularly here on opensource.com is the trend toward organizations giving up some control over the direction of their brands to the communities around them. I’d love to hear your thoughts. Is this a positive thing? Dangerous? Maybe both?
ALINA: Brands exist because there are customers. Although that might sound like a blinding flash of the obvious, it’s important to remember that ultimately the customer always decides whether a brand will flourish or die.
Just like in any conversation worth having, there is a time to talk and a time to listen. Listening to the aspirations, desires, needs, and challenges of your core stakeholders is the most critical brand building competency.
I do believe that control is critical to brand success whether you are a start-up venture, a non-profit or a consumer brand. Having values that don’t waiver. Being certain about why your organization exists. Being consistent about who you are and what you stand for. Taking the time to engage your entire organization in the vision and values. Creating places where conversations can happen. Building trust. Anticipating and fulfilling needs. Being transparent. Making certain that the brand experience is coherent and relevant. These maxims are intentional. As more brands in the future are co-created with end-users, perhaps this notion of control will evolve to a more collaborative model.
The third edition of Designing Brand Identity is available on Amazon now. Alina Wheeler’s new book Brand Atlas: Branding Intelligence Made Visible will be available in April, 2011 and is available for pre-sale now on Amazon.
[This post originally appeared on opensource.com]
As 2010 comes to a close, I thought I’d write my last post of the year about a project that has really moved and inspired me. The project is called Studio H, and is the brainchild of two brilliant designers, Emily Pilloton and Matthew Miller, who have found a new calling as teachers in one of the poorest, most rural counties in my home state of North Carolina.
Even though Bertie County, where the experiment is taking place, is less than 2 hours away from where I live, I first heard about this project earlier this year from a good friend who showed me the TED Talk Emily had given at TEDGlobal 2010 in July. Here is her talk:
It’s a wonderful story. Two successful designers leave their San Francisco home to move to the poorest county in North Carolina and design a program to help public school kids (over 95% of who qualify for reduced-rate or free lunches) get a shot at a better future.
What makes the story particularly compelling is the non-traditional learning approach, utilizing design thinking and some other tools that will be very familiar to those of us who do things the open source way.
Watch the TED talk first, which will likely bring anyone but Scrooge himself close to tears, but don’t stop there.
This project is not just a theory. Studio H is underway, with the students now well into their second fall project, designing some really amazing chicken coops (chickens are a big part of the Bertie County economy).
You can follow the students’ progress on the blog here.
The third and final project next spring will be to design and build a public farmers market in downtown Windsor, the county seat of Bertie County, population 2000.
If you like what you see so far, consider making a donation. After all, this could be what the future of education might look like.
I certainly hope so.
This post originally appeared on opensource.com.
The other day I was chatting with friend and digital strategy/social media expert Ken Burbary on the phone. He was advising a colleague on some good community-building techniques to consider when all of the sudden the following words came out:
What? I did a double-take (or at least the conference call equivalent) and asked him to repeat himself.
I had heard him correctly.
Ken lives in Michigan. Michigan is not far from Wisconsin. Wisconsin is where a lot of cheese is made. Wisconsin also has an (American) football team called the Green Bay Packers.
The biggest fans of the Green Bay Packers wear wedges of cheese made out of foam on their heads to show their support for the team. When someone will wear a big wedge of cheese on their head to show support for their team, that means they are a pretty big fan.
So Ken was saying that good community catalysts seek out and empower the biggest community supporters and advocates—the cheeseheads.
I found a fantastic blog post, written last fall by a colleague of Ken’s named Rachel Happe, entitled Cheeseheads. The post, which appears on The Community Roundtable website, explains in more detail the concept of how to engage your community’s cheeseheads. I won’t repeat Rachel’s advice here, but instead want to ask a follow-on question:
Sitting at a football game at Lambeau Field, it’s pretty easy to spot most of the biggest fans. They have foam cheese on their heads.
But what you do when a community isn’t the foam-hat-wearing kind? How do you find and empower the people who are the community’s energy source? Here are a few thoughts from me on how to find the biggest community advocates when they aren’t in plain view.
[Read the rest of this post on opensource.com]
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]
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.
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]