Future Changes

The nasty four-letter word that must be banished from the web

BusinessWeekIn a BusinessWeek article on the Google Sites launch, Dave Girouard, manager of the division that oversees Sites says:

“We are literally adding an edit button to the Web.”

But no mention of the word wiki, the very idea that has powered the rise of that “edit button.” In his writeup of the launch, Om Malik says:

“I bet like me, no one wants to deal with another wiki.”

No one? Really?

Fortunately, The CNET & ZDNet guys take a much more levelheaded approach, and point out Google’s haste to banish “wiki” from the web:

Larry Dignan says:

Frankly, none of this rebranding works all that well. It’s still not clear what Google Sites is about judging from its name. Google is trying to mainstream the use of the wiki but without the name. But Google Sites doesn’t exactly bonk you over the head with meaning either.

Overall, Google Sites is a collaboration app for people that are managing projects or classroom activities. In other words, it’s wiki-ish.

As for the branding–Jotspot to it’s-not-a-wiki to Google Sites–Google didn’t exactly clarify much of anything.

Rafe Needleman says:

Call it what you will (it’s a wiki, ok?)

Dan Farber says:

The term “wiki” has been banished from Googlespeak as the company tries to mainstream its collaborative applications. “There shouldn’t be a distinction between wikis and sites,” said product manager Scott Johnston. He hopes that the “edit button” becomes pervasive as the collaborative Web takes hold.

Johnson’s answer is interesting from a long-term perspective, but I don’t think banishing a term that many people in the mainstream are just beginning to understand, and value, is the clearest approach. Google should look to Apple, which does a much better job of easing major cultural change into the mainstream.


3 Comments

  1. I’m not sure I fully agree with you.

    The term ‘wiki’ scares a whole lot of people who are not really into this whole web 2.0 / Enterprise 2.0 stuff …

    Also that term generally brings the word ‘wikipedia’ in their mind, and the use of the wiki technology can bring something completely different,which confuses those people even more …

    I’m starting to lobby inside our organization to implement blogs and collaborative online spaces (yes, wikis! ;o)),and I can tell you that its easier to tell people about a document that different people can contribute to, rather than using the word wiki …

  2. Guy says:

    From what I see of their marketing materials so far, they are promoting Google Sites as a replacement for online website authoring tools. The various examples they give are all basically the same thing – pages with various, presumably templated, containers. I’ve not been able to get in and test because it will likely munge my other google services associated with my email address (quite annoying) but I can see where they are coming from – they see the underlying wiki technology as a great way to make common website scenarios easily editable online.

  3. New Google Sites Application Misses Mark

    After waiting expectantly for the release of Google Sites, the success to Jotspot, for more than a year, I must confess I’m pretty disappointed in the result. The user interface is clunky and non-intuitive and offers little new in the way of collaborative tools, other than Joomla-esq shared web page editing.

    What happened? Google already has a terrific widget enabled web page creation tool. It’s called Blogger! Why didn’t they use that technology to make dropping various functional elements onto a page easy?

    The ability to quickly create an Intranet/Xtranet of four to twenty pages is what most of my SMB clients are looking for. Doing this with SharePoint has always been too developer and infrastructure intensive, leaving us to recommend products like WebOffice (formerly Intranets.com) and Blue Tie as web-based collaboration tools.

    BlueTie in unique in that it offers unique ways for partners to monetize the solution and generate a unique ongoing revenue stream. In fact, BlueTie was recently recognized as an OnMedia Top 100 Winner.

    Google has missed the mark badly with its Google Sites application. It’s unfortunate, because it takes the pressure off Microsoft to improve SharePoint’s ease of use and Cisco to lower the cost of WebOffice.

    Until Google releases a Google Sites application that is significantly easier to use and functional, I will continue to recommend WebOffice, Blue Tie or our own TeamPro application as a Intranet/Xtranet solution.

Leave a Comment

Stewart Mader is an author and expert on technology adoption in organizations. He has published two books, Wikipatterns and Using Wiki in Education and has written for Science Magazine, ZDNet, The Content Wrangler, and Software Development Forum.
He is a dynamic speaker, experienced project manager, and is available for consulting engagements. Details
WIKIPATTERNS
A Practical Guide to Improving Productivity and Collaboration in Your Organization
  • Amazon.com
  • 800-CEO-READ
  • Free Chapter
  • Wikipatterns book: a practical guide to improving productivity and collaboration in your organization

    USING WIKI IN EDUCATION
    Case Studies from the Classroom
  • Amazon.com
  • Lulu Press
  • Examples & Resources
  • Using Wiki in Education wiki book


    Loading
  • Enterprise Wiki Software Guide - Tools & Capabilities
  • Why Businesses Don't Collaborate - Research Report
  • 21 Days of Wiki Adoption - Video Series
  • 8 Things You Can Do With an Enterprise Wiki
  • Who Owns the Wiki? 4 Key Groups
  • Timeless Patterns in Technology Adoption
  • Failure to Launch: Factors Behind Stalled Adoption
  • Rules are for Impatient People
  • Better Project Collaboration Using a Wiki
  • Geometrica: ISO 9001 Certification With a Wiki
  • When is a Wiki a Tool, and When is it a Medium?
  • Guess What: It is About the Tools
  • When Starting a Wiki, Don’t Forget Design
  • Wikis in .edu: Teaching Students to Share Knowledge
  • Interview: The State of Wikis in Education
  • Would You Pay 5¢ to Read This Article?



  • BARNRAISING WORKSHOPS
    A BarnRaising is a planned event that I use to help teams get started using the wiki. I start by having people look at examples of social software use in organizations to help focus their thinking on how it can help them, then identify specific workflows or business processes they want to improve. During the half-day workshop, the team gets its workspace set-up, structured, and seeded with content directly tied to the uses they've identified, so that when they return to their day-to-day work, the tool is embedded into their day-to-day workflow.



    PILOT, POLICY & PATTERNS
    I can work with your team to define project scope, assess cultural readiness, create policies and procedures, run a pilot, and manage large-scale deployment. I recommend developing a procedure to handle requests for new workspaces, a scalable naming convention, data retention policy, and careful communication policy. I’ll help you define content and workspace structure, develop templates and procedures for seeding the wiki with content, and migrate information to the wiki from tools that will be deprecated as a result of this project.

    Based on our information gathering, we’ll compile a list of people and groups who should be involved in the pilot phase. As their use gets underway, I’ll advise them as needed, assess their progress, and suggest refinements. To prepare for large-scale adoption and use, we’ll analyze usage patterns from pilot groups, identify critical integration and performance issues and recommend solutions. We’ll also capture anecdotes and examples to share with other groups during broader adoption.



    RETURN ON ADOPTION (ROA)
    I measure success in terms of Return on Adoption (ROA). This means that we take more into account than just the financial investment, and look at metrics that can’t easily be manipulated or give “red herring” results. For example, we'll look at the average number of edits and comments on pages, and based on content types (referential, workflow, project, etc.), and business units, because these directly indicate the level or participation by employees. Trends, or patterns, in these figures over time help to assess the pace of adoption, where usage is most active, and where we need to spend more time guiding people.




    Recommended Websites