mobile-workerWith demand for collaboration solutions increasing, organizations that were early adopters can teach late adopters some valuable lessons regarding their experiences, both good and bad. Over the past two years, especially the last year and half, the industry has witnessed an increased demand for IW solutions due to an increased mobilized workforce and traditional IT simplification projects. Generally, for IW solutions to be successful, a multi-faceted approach (Governance, tools, people etc…) are required. From a Microsoft perspective, the core of collaboration for Microsoft is SharePoint technologies (Including Lync, Exchange, One Drive etc.). For IBM it was Domino but is transitioning to Web Sphere based solutions. In this Blog I will share some of my experiences with clients, identify pitfalls and recommend an approach to use with clients once they have made the decision to adopt IW tools.

What are Collaboration Solutions?
Having worked with Collaboration technologies since 1991 (Lotus Notes) and SharePoint technologies since 2001 I’ve noticed some trends. Typically, when people think of Collaboration, they think SharePoint (or Notes) only, but to address most of the business problems that organizations are faced with today, their Collaboration service offering must include the following tools:

  • SharePoint – Presence for collaboration, application integration and delivery, document management, workflow, search and social networking to name a few.
  • Lync – Presence awareness, Instant messaging and video conferencing.
  • Exchange – Messaging, calendaring and contact information as well as SMTP engine for SharePoint.
  • Livemeeting – One to many voice and video conferencing.

As with any tools, they are only as successful as the organizations ability to adopt them. Specifically, a change management program that introduces policy, training, mentoring and adoption measurement must also be in place -.Search on my “user Adoption Framework” Blog for more information.

Maturity Model
That’s a handful of technologies and quite the undertaking to prioritize, design, deploy and operate! I prefer to model the technology adoption using a maturity model of sorts which is as follows:

  1. Stage One – Establish/Ready the foundational IT services, technologies and operations. This technology includes authentication technologies such as AD, security such as VPNs and virus protection, server consolidation/optimization and storage and consolidation/optimization. Provide the basic devices and access to the corporate network. Also, user adoption plan developed to influence culture and measure adoption is developed
  2. Stage Two – Establish collaboration environments and develop rich information architectures that support communities (practice, professions, interest) and optimize them for efficient search and browsing. The access to the systems is optimized for mobile workers whereby anytime anywhere access is provided through laptops and smart phones as best makes sense. User adoption plan executed to influence culture and measure adoption is developed.
  3. Stage Three – consolidate, integrate, leverage and retire your application portfolio. Develop rich composite applications that leverage corporate data sources, documentation and workflows. Develop business focused social networks to truly leverage the organizations IP (products, services, knowledge, contacts etc…). Also, ongoing user adoption execution and measurement ongoing until target adoption levels reached.

Figure 1 depicts the model visually:

iwmaturity

Figure 1: IW Maturity Model

Impacts of IW on IT and the Business
It has quite an impact on the business when staff and management adopt and integrate Collaboration tools into their day-to-day business tasks and operations. Let’s have a closer look at the impacts in more detail for both IT and the business:

  • IT – several foundational technologies are required such as networking (internal and external), security, authentication, servers, storage, management and operations. Additionally, staffing for these technologies is required in order to provide help desk and other forms of support. Finally, service arrangements with outsourcing and leasing companies have an impact.
  • Business – the staff and management are busy supporting clients and their business partners. Generally bound by policy and procedures (Company and regulatory to name a few…), they have day-to-day objectives and tasks to carry out. Remembering that people generally resist change (and like routines that don’t change) introducing new technology is viewed as disruptive (unless it’s fixing something that is terribly wrong).

The Typical Painful Journey
With so many impacts to manage, it’s a handful for most organizations to manage successfully. Based on experience with organizations large and small, most don’t get it right and both IT and the business suffer for it. In many cases clients take the following approach:

  • Stage 1 – Consolidate Collaboration applications (Intranets, Portals, collaboration tools etc…). They move from 4-5 tools down to 1 or 2 and dump the data into the tools with little rigor applied. Operationalizing the tools generally means just opening the door and letting the tools sink or swim. It is focused on IT plumbing and not information and people.
  • Stage 2 – The sink or swim generally leads to sink. The tool becomes bloated with useless data, navigation becomes difficult and search returns hundreds if not thousands of pages filled with useless data. Why? No user adoption plan, information architecture, content management disciplines and governance of the service offering.
  • Stage 3 – The realization that a mix of governance, information architecture, process, policy and staffing is required for the service to be sustainable with any level of quality. For example, at the moment two of my clients are struggling with the same problems.
  • So why do things go wrong? Generally, organizations begin with a vision that is well intentioned but later degrades to let’s just get something done to meet the dates enforced on us my senior management. Also, much of Collaboration adoption is not well known as compared with Email (such as Exchange), which has been around for decades in some form or another. Exchange patterns and practices for requirements, design, deployment and operating are well known.
  • Governance – a companies lack of appreciation or understanding of governance and maintaining the environment / sustaining the culture” – e.g. this is where training for end-users / administrators and Information Managers is required, how to operationally implement content management or collaboration based policies and standards. Basically Collaboration culture does not happen on its own – governance that is implemented and controlled nurtures it.
  • Unrealistic dates – usually set by a new executive trying to make their mark or external factors that force dates (such as compliance).
  • Unrealistic expectations – a vender oversells their product and or the solution marketing campaign within the organization was hastily assembled and delivered.
  • Too many projects on the go – the average large organization has thousands of projects on the go at any given time. Understanding the collision points and dependencies is usually the challenge.
  • Too many new technologies – new technologies are not well understood and their quirks/bugs are unknown. These sorts of unknowns can add weeks and or months to a project.
  • Staffing and skill set shortages – with so many organizations running leaner these days, it’s difficult for them to juggle skills and ramp up for new technologies and or contracts when demand is high. Work all day and learn all night might be a good analogy!

A Best Practice Approach
Back to the subject of trends, when thinking about maturity models for Collaboration solutions, experience has taught me to architect and grow IW solutions using the following approach:

  • Establish governance – this consists of executives, department management, department SME, PMO, Architect team and purchasing.
  • Staff your team with experienced consultants – knowledge transfer is key to your staff and leveraging experience is key to reducing risks.
  • Assign (dedicate a %) your staff to the project team – your staff won’t learn nor accept ownership unless they are involved.
  • Understand your organization’s information management needs – many compliance officers are concerned that Collaboration solutions will complicate records management enforcement.
  • Design a service model for Collaboration – approach Collaboration as a service offering and adopt a service level approach to developing your architecture.
  • Content and Systems Strategy – in order to drive user adoption the user experience (and cost savings) must be compelling.
  • Information Architecture – in order to build and sustain a usable and intuitive environment, the layout of the sites, pages and content must aggressively managed (governed) using content mgmt disciplines and security as best makes sense.
  • Collaboration architecture – the architecture for your IW solution whether it stands alone or is integrated with existing or new systems.
  • Systems Architecture/Impact analysis for the infrastructure that will support the Collaboration solution.
  • Realistic project charter and schedule – a project charter, schedule and staffing, amongst other PMI recommended process and artifacts.
  • Tailoring this approach is key to success since many organizations will have completed work in some of the areas. Expect gaps but don’t force them to reinvent the wheel.

Summary
With the upward trend of Collaboration solution demand, we have an incredible opportunity to provide solutions based on Microsoft technologies and your hardware and software and third-party solutions that bolster the solutions functionality, performance and manageability. I’d like to hear from you regarding your thoughts on this Blog and ideas you have to improve the approach!

Advertisements