IBM Connections is a great piece of software. It is not designed to solve certain business cases though. As a matter of fact, people have to find ways to map their business cases to IBM Connections. Moreover IBM Connections is an empty shell and heavily relies on people to use the system. People only tend to use systems though if they find valuable content that helps solving daily problems. But that content has to be provided by people so it is like chasing one’s own tail. These are two crucial points that make IBM Connections adoption a difficult task.
One strategy to overcome this is to install Community Managers who work with users to find ways to map their business cases to IBM Connections. Another strategy is to automatically provide and migrate content from other systems into Connections in order to get and keep the system alive and kicking.
We will discuss this and show how to deal with it in order to make a Connections roll-out and the product life thereafter a success.