Home
  • About
  • Contact
  • My Calendar
  • Presentations
  • WordPress Consulting
  • Advertising
  • Podcasts
  • Jobs

  • Wikinomics: Combining Wikis with Economics; the More You Share, the More You Win

    March 8th, 2007 | Posted in Web 2.0, Wikis 8 Comments »

    wikinomicsWikinomics explores the economic side of wikis. In this Harvard Business Review (HBR) ideacast, Don Tapscott, author of Wikinomics: How Mass Collaboration Changes Everything, tells a story about a CEO of a gold mining company who embraced wiki principles to boost his company’s revenue from 90 million to 10 billion.

    Frustrated by his geologists’ inability to locate the gold in his land, the CEO nearly closed the company, but in a final effort, decided to open up his intellectual property to geologists and engineers around the world to see if anyone could provide better guidance about the gold’s location. The top three responses would be awarded half a million dollars. After evaluating the responses, he selected the top three and awarded the prize money. But then the really interesting part begins.

    He used the information from the submissions to actually find the location of the gold. In one year, his company’s revenue increased from 90 million to 10 billion. This is the power of mass collaboration. Had the CEO kept the intellectual property (IP) confidential, as most company’s treat their IP, the company would have limited itself to a small intelligence. But collective wisdom seems to triumph in most endeavors.

    This is just one story from Tapscott’s book. It looks like a great read. For more online reading, you can visit his wikinomics website. Some reviews of the book do a nice job summarizing the principle of wikinomics:

    “Wikinomics illuminates the truth we are seeing in markets around the globe. The more you share, the more you win. Wikinomics sheds light on the many faces of business collaboration and presents a powerful new strategy for business leaders in a world where customers, employees, and low-cost producers are seizing control.”

    - Brian Fetherstonhaugh, Chairman and CEO, OgilvyOne Worldwide

    “Collaboration – externally with consumers and customers, suppliers and business partners, and internally across business and organization boundaries – is critical. Wikinomics reveals the next historic step – the art and science of mass collaboration where companies open up to the world. It is an important book.”

    - A. G. Lafley, CEO, Procter & Gamble

    “I love this book. How counter-intuitive is it that openness, peering, sharing, and acting globally would become key to corporate competitiveness, growth and profit? Mass collaboration is the most disruptive development in business in a long time. Consider Wikinomics your survival kit.”

    - Ross Mayfield, CEO, Socialtext

    My favorite reviewer is the one who wrote, “the more you share, the more you win.” How can this be applied to technical writing?

    Most companies maintain tight control over the publishing rights of their help files. Sharing publishing rights with users may seem frightening, but the greater the risk, the greater the reward. We could share authorship with both our project teams and users. They could contribute tips, analysis, and insight that would take us beyond what we ourselves could create.

    Most companies keep their style guides, templates, and writing methology secret. Anything you develop while you’re at work becomes protected intellectual property of the company. But what happens if you share those templates? Or that stifling style guide? Readers might show you how to make them better.

    Companies also tend to protect news about their IT projects. Exactly what are they working on, for whom, what’s involved, who’s working on it? Sharing that information would help bridge gaps between users and IT departments. Just having a development blog provides an access point for users to connect with developers, and for developers to connect with users. Feedback, sharing of ideas, and usability exchanges could flow freely with transparent, authentic project blogs.

    Code about software is also secret. Your developers just spent the last year hacking out the code for that software. Are you going to release it to the public, for anyone to copy/use/view? Isn’t that corporate suicide? But if the principle “the more you share, the more you win” is true, perhaps users would build on the code, and enhance it, and then give back to you. Rather than starting from scratch, you can mutually benefit. Keep building up, rather than building independently.

    Tapscott says businesses that don’t participate in the new mass collaborative web won’t keep up:

    In the last few years, traditional collaboration—in a meeting room, a conference call, even a convention center—has been superceded by collaborations on an astronomical scale.

    To keep up, businesses will have to change their models of collaboration, opening up the doors to a global audience. The technical writing community is slow to embrace this trend, but in the future, adopting wikinomics may be mandatory just to keep pace with those who are.

    These icons link to social bookmarking sites where readers can share and discover new web pages.
    • del.icio.us
    • StumbleUpon
    • Facebook
    • LinkedIn
    • TwitThis

    8 Responses to “Wikinomics: Combining Wikis with Economics; the More You Share, the More You Win”

    1. Heidi says:

      This post reminds me of the book, The Wisdom of Crowds (a book I’ve been meaning to read but haven’t yet). It also reminds me of an NPR Business Story of the Day (or was it the Marketplace public radio show or live NPR radio that I was listening to, can’t remember) where they were talking about how popular it has become to offer prizes lately. In other words, a company, millionaire, or any group decides to put out a prize to solve a technical problem, social problem, and so on; that prize is then awarded and the sponsor of the prize goes on to innovate around the ideas that were presented to them. It turns out that prizes weren’t as popular as in years past. Then again, the world has more millionaires and billionaires than it used to, too.
      Your posts about wikis definitely make sense to me. I could see your championing of them making a difference in their future adoption; keep them coming.

    2. Aaron says:

      Tom, your post on mass collaboration and wikis was very interesting. I think this sort of collaboration between the user and the technical communicator is one of the key themes when thinking about the future of user assistance. Collaboration using a wiki or a user community could provide a wealth of information about the value of content. This body of information could be mined to improve the help content that a user receives. The means by which users contribute content will require control and moderation in order to keep content relevant and accurate – a significant challenge. There are a lot of things to discuss with this idea, but not enough time to discuss them all here… great post, you have me thinking of a future podcast.

    3. avi says:

      6-7 years ago tech writers were not willing to share their text (although it wasn’t their property). Today, the text is shared, but the meta-data isn’t. I wonder whether this is a classical KM problem.

    4. Tom says:

      Hey Aaron, it’d be cool to hear a podcast on that. I’d like to find a lot of examples of companies using wikis for documentation. It seems like a neat idea, and I’m planning to experiment with a wiki-based project soon, but I think corporate documentation wikis are mostly conceptual right now.

      There are tons of issues surrounding documentation wikis. One writer said to me, if you do that, your project will never be done. That was a sobering thought. She also said, you don’t know what user comments are like. Imagine a user that vents or rants about how bad the project is, rather than supplying help content. What do you do with that?

      Another problem is user content may be nearly unreadable. Do you spend your time fixing up user content for the life of the product? What if a developer adds a lot of info that is simply not relevant or useful. Or what if the instructions are inaccurate.

      Still, despite the risks, I would be interested in experimenting. The benefits may outweigh them.

    5. Tom says:

      Avi, you wrote “the text is shared, but the meta-data isn’t.” Can elaborate on that? Also, thanks for the link to your blog. I just subscribed to your feed.

    6. avi says:

      Sure :-)
      Suppose I am writing a user guide. The user guide’s draft is being circulated within the company: people from R&D, PM and QA are reviewing it, commenting to it and writing into it. Then, it returns to me for finalizing and delivering.
      Now, the way I am writing the user guide and the way I am managing the communication with my reviewers, [b]are not shared[/b].
      I either write notes for myself, or write no meta-data at all. Such data includes answers to questions like [i]how am I going to approach my next user guide[/i] and [i]what have I learned from the user guide I have just delivered[/i].
      Should I share such data? To what extent?

    7. I would think the main thing to get around is the monetary part once you figure out what you want to do. It’s something that I just can’t seem to get around, so maybe you can help me out.

    8. Penis enlargement products reviews that works best to gain 2-3 inches to your penis size naturally and produces hard rock erections in demand. http://www.penissizeenlargement.net

    Leave a Reply

    « »