Introducing a social intranet at Freshfields Bruckhaus Deringer
2 likes1,822 views
The document discusses the transition of a static intranet to a more dynamic and collaborative environment in response to user needs for better content accessibility and maintenance. It highlights the implementation of wikis for document creation and discussions among globally dispersed teams, along with training and communication strategies to foster user engagement. Overall, the shift led to increased participation, improved information management, and enhanced collaboration within the organization.
Introducing a social intranet at Freshfields Bruckhaus Deringer
- 1. Confluence User Group 28 April 2010 Stephen Perry Knowledge and Information Management Adviser
- 2. Agenda Business need Example uses Change management elements Lessons learnt Overall result
- 3. Business need Needed to move away from the static intranet to a more collaborative, participative and dynamic environment Content was out-of-date, difficult to find and complex to maintain High resource/time costs due to repetitive, labour intensive processes with long review cycles and limited number of editors Interfaces not consistent or easy to use Low user satisfaction and usage
- 4. Example – Private Equity Group
- 5. Example – ITG Sector Group
- 6. Example uses Creating a document Groups quickly create Wiki spaces for pitches, thought leadership or know-how Globally dispersed teams are directed to the Wiki to make their contributions Central team then collates the information and builds the document from all the material in one space US Partners discussion forum Wiki space allows the US Partners to discuss, debate and agree the key issues facing the business
- 7. Change management elements Adoption Basic & Advanced training (via face-to face & Webex) 5 minute ‘viewlet’ created for Fee-earners Project Wiki & on-line support Sense of friendly ‘competition’ Consistency not necessary Participation not mandated Key influencers targeted Increasing collaboration to drive business benefits
- 8. Lessons learnt What would we have done differently? Planned the content migration in more detail Agreed earlier how to measure and monitor usage Identified more business processes which would benefit from the Wiki Initiated more two-way communication between users and the central team Built a coalition What worked well? Tight/loose approach Clear business need and part of the firm’s strategy Did not over-promise Focus on usability and user centric design Communication of good practice
- 9. Overall result Increased intranet use and participation Cost-effective capture, maintenance and delivery of firm and client-related information Better informed staff with access to timely and relevant legal intelligence Improved collaboration and knowledge sharing between globally dispersed teams Huge demand for new content areas Users have now adopted the intranet as their own
- 12. Why we chose Confluence to replace FrontPage Needed lightweight, flexible, low cost approach Wanted ownership of content in our practice/sector groups Supported a structured intranet and flexible collaboration spaces Ease of use and simplicity Low barrier to participation Recognised as ‘best-of-breed’