Group items tagged

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.

When faced with the choice of learning new technology and chatting to colleagues on the phone and email to get a job done, if it can be done with what they already know they will go with that; Collaboration tools work best when your collaborators are geographically distributed and in other time zones and I wonder how many teams have that as a situation? Sure, globalisation is spreading and small, nimble operators are connecting using these tools, but how many large corporations are active users? I know IBM is and I would imagine technology firms would be at the vanguard. I was surprised however when PriceWaterhouseCoopers consultants arrived in IBM because there were unfamiliar with collaboration tools and disinterested in using them. It works best when all the collaborators are equally enthusiastic and capable in using the tool. It just takes a handful of influential members of a team to stop using the tool for the tool to be abandoned. The majority of people in organisations are baby boomers (I'm not sure this is true) and haven't been brought up in environment using collaboration tools. I was in a pub the other day meeting our complexity group and I overheard a small group of people in their 20s and 30s talking about the MySpace interactions. These people already know how to use the tools and will expect them in the workplace.

What happens when the data flow is asymmetrical - but in favor of creators? What happens when everyone is uploading far more than they download? If everyone is busy making, altering, mixing, and mashing, who will have time to sit back and veg out? Who will be a consumer? No one. And that's just fine. A world where production outpaces consumption should not be sustainable; that's a lesson from Economics 101. But online, where many ideas that don't work in theory succeed in practice, the audience increasingly doesn't matter. What matters is the network of social creation, the community of collaborative interaction that futurist Alvin Toffler called prosumption. > As with blogging and BitTorrent, prosumers produce and consume at once. The producers are the audience, the act of making is the act of watching, and every link is both a point of departure and a destination.

And who will write the software that makes this contraption useful and productive? We will. In fact, we're already doing it, each of us, every day. When we post and then tag pictures on the community photo album Flickr, we are teaching the Machine to give names to images. The thickening links between caption and picture form a neural net that can learn.

The more we teach this megacomputer, the more it will assume responsibility for our knowing. It will become our memory. Then it will become our identity.

For many of us, a piece of chalk represents a time in our lives when anything was possible. A time when we were learning, building, communicating and most importantly - having fun. So when we decided to create a great collaborative web application, it seemed like the perfect name. However, like back in school, our imaginations started to run rampant with ideas. It didn't take long for us to realize what we really wanted. Something that takes us back - not to the classroom or playground, but to a world where we can create and collaborate freely, with friends, colleagues or even strangers. Designers, programmers, writers, family, friends - anyone. We all want tools that make us more productive, especially when we're working in groups. Chalk gives any team an immediate, real time collaborative environment thats accessible from any computer in the world. Do you want to share your ideas, code or graphics instantaneously with others? Chalk is already changing the way we work, and we're sure it will for you. Oh, and did we mention Web 2.0 yet? Chalk communication is in real time, powered by the excellent Ruby on Rails and AJAX, and it's fully compatible with Internet Explorer 5+, Firefox, OmniWeb and Safari. Not to mention the excellent social features we're still adding such as buddy lists, instant messaging and even entire community hub - all without a single page refresh and just a mouse click away. The end product is almost ready. We've come a long way in a short time, but we're about to graduate (hopefully with honors!). We hope you'll be there at the ceremony so you can take Chalk for a test drive. Until then, sit tight and tell your friends - after all, thats what Chalk is all about, sharing.

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.