Rolling out Features of an Emergent Collaboration Platform

0
20

Share on LinkedIn

After selecting a vendor for your enterprise collaboration initiative it’s tempting to just release the product with all the features to the company. This is not the most effective way to roll out a platform as it will overwhelm the employees who are going to be using it. Many tools and platforms today come with quite a robust feature set but that doesn’t mean they should all be released at once. In Andrew McAfee’s post entitled “Drop the Pilot” he states that organizations should:

“Deploy tools that deliver a novel capability, like microblogging, social network formation, or prediction markets. Tools that deliver something novel — that aren’t trying to displace an incumbent”

I mostly agree with this and this is something I am seeing work quite well within organizations. The most effective features to start with are those that can be familiar to employees while offering a new way to solve an existing problem that employees are currently faced with. However, I would actually not start with “prediction markets” as McAfee suggests as they have a much higher learning curve then some of the other simpler solutions such as microblogging or rich profiles.

There isn’t a specific timeline for when the entire feature set has to be rolled out, this should be gauged based on employee usage and feedback of existing features. For example if you find that employees are struggling with understanding how to use microblogging then spend some more time on this and roll out additional features later. If however employees are quick to adopt and use microblogging (basically if they are comfortable with it) then you can release additional features much sooner. Overall you might roll out all the features in a few months or in a year (or longer). Remember every feature that you roll out can have several different uses, so get employees comfortable with a few of them first.

Just because the vendor you go with has the capability to do everything doesn’t mean you want it to (at least not at the start). I encourage a phased approach to deploying these tools as I think it will help with employee adoption and the overall comfort level with using these tools.

A few final things to remember

  • Start with simple yet valuable features that employees will be comfortable with (such as rich profiles and microblogging)
  • Wait for employee adoption and comfort level to rise with existing tools before adding new ones
  • Features can be rolled out in any timeline that makes sense to your company
  • Don’t roll out everything at once as it will overwhelm employees and the learning curve will be steep

Republished with author's permission from original post.

Jacob Morgan
I'm a best-selling author, keynote speaker, and futurist who explores what the future of work is going to look like and how to create great experiences so that employees actually want to show up to work. I've written three best-selling books which are: The Employee Experience Advantage (2017), The Future of Work (2014), and The Collaborative Organization (2012).

ADD YOUR COMMENT

Please use comments to add value to the discussion. Maximum one link to an educational blog post or article. We will NOT PUBLISH brief comments like "good post," comments that mainly promote links, or comments with links to companies, products, or services.

Please enter your comment!
Please enter your name here