“We already have program management,” is a typical statement I hear when speaking with a customer about collaboration program management. The unfortunate truth is, most organizations do not have formal program management or know how to effectively manage a Collaboration specific Program.
Instead, when talking about program management you should ask “Why is a collaboration program different and what should I consider?” Here are a few explanations:
There are many misconceptions about Collaboration Programs, but one of the biggest, and potentially most impactful, is that you only need to focus on the technology design and build. I can tell you from my experience in running many programs; a successful collaboration program requires a lot more than a successful technology implementation.
I’m not going to bore you with the formal definition of a program and how it differs from a project, but I will tell you that a successful collaboration program typically includes several non-technology projects (component projects) that must be planned and managed in order for the collaboration technology to be deemed a success. Examples include operational readiness, organizational change management, migration readiness, and more. Many times, programs fail to identify and manage these component projects. As a result, the collaboration program slows, business cases fail, ROI isn’t realized, adoption lags, issues arise, and satisfaction declines.
On the other hand, I have personally managed programs where these component projects were properly managed at many large enterprise, commercial, service provider, and government customers. The positive impacts of following the Collaboration Program Management best practices were obvious and tangible. The below metrics are some of the major documented impacts.
The impact of “doing it right” Read More »