Bram Grigaitis and Chris Becker's PwC Presentation and Notes -- NY/NJ User Group, October 16, 2015

Version 3

    (These are my notes from agrigaitis and Chris Becker's presentation at the October 16 NY/NJ Jive User Group.  If you have more questions for Bram and Chris, please leave them below in the comments!)

     

    PwC has an internal Jive instance called Spark, along with 3 external communities.

    • Spark is a pretty mature community, has already hit new highs, new plateaus, of user activity and is now asking the question, what is this platform going to become?  How might others potentially use and integrate with this community?
    • Globally based community, globally based team, and working to enable the various territories and empower people to do what they need and want to do.
    • Spark is 'open' in the sense that anyone can create a group. There are processes to monitor compliance with terms of use but generally people are free to leverage Spark to suit their needs.

     

    Program, Change and Stakeholder Management

    • Success has come largely from a focus on the change and people side of the program, and less on the technology. While some customizations have been necessary, its been more on the backend side due to risk and security. Features and functions are less of a focus.
    • Consulting effort is focused on working with teams that have use cases that drive the most business value and can be best repeated by other groups / teams (e.g. proposals, portal replacement).
    • Helping people to understand and embrace the journey towards open and transparent ways of working has been the biggest challenge but also one that is driving the greatest competitive advances.

     

    Compliance and data privacy:

    • Challenges in the past have included how to have client confidential discussions - have used plugins in the past and are looking to transition to using add-ons or even developing custom APIs for Jive.
    • Hosted by Jive:
      • They use Jive servers hosted out of Amsterdam, since many European countries are more comfortable with data being hosted there as opposed to in the US.
      • They also use the external storage framework to store certain types of content in certain areas depending on where you are.
    • E-discovery is also necessary and they have developed a solution that creates "glass walls" so that the community can be collaborative while also giving access to lawyers, etc., who need to perform searches.

     

    Jive for Office was one of their biggest wins and was quickly adopted by the sales team who used it to draft their proposals - this sort of key use case allows Jive to get embedded at your organization.

     

    Performance:

    • They leveraged Akamai to improve page load time, along with OOTB stuff.
    • They were able to decrease average page load time in some countries from 16 seconds to 5-6 seconds.
    • Jive 8 is a fundamental re-architecting and may solve a lot of performance issues that PwC had to solve for using other methods.

     

    Use Cases in Spark:

    • Site "Navigator"
      • Size & scale of implementation makes it difficult to visualize the site
      • "Navigator" provides an interactive data visualization tool which allows you to see communities and content based on tagging (this is generated automatically when a user creates a group and a script asks them questions about the purpose, confidentiality, etc. of the group, then applies tags)
    • The "Proposal Hub"
      • Team devoted to developing porposals to sell has a space to provide access to their tool sets
    • "Portals use case"
      • Have had a lot of success using Jive for portals, especially replacing SharePoint and other heftier tools
    • "Dr!ve"
      • A retention initiative that allows people to apply for 2-3 week secondments - application/postings are within Jive and information is stored in a the background with an API

     

    International/multilingual communities:

    • How do you give people the tools to collaborate in a decentralized, internal community that spans countries and languages?
    • "Look Inside" is an onboarding community for people who have been hired but have not yet joined PwC, to smooth the new hire experience.
      • Idea is that they set up some basic rules and created separate communities for each country.
      • Each country may not only have different languages, but may also have a different idea of the mixture of laungages they want people to use.
    • At PwC, machine translation would not fly, so they have people translating important content and use tools like "Dotsub" to do time-indexed translations of videos.
    • Crowdsourcing is an important tool at PwC, and they believe that if they are commanding and controlling, they are not embracing the spirit of Jive. There is also the need to enable teams to manage and own the change so a decentralized approach tends to help drive this change.