As many of us know explaining exactly what social media, community and online collaboration is and how/why it’s different from what existed previously is sometimes challenging and more often than not frustrating. I just learned about this video, of Clay Shirky at this years Web 2.0 expo where he really breaks it down and makes sense of it all. One of the key takeaways is that media (both current and future) is not uni-directional but rather bi-directional. It’s no longer about simply consuming it, it’s really about consuming, creating and sharing. Another is: “Where is the mouse”. If you don’t know what that means, take a look at the video or at the very least read the transcript of Clay’s speech, I think you will get it.

My thanks to Jack McKee for posting about this video on his blog which brought it to my attention.

Sphere: Related Content

I can’t believe a little over a week has passed since I was at the digitalNow conference in Orlando. Part of me feels like I just left, part of me feels like it was forever ago. I guess all good things have to come to an end. The true mark of a great conference experience can be assessed both qualitatively and quantitatively.

At the end of each conference that I attend I ask myself the following questions: How were the individual sessions? How were the keynote speakers? How was the space and time managed? What was the quality of the interactions? Did I leave the conference knowing just a bit more about topics that I am extremely passionate about as well as topics I had never contemplated?

Similarly I also find myself evaluating the qualitative aspects of the conference as well. How many of the sessions were thought provoking or really worth attending? How many of the key note speakers would I want to see again? How many new people did I meet? Of those people that I met how many do I plan on staying in contact with? How many old friends was I able to catch up with? How many new ideas did I leave with? Of those how many are immediately actionable? How many can I act on in the future? If I had a choice of paying any amount of money for the privilege of attending the conference how much would I be willing to pay?

From both a qualitative and quantitative perspective I have to say that the conference was a great success. Very rarely do I attend a conference that I am conflicted between session times and across the whole agenda regarding which sessions to attend. This is one of the few exceptions in recent memory. I actually had to plan out my time really effectively and on a few occasions had to chose between two concurrent sessions that I wanted to attend. Needless to say the conference was programmed very well. I have to say the same for each of the keynote speakers. Of the four speakers, three of them (Chris Anderson, Jeremy Gutsche, and Dan Heath) left an immediate impacts on me, and only one left me questioning the relevance of her presentation (I later realized a lot of value from the presentation but will share that in a future post). Even so it was a good hit rate for the keynotes.

As far as the time and space goes, I have no complaints about either. There was a generous amount of time in between sessions to check voice mail, get a beverage or snack and network. The space was well used with a phenomenal ratio of space per attendee. The fact that the conference center was attached to the hotel made running back and forth between my room and the conference quite easily too. Add to all of those facts that we were within an earshot of Disney World and easily accessible transportation made the location pretty magical (pardon the pun) even for those who aren’t huge Disney fans.

The quality of the interactions perhaps one of the most important litmus tests of any conference was excellent. There was a great mix of attendees from senior executives to more junior staff members but all had interesting perspectives and plenty to share. The presenters, panelists and facilitators also represented a broad array of skills and experiences. When mixed together there was the right amount of people with the right kinds of experience so there was never a shortage of people to talk to, things to consider and ideas to glean. I walked out of the conference with a number of great ideas largely related to online communities and because that is my primary focus now, it was just in time. Some of the ideas were simply a result of synthesizing the knowledge that I absorbed by attending the sessions. However, many others were simply reactions (some positive, some not so positive) to something I saw or heard from other participants. There is no one source for ideas so I am happy to take them from where I can find them.

And as far as meeting up with new acquaintances as well as catching up with old friends the event was pretty good for that as well. Granted it wasn’t as well attended as some of the ASAE events where many of the folks that I am closest to (whats up Jamie, Jeff D., Maddie, Zach, Lindy, David, Andy and Jeff C. and a whole bunch more) but there was no shortage of great people here (whats up Greg, Ben, Rob, Andrew and Becky). Suffice it to say, a lively conversation was never far away. I was challenged as much by the conversations that I had after hours as the one’s that I had at the conference but the sum total of all of them contributed to the same end result. I learned a lot about a number of topics, learned some things about a number of great people and learned even more about myself. Without getting into the specifics (perhaps I will save this for another post) it was well worth the price of admission and then some. In fact I’d go so far as to say that any interaction that can return similar thoughts and idea generation guarantees an immediate ROI.

It goes to show that in the right environment with the right people and a common theme pretty incredible things can happen. So how do define a good conference experience? What qualitative and quantitative metrics do you use to measure personal and professional return on your conference investment? Drop your comments below. I am listening!

Sphere: Related Content

In Part 1 of this post I shared 12 Tips for Effectively Implementing Wikis in your organization. These tips included Form Following Function, Harnessing Peer Power, and Finding the Wiki Champion(s) in your Organization.

To continue the thread, here are 13 more tips that will help you to effectively implement wikis in your organization.

13. Reward activity

Create simple graphical reward badges for frequent contributions, moving a project to the wiki or any other activity that promotes adoption of the wiki. Badges should be placed on the user’s wiki page for everyone to see.

14. Create navigation pages to guide browsing across the wiki

Support for dynamic content is a must here, as the content will remain evergreen.

15. Encourage ownership and personalization

User pages are a great opportunity to experiment with features and gain familiarity with the wiki. Encourage users to personalize their own pages with widgets, badges (see tip 13),photos and feeds.

16. Use the wiki first

Most users already search the Internet but don’t know that the same facility exists inside the company. Whenever an opportunity arises, remind users to use the built-in wiki search first to find the information they are looking for before defaulting to other avenues.

17. A little latitude goes a long way.

Let users make mistakes; good wikis make it easy to reorganize content.

18. Integrate your wiki with in-house systems

Integrating the wiki with your AMS and other CMSs and allow users to create their own dashboards and mashups for daily activities.

19. Make the wiki part of the culture

Self-expression is important in teams and across organizations. Wikis are a perfect embodiment of self-expression that transcends organizational structure. Just make sure you know your culture and whether it will embrace a wiki or reject it before heading down that path.

20. One size does not fit all.

Wikis don’t work for all organizations. Your organizational culture needs to embrace the open exchange of knowledge and information in order for a wiki to succeed. Furthermore, single all-encompassing wikis seldom work in organizations. With wikis implemented at the organizational level, the concept of “spaces” or “projects” are almost always required.

21. Security is a must

Granular security with the ability to specify permissions—even at the page level—is often required for enterprise wikis.

22. Find support from those that stand to benefit the most.

Start with those who need it most. There is no single best practice on how a wiki should be rolled out within a large organization. However, it is often most effective to implement a wiki within those groups or departments that have immediate use for it. Forcing the wiki as a organization-wide mandate is usually not a good idea.

23. Let it go viral

As users within the organization send out wiki links or e-mail wiki pages, other users will get interested—or at least curious.

24. Know Thy Users

Depending on what wiki platform you choose to use, some require detailed configuration to use some of the more advanced features and functionality. Make sure you know what users want before rolling out your wiki and make sure that the functionality meshes well with the need.

25. It’s a numbers game.

The older the wiki, the more frequent the access. The greater the access the great number of lurkers. The greater the number of lurkers the more potential contributors. It all adds up.

Obviously this list is not all inclusive. What did I miss? What have you learned from your own Wiki implementation that others can benefit from?

References: eWeek - 25 Tips for a Better Wiki Deployment

Sphere: Related Content