4 Replies Latest reply on Aug 2, 2013 10:38 AM by leigh_pankonien

    Top 10 Reasons to Bring Social Collaboration to IT - #swarm

    leigh_pankonien Beginner

      Screen shot 2013-08-01 at 12.43.39 PM.png

      A recently published article by Sue Poremba summed up the top 10 reasons to bring social collaboration to IT:

      1. Protect network information while enabling internal/external collaboration
      2. Build informal bonds
      3. Share dashboards and reports
      4. Lower the failure rate on IT projects
      5. Streamline company-wide communication activities
      6. Reduce admin burden
      7. Ensure the right people get access to the right info
      8. Grow the business
      9. Communicate securely
      10. Reduce email frustration


      Which reasons resonate the most with you? Are there any other reasons that should be on this list?


      I'm interested to hear from you: A Chapel Aaron Kim Adam Mayer Alan Lewis Adrian St. John-Bee Alex McKnight  Andrew Sommerfeld Andres Campos amit mahajan Andy Yates Angela Eick Ashish Trivedi  April Hicks Barry Pierce Ben Duguid  Bruce Weatherford Brian Shoemaker Bryce Williams

        • Re: Top 10 Reasons to Bring Social Collaboration to IT - #swarm

          As a long time IT Project Manager who has used Jive to successfully manage projects, I am going to go with 3, 4, 5, 7, and 10 that resonate most with me.  Where I have seen the biggest benefit is with taking the collaboration aspects of a project out of email (#10).  HUGE for a PM!  When the work is moved into Jive the PM and the team have access to all of the conversations, thus all of the decisions.  I have been a part of projects where once the work was moved into Jive, the weekly status update meetings became unnecessary and were cancelled.


          This did a few obvious things:

          • Gave that time back to the team to do productive work, not sit in uncessary meetings playing on their iPhone.
          • Meetings that did need to be scheduled had a very clear purpose with an accurate invite list.


          Moving the project communication out of email into Jive also did a not-so obvious thing

          • Projects timelines were accelerated because conversations and decisions happened quickly, allowing people to move forward quicker, not having to wait for folks to report out during the weekly status meeting.


          Adoption by IT is interesting, and always not as quick as you think it should be. Us IT folk are usually bombarded by many, many tools that are supposed to make our jobs easier, usually with the opposite result. Jive at the surface seems like another place to go to do our work. But in reality, Jive isn't replacing an existing tool (other than email,)  It is a new and powerful tool that gives IT a collaboration platform to get projects done quicker, which gives us project managers more time to create those reports that tell managers that our projects are all green in the Project Dashboard.

          • Re: Top 10 Reasons to Bring Social Collaboration to IT - #swarm
            thebryceswrite Beginner

            Our most impactful IT related benefits have been in the communication, training and support of IT services to users as an alternative to typical help desk style requests. This way people can help one another solve problems with technology and share tips on how to use the capabilities more effectively...and each time IT is helping people solve those problems it is done so in a visible, searchable and reusable manner...instead of only helping one person at a time solve their problems through more standard IT Help Desk type queries and tickets.


            Successful examples:

            - Outlook Support (email client migration support and communications)

            - Sharepoint Guru access

            - Office / Win7 comms and Q&A

            - Jive support (obviously)

            - SAP OCM and support

            - OCM, communications and support for our Mobility and BYOD programs

            - Information security initiatives


            We have pockets of the project management, team collaboration examples as well...but from an overall company scale impact...these virtual support communities have been very successful for us and continue to be copied for each new / updated IT capability. Sometimes because if teams don't proactively provide one for their service...the questions will appear in generic places anyway and pull them in. So by providing a space at least the interactions remain in a consistent context instead of organically showing up in other places.