• Save
Climbing Levels Of Collaboration
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Climbing Levels Of Collaboration

  • 4,082 views
Uploaded on

Groups can take action even quicker than before thanks to tools that amplify group communications, such as wikis, blogs, forums, social networks, and instant messaging. There are distinct levels of......

Groups can take action even quicker than before thanks to tools that amplify group communications, such as wikis, blogs, forums, social networks, and instant messaging. There are distinct levels of collaboration that a group can attain and what they accomplish directly correlates to the level of collaboration.

More in: Education , Sports
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
4,082
On Slideshare
3,939
From Embeds
143
Number of Embeds
4

Actions

Shares
Downloads
0
Comments
0
Likes
4

Embeds 143

http://justwriteclick.com 137
http://www.linkedin.com 4
http://www.slideshare.net 1
https://www.linkedin.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Groups can take action even quicker than ever before in history thanks to tools that amplify group communications such as wikis, blogs, and instant messaging. There are three distinct levels of collaboration that a group can attain and what they accomplish directly correlates to the level of collaboration. 1 Information sharing - this hands-on example would be just finding out information as any technical writer does, via email, phone calls, interviews, etc. 2 Cooperating - this hands-on example would borrow from Agile techniques to help shape a web application and online help going with it, more like a "we're all working at a startup in someone's garage." 3 Collaborating - this hands-on example would demonstrate how a Book Sprint is run with subject matter experts identified and working together to create an information deliverable, with FLOSS Manuals' wiki platform as an example.
  • Author of the book, Conversation and Community: The Social Web for Documentation I’ve had a lot of interesting collaborative authoring experiences plus I’m embedded on an Agile team and I’d like to share. Michael Cote challenged me to find good end user doc wiki
  • These are the classics of collaboration. Follow the rules. Be on time. Be professional. Share. Offer candy or chocolate. Interesting side note – more submissions to STC Intercom about “how to get info from SMEs” than any other unsolicited article topic. We know how to do this part. Exercise – design a transportation device Transport people between 1 and 10 miles per hour Stop on demand Carry at least one person Restrain at least one person (so they don’t fall out) Look nice Now imagine if I told you: Work alone! Don’t look at your neighbor’s paper! No collaboration! No talking! You’d each have a nice drawing at the end of a five minute period. Now, if I had you gather back together into workgroups, and you took the braking system from one design, the propulsion system from another design, and the restraints and aesthetics from another design, what would you get?
  • Agile development practices – Communication tools borrowed from the gaming industry offers voice interaction Video conferences Creating “ball points” example – went from 1 “ball point” to 5 to 50 due to iterations and learning from experience plus being willing to experiment Define crowdsourcing: delegating a task to a large diffuse group, usually without monetary compensation Iterations involve retrospectives – what went well? What would you change? (photo is a Bog oak floor in Denmark) What are some of these collaborative tools? Wikis are one. Other methods involve getting to know each other and your readers. Social bookmarking – show Wordle Social networking - Facebook, LinkedIn (search LinkedIn for your product’s name)
  • Wiki is a website that uses wiki software, allowing the easy creation and editing of any number of interlinked (often databased) Web pages. Based on permissions, users can edit pages Basic code is either wikitext (ascii based markup language) or HTML code - A wiki allows a group of people to collaboratively develop a Web site with no knowledge of HTML or other markup languages. Anyone can add to or edit pages Not just Wikipedia, your enterprise wiki is not Wikipedia
  • Enables simultaneous edits Give customer a voice and view point Living, breathing, changing documentation
  • Crowdsourcing is the term for the act of taking a task traditionally performed by an employee or contractor and outsourcing it to an undefined, generally large group of people in the form of an open call. Twitter mosaic
  • eBay wiki, now defunct, originally said their goal is to reduce support phone calls Open source wants open documentation Apache wiki, One Laptop per Child wiki, FLOSS Manuals free documentation for free software
  • from Wiki for Dummies Don’t go on wiki suicide missions Wikis don’t have magical powers. They cannot create camaraderie where none exists, nor can they streamline an out-of-control operation. They are not powerful information magnets, nor will they make your team better writers, more organized, or more intelligent. In short, without a strong guiding hand, wikis are useless. starting a wiki was in reality just a procrastination attempt—put off the real work of collaborating and cooperating with each other by distracting yourself with wiki engine research and selection and installation
  • What will your customers receive in return for their contribution? Borrow a point system from your customer support forums, perhaps? Points can be traded in for t-shirts or registrations to user group meetings or conferences.
  • Efficacy Reciprocity Reciprocity Reputation Reputation
  • First and foremost: Build a sense of community Adaptations on a theme - comments, wikislices, internal wikis Online forums Feedback from customers always looping to your source files Listen: Search.twitter.com for product name Blogsearch.google.com, search for product name Infoslicer at http://www.youtube.com/watch?v=Y0UDRi37MWM
  • OLPC chose a wiki as an open source solution to offering information to developer volunteers initially, but end-users also need documentation in their wiki. Mediawiki and Floss Manuals, which runs on TWiki. wiki.laptop.org contains all information about the XO laptop, but FLOSS Manuals contains targeted information for certain audiences. The structured nature of the wiki would let us re-use content for different audiences such as kids, parents, school admins, or teachers. Since they started with it from the beginning, the only changes I observed were my own learning and building of mental models for the use of wikis for information storage. Looking at WikiPatterns.com, which patterns or anti-patterns are in place? The Invitation pattern is a nicely done people pattern. They also have a nice Starting point on the OLPC wiki. And Welcoming is definitely a part of their best practices, even though it’s very difficult for them to keep up with the interest in volunteering. Have you done anything to encourage one pattern or squash out an anti-pattern? I know there have been acts of Vandalism on people’s talk pages, but those just get reversed immediately by a very on-their-toes administrator. I guess the act was in retaliation for an answer someone gave in an FAQ. I also see a little bit of ThreadMess going on with some development-oriented pages.
  • The original Book Sprint was invented by Tomas Krag, who wanted to get his friends together to write a book for wireless networking in the developing world. He thought he’d buy a stack of plane tickets, get everyone together to figure out the book’s outline, then send everyone home to write. What was unexpected is how much they got done just while in the same room together.

Transcript

  • 1. Climbing the Levels of Collaboration Or, How to Harness the Power of Crowds (or your Coworkers) Anne Gentle STC Webinar, September 2009
  • 2. My Story
    • Senior technical writer at ASI
    • Blogger at Just Write Click Started researching wikis at BMC Software Working on the FLOSS Manuals wiki and community
  • 3. Information Sharing
    • Co-location, email, IM, interviewing
    • The classics of collaboration. Follow the rules. Be on time. Be professional. Share.
    Photo courtesy http://www.flickr.com/photos/idletype
  • 4. Cooperating
    • Agile development practices : iterations involve retrospectives – what went well? What would you change?
    • Crowdsourcing
    • Computer supported (social web enabled)
    Photo courtesy http://www.flickr.com/photos/seier/
  • 5. What’s a wiki?
    • Created in 1995
    • Makes web pages quickly
    • Cross-platform, cross-browser
    Photo courtesy http://www.flickr.com/photos/7362334@N08/
  • 6. Wiki growth
      • Enables simultaneous edits
      • Give customer a voice and view point
      • Living, breathing, changing documentation
    Photo courtesy http://www.flickr.com/photos/jurvetson/
  • 7. Collaboration benefits
      • Encourage crowdsourcing
      • Scalability  goes up and up
      • Online identity
  • 8. Wiki matching
    • Return on investment by reducing customer support calls
    • Sometimes a customer forum isn't enough
    • Open source products often use wikis
    Photo courtesy http://www.flickr.com/photos/peterkaminski/
  • 9. What a wiki can’t do
    • Don’t go on wiki suicide missions (Wiki for Dummies)
    • Don’t put off collaborating with wiki engine research
    Photo courtesy http://www.flickr.com/photos/roland/
  • 10. Motivating community contributions
    • Reputation
    • Reciprocity
    • Attachment
    • Efficiency
    Photo courtesy http://www.flickr.com/photos/conanil/
  • 11. Reputation
    • Will your customers appear expert in your product if they contribute to your wiki? This type of motivation is especially important to consultants. Make their contributions shine so that they will return with more scenarios.
  • 12. Reciprocity
    • What will customers receive in return?
    • Can you borrow a point system?
    • BMC Developer Network example: points can be traded in for t-shirts
  • 13. Attachment, belonging
    • How will customers feel part of your team or part of your support team, if that motivates him or her? Association with a cause - wiki.laptop.org.
  • 14. Increased sense of efficacy
    • How will customers save time or money by contributing to your wiki? Consider a knowledgeable expert who feels she answers the same question via email over and over again.
    http://isnwiki.jot.com/WikiHome/Articles/111111431
  • 15. Test yourselves – Which motivation is in play?
      • I like to see which online forums have the quickest response times to questions.
      • I help out on the message boards because I know I’ll have a question that I won’t be able to answer, and I will get help when I need it.
      • When I was new to this technology or tool, someone helped me, so I want to help others who are just starting out.
      • I’d like to switch careers so I make sure my online answers are sharp and quick.
      • To promote and grow my consulting business, I’m learning more troubleshooting techniques by helping out with the scenarios that people bring to the community.
  • 16. Do you have to use a wiki?
    • First: listen. Then: participate, join a community Adaptations on a theme - comments, wikislices, internal wikis Online forums
    • Feedback loops to your source files
    Photo courtesy of http://www.flickr.com/photos/canoafurada
  • 17. FLOSS Manuals wiki
    • Why did you choose a wiki?
    • What type of wiki are you using?
    • How are you using the wiki?
    • What changes have you seen as a result of using the wiki?
  • 18. Book Sprint
    • FLOSS Manuals wiki and community
    • OLPC and Sugar Labs
    • Firefox and more
  • 19. FLOSS Manuals Book Sprints
    • Many lessons learned along the journey.
    • See http://en.flossmanuals.net/booksprints for a manual.
    July08: Inkscape, Paris Aug08: OLPC, Austin TX Nov08: Internet Censorship, upstate NY Feb09: Digital Foundations, NYC Mar09: Firefox, DocTrain West, Palm Springs CA Mar09: Command Line, FSF Annual Mtg, (Boston) Apr09: PureData, NYC & Berlin May09: CiviCRM, Truckee CA
  • 20. Wiki Patterns
    • Stewart Mader's website and book of the same name are extremely helpful for spurring wiki adoption.
    • Patterns describe a certain solution to a problem in a context.
    • To avoid problems, you want to follow a model pattern or be on the lookout for anti-patterns.
  • 21. Best Practices
      • Establish a working draft area and a “published” area (or wiki)
      • Write a wiki style guide
      • Give training on the wiki and a sandbox area
      • Maintain rules for arbitration
      • Offer original content, update content
      • Beware of spammers, and back up often
      • Join the community, be a genuine contributor
      • Recruit reviewers
      • Maintain categories
      • Watch recent changes
      • Expect small percentages of contributors and value them highly (90-9-1)
  • 22. Resources
    • Wiki tools research at wikimatrix.org
    • Wikipatterns website for adoption and people patterns
    • Meatball wiki
    • Anne Gentle’s podcasts on TechWriterVoices.com
    • ffeathers.wordpress.com - technical writer at Confluence
    • JustWriteClick.com – wiki category
    • FLOSS Manuals at flossmanuals.net
  • 23. Discussion
    • Questions?
    • www.justwriteclick.com www.conversationandcommunity.com
    • Contact: [email_address]