Social media and intranet case studies, best practices, & evolution by Toby Ward.
View Article  Delivering a high-performing intranet (Case Study with Iron Mountain)
“There is an enormous thirst for communications... we really dedicate almost the entire home page of the intranet to communications,” Cheryl Travis, intranet manager, Iron Mountain.


Iron Mountain Incorporated (NYSE:IRM) helps organizations around the world reduce the costs and risks associated with information protection and storage. The Company offers comprehensive records management, data protection, and information destruction solutions along with the expertise and experience to address complex information challenges such as rising storage costs, litigation, regulatory compliance and disaster recovery. Founded in 1951, Iron Mountain has 20,000+ employees and is a trusted partner to more than 120,000 corporate clients throughout North America, Europe, Latin America and the Pacific Rim.

The following is a summary of the “Delivering a high-performing intranet (Case study with Iron Mountain)” intranet webinar on May 28, 2009, with Cathy Mcknight and Cheryl Travis.


6 stages of project management (Cathy Mcknight, Prescient Digital Media):

1- Enthusiasm

2- Depression

3- Panic

4- Search for the guilty

5- Punishment of the innocent

6- Rewards for the non-participants


Planning:


  • “Failing to plan is a plan for failure.”

  • “A good plan today is better than a perfect plan tomorrow.”

  • “Ensuring you have key planning documents in place (be it the style guide, or content plan)... it's absolutely critical, and its saved my (intranet) project in many ways,” Cheryl Travis, Iron Mountain

Planning involves understanding

  • business needs

  • functional needs

  • the right technology needs

  • resources (internal and external)

  • budget


Planning is done – now what?


Governance

    • Governance structure

    • Roles and responsibilities

    • Supporting documentation


Communications

  • Engaging leadership

  • Engaging content owners & publishers

  • Pre-launch employee communications

  • Launch

  • Ongoing communications (keeping momentum)


“We certainly need to engage leadership because frankly these are the people that fund the intranet,” Cheryl Travis, Iron Mountain


Content

  • Content audit

  • Content ownership

  • Approvals and publishing

  • Creating and repurposing

  • Translation

  • Archiving

  • Reviewing and updating


Technology

  • System requirements

  • Resource requirements

  • Ongoing support


(Note: Iron Mountain uses SharePoint for their intranet, Scout)


Site Build

  • IA

  • Wireframes

  • Design


“For information architecture (IA) and wireframes you can't rely on your own internal team because they live the company everyday,” says Cheryl. “You want the IA to live no matter how your organizations changes. To have a 3rd party to structure your IA is critical.”


Lessons learned at Iron Mountain

  • Engage content owners at the start

  • Rely on your independent resources

  • Trust your sixth sense

  • Keep communications lines open


“The sooner you communicate with them (content owners), the better,” Cheryl Travis, Iron Mountain.


The intranet gap


“What the business wants and what IT delivers can be two different things,” Cathy Mcknight, Prescient Digital Media. “An intranet is a process, not an event.”


“Its really good to have an outside expert to apply best practices,” says Cheryl “They have the clout and experience to do this (Prescient Digital Media).”

View Article  Intranet 2.0 becomes mainstream
Social media adoption has accelerated on the corporate intranet, led by blogs, wikis and discussion forums. Despite a low cost of entry—often below $10,000—adopters are not reporting outstanding satisfaction with the investment, especially among the executive ranks, driven by inadequate planning and weak or non-existent business plans.

This data is contained is contained in the results of the Intranet 2.0 Global Survey, which included the participation of 561 organizations of all sizes from across the planet.


Intranet 2.0 Global Survey Results

Once a nice-to-have or a future wish, Intranet 2.0 tools such as blogs, wikis and other vehicles have become mainstream, and are present in nearly 50% of organizations (regardless of size) in North America, Europe, and Australia and New Zealand,” says Toby Ward, the study author, and President, Prescient Digital Media.

To download a free, summarized version of the free report Intranet 2.0: Social Media Becomes Mainstream on the Corporate Intranet report or please visit:

http://www.prescientdigital.com/articles/download-summary-report-of-intranet-2-0-global-survey

To purchase the full, 44-page Intranet 2.0: Social Media Becomes Mainstream on the Corporate Intranet report of analysis & recommendations or please visit:

http://www.prescientdigital.com/articles/purchase-intranet-2-0-global-survey-report

Read about the results Intranet 2.0 becomes mainstream 

Technorati Profile


View Article  SharePoint website case study: Alfa Laval
(PHILADELPHIA, PA) External website case study using MOSS 2007 presented by Pernilla Webber, Alfa Laval, at J. Boye – Philadelphia 2009.


SharePoint has handled it very well (external website and extranet).”


Overview

  • Business to business company founded in 1883

  • Services: heat transfer, separation, fluid handling (heat exchanges, etc.).

  • Revenue: $2.7 billion Euros in annual sales.

  • Employees: 10,500 in 60 countries

  • Public website luanched in SharePoint in May 2008

  • Extranet planned for June 1, 2009

  • Intranet pre-study started for launch in 2010


Public website (www.alfalaval.com)

  • 3000 pages

  • 25 languages

  • 60 country sites

  • Pre-study: 1-year (planning, etc.)

  • Implementation: 1-year (launched May 2008)

  • Project team of 5 people

  • 50% of money on external dollars; 50% internal time and resources


Implementation strategy

  • Standard SharePoint

  • Limited external application integration

  • One platform for public website, extranet and intranet

    • Strategic direction

    • Operatonal efficiency

    • Functional development

    • Governance and resources (single governance structure for all sites)


Challenge / problem: Variation system

    • Custom development to allow for

    • Submit variation to slected country sites

    • Reject/Accept a submitted variation

    • Submit variation' doesn't work for web parts

    • Reuse of language versions not possible


Challenge: separating language/locale

    • Only one language version

      • Spanish in Spain, Chile, Colombia, etc.

      • English in UK, India, US

    • Many languages are supported – but its not supported to have one language for the CONTENT and another rfor the authoring environment


Challenge: Image management

  • Where is a particular image used? What pages?

  • Different versions of the same photo are not grouped together by type

  • Overly basic / simplistic


Challenge: creating forms (complicated for authors)

Challenge: formatting is difficult with standard editor (reusable cotnent doesn't work with the RadEditor)


Integrator: Fishbone Systems AB


Analysis: well this blows out of the water the notion that SharePoint shouldn't be used as an external website platform. The Alfa Laval site is impressive – with 60 sites in 25 languages. Microsoft would do well to add this to their case studies alongside Hawiian Airlines.


Visit the website: www.alfalaval.com


Technorati Profile


View Article  SharePoint Confessions – stories from life on MOSS
(PHILADELPHIA, PA) Presented by Dorthe R. Jespersen, J. Boye, at J. Boye – Philadelphia 2009.


Key recommenations:


  • Don't assume that because its used for the intranet, it will be good for the Internet

  • Compare with alternatives

  • Manage expectations

  • Keep it simple

  • Have a strategic plan

  • Get to know your IT

  • Focus both on micro and macro governance

  • Stay updated with service packs

  • Follow best practices

  • Pay attention to release information


Notable client quote: “Only after implementation did we start to learn about what the system could do. In hindsight we should have utilized the integration with office Word. Also, we are beginnning to rebuild our templates, as we didn't hink through the advanced features SharePoint offers the first time.”


Other learnings:


  • It's free!” - WSS is free, MOSS 2007 can be very expensive (particularly customization)

  • Training is required and costs money, as does maintenance

  • All Microsoft parnters are not created equal


Notable client quote: “I didn't know you could disable My Sites. Our integrator told us it wasn't possible. But you have done it already?”


Notable quote: “We are using Sharepoint 2003 and need to upgrade. But we've decided to skip MOSS 2007, and go for 2010 instead once that gets out.”


Technorati Profile


View Article  SharePoint dissected (MOSS 2007)
(PHILADELPHIA, PA – J. Boye) Insights from CMS Watch founder, and co-author of the CMS Watch Report, Tony Byrne.

Tony Byrne, CMS Watch:

  • SharePoint is part product, part platform, part ecosystem – a collection of technologies that have varying degrees of finish

  • Under-reported and under-appreciated dimension of SharePoint: built solidly on (almost) latest .NET platform

  • Be cautious of developer/integrator enthusiasm

  • Keep Implementation of SharePoint Simple (KISS)

  • Embrace configuration, some customization and integration, avoid extension (e.g. building custom applications, etc.)

  • The latest marketing from Microsoft is “to really finish or complete MOSS you should look to external partners.”

  • Oxcite, 3rd party open source blog tool for .NET (not SharePoint)

  • Just because a firm is a Microsoft partner, doesn't mean they have SharePoint expertise

Cautions:

  • Some MS partners / vendors are in over their heads

  • Not all are experts in all SP services

  • Temptation to over-engineer

  • Experienced integrators are in high-demand

Caveats:

  • Test performance, reliability, and security features carefully

  • Contrast software with "consulting-ware" (developed once for a client and re-sold)

  • Remember: its not just another module, but another vendor

  • Many partners fervently hope that MS will buy them, but Redmond typically recreates rather than acquires

  • This can be very inconvenient for you down the road with MS upgrades SharePoint


Technorati Profile

Search
    follow me on Twitter