Here’s 10 practical steps (or rather 9, #10 is not so practical!!!) that can enable an organisation to gain the support of its staff and the efficiencies inherent in project collaboration software (from TechRepublic)
#1: Start with the basics — incorporate everyday tools
Choose software with familiar, everyday tools, such as e-mail integration, Wikis, and instant chat. This makes introducing new software less intimidating right from the start.
#2: Consult users
Consult the people who will actually be using the software before making a purchase. Take it from the experts: “IT professionals, project managers, and business development managers should provide input into the PPM [project and portfolio management] investment decision; otherwise, the tool might not be capable of providing all promised benefits.” –Daniel B. Stang, Gartner research
#3: Try subscription-based
Subscription-based pricing is more flexible, so you can deploy on a small scale first to make sure it is right for your company. Pay-as-you go flexibility allows organizations to add or subtract functionality as needed, so you’re not locked into expensive commitments.
#4: Collaboration promotes adoption
Tools that offer enhanced collaboration abilities lead to more rapid adoption, as teams can grow virally and expand as more employees are pulled in.
#5: Simple, effective user interfaces.
Remember that it’s a user interface, not a developer interface — navigating the system shouldn’t be like solving a Rubik’s cube or completing a scavenger hunt. Rather, it should be brilliant in its simplicity. Choose software with a friendly, intuitive interface designed with the end user in mind, and people will be more willing to give it a try.
#6: Fast deployment = fast adoption
Common sense tells us the quicker a solution is deployed and is up and running, the quicker employees can familiarize themselves with it. T
#7: Adoption flows downhill
Lead by example. If others see team leaders using the software, they will be motivated to follow suit.
#8: Less is more
Make sure to distinguish between “must have” and “nice to have.” Inundating your team with a solution that has all the bells and whistles will intimidate and veer users away from a smooth adoption. Apply the 80%-20% rule. It works!
#9: It takes a village community
Offer a help community — quick, anonymous online assistance forums for troubleshooting and shared experiences.
#10: Offer cash rewards
When all else fails, bribe employees with cash and/or fabulous prizes.
Great list! We didnt offer cash rewards, we just made it part of peoples KPI’s that seemed to work quite well.
By: Sherif mansour on April 21, 2008
at 7:33 pm
KPI’s … great.. if you can get the buy-in of the senior management so that KPI’s can be updated !!! I’ve just put up a new post listing some useful facts when soliciting executive buy-in to a km/doc man project :
https://pjdnyc.wordpress.com/2008/04/22/building-the-business-casebuilding-the-business-case/
By: Peter on April 22, 2008
at 5:12 am