If one considers the software landscape currently encountered in companies, it almost resembles a patchwork of various applications that more or less charts the company’s historical development over time. This begins with decades-old, self-programmed and custom-built solutions and extends to standard programs by different vendors that are used across the company divisions to deal with the same task.
It’s hardly surprising, therefore, that most IT managers feel a bit like zoo wardens when they are asked just to assess the solutions in place. The situation is not much rosier on the financial side, either: a confusion of license agreements with less than ideal purchase terms from a host of vendors place an additional burden on the IT budget. Every vendor solution, or to put it more astutely, every solution pen in this zoo, needs to be maintained and claims its own slice of the IT budget. Ultimately, after all, it is the zoo warden’s job to make sure all the animals are fed – or isn’t it?!
So it will hardly simplify the current or future vendor situation in a company when even more solutions – in this case Office 365 – are up for rollout. Does it have to be this way?
I would like to use this article to address a number of aspects and, among other things, to present possible solutions for the successful rollout of Office 365: