Group items matching

in title, tags, annotations or url

integrate with third party services

you don't have to waste time duplicating

Best Practices Learn how the pros achieve higher productivity through enhanced collaboration. Attention Management - Reduce time wasted in the Inbox. CC to Wiki - Get around the curse of Reply-to-All. Collaborating on a non wiki page using a wiki page - Use the attachment feature to collaborate on presentation files, etc. Designing Spaces - Key considerations for creating new spaces. Developing a Public Blogging Strategy Distributed Document Review Gardening and Wiki gardening tips Index Pages - create starting points for navigation around topics of interest. Lightning Editing - how to co-edit a document with a collaborator Securing buy-in - getting others to shift perspectives on wikis Sparking participation at events Using the workspace as a document repository

Best Practices Learn how the pros achieve higher productivity through enhanced collaboration > . > Attention Management > - Reduce time wasted in the Inbox CC to Wiki > - Get around the curse of Reply-to-All. > Collaborating on a non wiki page using a wiki page > - Use the attachment feature to collaborate on presentation files, etc. > Designing Spaces > - Key considerations for creating new spaces. > Developing a Public Blogging Strategy > Distributed Document Review > Gardening > and > Wiki gardening tips > Index Pages > - create starting points for navigation around topics of interest. > Lightning Editing > - how to co-edit a document with a collaborator > Securing buy-in > - getting others to shift perspectives on wikis > Sparking participation at events > Using the workspace as a document repository > Doing a demo Create tagging structures - Develop a core list of tags for your wiki Wiki Structure - Create a page which outlines important elements of the wiki Stop creating Word documents - The first rule of integrating wikis effectively See also Bonnes Pratiques for a chart of best practices and French translations.

Here are my thoughts on how to use a wiki page to collaborate on creating a non wiki page let say a powerpoint presentation. I am looking for feedback on this so feel free to add comments.

The challenge I have been running into is convincing CTOs, CIOs and CKOs that there are network effects. These people have invested heavily in pre-Web 2.0 "knowledge management" solutions. They view blogs and wikis as a threat to the possible success of their existing investments. They fail to realize that adding a wider range of productivity tools to the Intranet will add value to existing tools, rather than take away from them.Do you have any suggestions on how to communicate this.

A short answer to your question is that in such cases an appeal to corporate competitiveness might make the most sense. Enterprise Web 2.0 (or to use the emerging enterprise 2.0 tag) evangelists such as Andrew McAfee and Dion Hinchcliffe are always on the lookout for corporate success stories to publicize. I'd pay close attention to what they have to say. Often in public presentations they are challenged by corporate audiences to "prove that this stuff works." They always like to point to public examples -- when they can -- in order to rise above the hype. Being able to point out that a comparable or competitive company "is doing X already - why aren't we?" can be a powerful motivator.

As a cost-conscious consultant I would first want to know whether the existing knowledge management system can be augmented with newer collaboration, social networking, and relationship management features in order to extend the investments in infrastructure that have already been made.

Imagine the complexities of modern communications condensed into a seamless experience with one address book, one voice mail, and one login across every mode of communication. That's what Microsoft is doing. We're combining e-mail, IM, voice, and video into a single, intuitive system built around people, not technology. And we're building it all into the Microsoft Office system the world knows and trusts. Companies will replace conflicting systems with a single, unified communications platform that leverages their existing data and telecommunications infrastructure. IT departments will deliver more flexible, more secure communications, with simplified infrastructure that streamlines management and reduces total cost of ownership. People-centric, integrated, secure communications that's the promise of Microsoft's vision for unified communications.

Corporate Wikis reviewed: Confluence, JotSpot, WetPaint, Socialtext by Troy Angrignon on Mon 10 Jul 2006 06:30 AM PDT  |  Permanent Link  |  Cosmos Wikis are on the rise in corporations. And it's about time. One of the principles of Web 2.0 is that your user community can generate content that is better, faster, and probably easier to read than you can as a vendor. One way to enable them to contribute would be to build a wiki and let them flesh it out. Some good examples are coming up in this article: "Corporate wikis breaking out all over: MSDN Wiki" by Dion Hinchcliffe. (He has another great post as well called "Exploiting the Power of Enterprise Wikis") Quote of the day: "Not leveraging the contributions of a company's most impassioned and enthusiastic customers is starting to be seen as a significand oversight in many business circles." It appears in the article that eBay is using Wikis to better communicate between their users, partners, and suppliers. Now MSDN (Microsoft Developer Network) is using their pages to improve the quality of their developer documentation with the MSDN Wiki. THAT is a great usage. Your users often know your product better than your engineers and product managers because they have to live with it day to day. And guess what? If they tell the truth about some part of your product being broken - that's a GOOD thing.

Atlassian's Confluence is the best of them so far. Pros: the overall design is clean, it has advanced management tools, good security, and simple attachments.Its email function has to pick mail up from a POP box which makes it a little bit less ad-hoc but still functional. And most importantly, it also has great tools for moving pages around. Cons: Text editing, like with most apps these days is a bit dodgy, and pasting in blocks of text from Word is likely to cause problems. The pricing model is reasonable but for some reason (possibly because they're from Australia), they still don't have a directly hosted option so you have to use somebody like Contegix or deploy it on your own box. This seems to be a big and obvious oversight on their part these days. Also, their pricing model doesn't encourage small deployments right off the bat. I think this is the one that we'll use more of internally at the company where I work. Summary: The best of the enterprise wikis today, and one of the best options for scalability.

WetPaint is a newcomer that is doing some interesting stuff and that might be a better bet than JotSpot. Pros: The design is beautiful, the tool is very easy to use, the text editor is one of the best I have seen. Cons: I'm not clear on their entierprise suitability and it's not really their target market. It didn't appear that they had much in the way of administration tools, granular security, or any way to integrate into a back-end authentication system. Summary: I met one of the WetPaint guys at Gnomedex but he didn't seem to know the product very well. Hopefully next time, they'll put somebody more knowledgeable at their booth who knows the product in more detail. I think they're worth watching to see what they do in the next few months.

Confluence is an enterprise wiki that makes it easy for your team to collaborate and share knowledge. Adding, sharing and finding content has never been easier. These benefits come with all the additional features needed to make it a part of your business: Enterprise security Simple installation and management Attractive, user-friendly WYSIWYG interface Powerful tools for structuring and searching your wiki Professional features such as PDF export and automated refactoring An open API for extension and integration

The current release of Chandler builds upon the experimentally usable calendar for individuals and small workgroups. It is a test release for collecting feedback based on real usage. In addition to basic calendaring, advanced features include: recurring events; time-zones; overlayed, multiple calendars; and managing a single event across calendars. Chandler offers innovative capabilities in calendar sharing to support workgroup collaboration. Chandler sharing is server-based, works across platforms and supports multi-author editing. Our goal for our most recent release, 0.7alpha4, is to give a rough sketch of what Chandler will be by our first Preview release (Spring 2007). This release introduces the Dashboard, which gives users a runway view of all of their information. Users can try creating a simple task list, and can share that list with others just as they can share calendars. Users can also experiment with sending notes, tasks and invitations to others via email.

multilingual content management. It handles Chinese, Japanese, and even right-to-left languages such as Arabic and Hebrew with ease

Instant, Full-text Searching All content is searchable immediately; even Word documents and PDF files.

business processes part of the document workflow

The browser battle renewed today

Microsoft's hand may have been moved by the launch of Wolfram|Alpha

much promise in connecting people to knowledge

Google is preparing to launch Google Translation Center

This is an interesting move, and it has broad implications for the translation industry, which up until now has been fragmented and somewhat behind the times, from a technology standpoint

Google has been investing significant resources in a multi-year effort to develop its statistical machine translation technology.