Married to memoQ
When you are committed, resistance is futile. Eventually, any business will have to upgrade to the latest and greatest version of the important software it uses. There is just too much temptation when reading about the many new features and performance improvements highlighted by the software manufacturers in their marketing of the new product. And so it came to pass that in June 2014, we at STP embarked on upgrading our memoQ server installation from the old version 6.2 to memoQ 2014 shortly after it was released. We made this decision despite a couple of challenging months in the summer of 2012 after our upgrade to memoQ server 6 when that was brand new. It’s worth noting that STP skipped memoQ 2013 and 2013 R2 altogether, having weighed the pros and cons we experienced when upgrading to version 6, and despite 2013 having many new features in which we had a great interest.
Early adopters of technology get the best of the new features and can capitalise on them sooner than the competition. But early adopters also bear the brunt of finishing the beta testing that the software manufacturer couldn’t complete in time for their announced release date. In our opinion, memoQ 2014 was not quite as ready for release as Kilgray had told us, since the beta testing could have been more comprehensive and not all new features worked properly. Furthermore, a good number of existing features that had worked flawlessly in the past were suddenly broken, and there were also performance elements that had worsened compared to the previous versions.
STP’s preparation for the migration was comprehensive and detailed. We had just a smidgeon under 10,000 projects on our memoQ 6.2 server, around 8,200 TMs and just under 1,000 termbases. Most of this data was archived, but a good amount of it also needed to be moved to the new installation. The actual software upgrading (installation and configuration) went fairly smoothly, but once we started using the 2014 server and client application, we ran into a wide range of problems, some of them affecting us both internally and in our collaboration with external suppliers. STP has a strong relationship with Kilgray and we feel assured that during these demanding months, the support and service we received from them was as prompt as it would have been for any important client of theirs. And yet, it was a challenge. Now that most of the problems have been ironed out and there are no longer any showstoppers in the process, we are back in a place where we once again appreciate what a great tool we have – so comprehensively – deployed.
It is always easier to manage change when it occurs in small, incremental steps. The alterations do not become overwhelming and the benefits are immediately obvious to the users. Bigger manoeuvres like this call for trust, expectation management, transparent cooperation and vigilant communications so that all the stakeholders are able keep their sights fixed on the envisaged end result throughout the project.