So your company or organisation has decided to splash out on the latest shiny new version of MS Office. It has been budgeted for, a team has been formed to handle the hardware, O/S and software implications, then the person in charge suddenly realises that beyond the investment and struggle to get the money to pay for the new software which can be used to leverage the ERP, CRM and LMS etc..systems, that this project is going to affect every user within the organisation. This project is going to have a major impact on the company.
At that moment you happen to be walking past that manager’s office and you hear the authoritative voice of the manager (thanks to a recent training course):
“John (or Jane) I’m glad I saw you, I just wanted to warn you that I am going to be sending you a meeting invitation to discuss a new training project that I would like you to take point on…..”
So here you are a week or so later and you are having to think carefully about how to proceed. The important thing at this stage is to gain an understanding as to what the reasons are behind the roll-out and what, if any budget you have got available to you.
The main reasons normally for a roll-out for MS Office is for either technical or/and business.
If technical it might be because the old version of MS Office is no longer supported or perhaps fit for purpose or the organisation is changing from MS Office to Google Documents – this immediately gets one thinking:
- How different is the interface between the new and old MS Office?
- Differences between the old software and the new?
- Are the files compatible between the old and the new?
- Within the new MS Office(?) suite are there going to be the same applications?
- Are users going to get OneNote?
- Will the way users use the new MS Office suite going to be different from the old?
If the roll-out is because of business reasons it might be that certain utilities or perhaps a certain version of MS Office is required, for example MS Office 2013/ Office 365 might be required in order that Sharepoint 2013 works as intended, again more questions are raised:
- Is there a deadline as to when this roll-out needs to be completed by?
- Are there any alternative solutions?