(And what you can do to make sure yours is a success!)
Over the last few years I’ve managed some pretty large MIS implementation projects for Tharstern and along the way I’ve gained some really valuable insight into what determines how successful a project will be.
I found out pretty early on that two seemingly identical projects can have very different results, both in terms of how well the MIS is received by its new users and also how smoothly the implementation process goes.
In this article, I’m going to share the 7 key factors that I’ve found to have the most influence on this, and suggest some things that you can do to make sure your project is a roaring success!
1. How open, honest and inclusive you are
The most successful projects I’ve been involved with all have one common denominator: inclusivity. Any implementation where the Project Team has kept End Users at arms-length from the new system until the 11th hour, will always encounter resistance. A cloud of animosity will sit over the whole project throughout the go-live period and into the ensuing months.
When Project Teams work in an open, collaborative and honest manner, End Users are more supportive and enthusiastic. They will openly offer constructive criticism and assistance when encountering any barriers to flow.
DO engage all End Users early on in the project lifecycle – this is their working environment you’re affecting.
DON’T give them a 10-minute demonstration in week 1 and never communicate again until go live week.
2. How considerate and respectful to the End User you are
Implementing a new management information system is disruptive to every employee’s working life. Project teams that consider and empathize with End Users concerns achieve greater success rates than a dictatorial approach.
So be prepared to help - your knowledge is to be shared, not hoarded. A new MIS will grow others professionally and personally.
DO empower – seek it, give it.
DON’T say “because I said so”.
3. How much of a team effort it is
Many times I see companies appoint just one person to project manage, configure the system, train End Users and deliver all integrations associated with a new system. On these implementations, I worry. Because that one person with the keys to the Kingdom bestowed upon them becomes the single point of failure. But in this person’s eyes, their heroics are elevating them to a point where knowledge is King and where individual Herculean endeavours will deliver personal and professional success – always to the detriment of the business and sometimes to the detriment of themselves.
When mild mannered Clark Kent turns into Superman, knowledge is his strength and pride is his Kryptonite.
DO appoint a project team - one person cannot know every aspect of a business.
DON’T subscribe to the “that’ll teach ‘em” attitude.
4. How mistakes and feedback are handled
Mistakes are going to be made - we are human. Blame and conflict are not conducive to a productive work environment. If something is criticized for its configuration or a document is berated for its design, you need to analyze the feedback and (if it’s justified) accept it, correct it and move on.
DO listen and hear, every voice is important so be open minded and objective about the facts.
DON’T make assumptions on working history or personal relationships.
5. How solution oriented you are
Often when project members come across a stumbling block in their project, I will hear common terms like ‘bugs’, ‘issues’, ‘user errors’, ‘roadblocks’, ‘punch list’ and ‘snagging list’. I’m not a huge fan of any of these terms because they all carry an implication of negativity.
I prefer to use the idiom ‘barriers to flow’ which I picked up from a very successful implementation recently. Whilst identifying that there is a barrier that needs addressing, it also expresses a positivity that the system will flow. There is no ‘block’ or ‘issue’, just a temporary barrier. Positive flow is the objective of all MIS implementations and ‘barriers to flow’ acknowledges the project goal and ties in with the defined aims and return on investment identified during the scoping phase.
This model project I refer to was headed up by the business owner. He was bold enough to subject his ideas to review by his staff. His ideas were challenged – sometimes in heated situations – but with an open attitude where the result was a clearly written set of aims. Financial, work efficiency and cultural targets were listed along with a process to measure every item and a regular forum where methods to improve were discussed and actioned. They went live 2 months ahead of schedule, with a return on investment surpassing their original aims.
DO Write down your aims, how you are going to measure and how you are going to improve.
DON’T believe the outcome is out of your teams’ hands.
6. How committed to the outcome everyone is
‘Take ownership’ – it’s a short phrase for such a large commitment but it’s at the core of all successful implementations. Those projects where the team is prepared to be accountable for errors as well as successes achieve more than those who hide and skive. Obviously, you need a blame-free culture for this to thrive but where a team believes in the outcome, their commitment will ensure success.
DO put the effort in: You get out what you put in.
DON’T be afraid to be accountable. A man who never made a mistake never made anything.
7. How enjoyable it is
I know implementing a new MIS is hard work and it can feel like a marathon struggle sometimes, but projects I have seen where key milestones are celebrated – whether that’s over a beer or meal – keeps the team motivated and productive.
DO reward and celebrate efforts.
DON’T over-reward – a hangover isn’t that productive!
In a nutshell
You may have noticed that much of the above actually boils down to 2 key things:
You have to have A Positive Mental Attitude.
You have to be considerate to your colleagues.
Without exception I have found that project teams who share these characteristics are highly successful – the MIS is well received and the transition to the new system runs smoothly.
A final bit of advice…
If you’re about to embark on your own implementation project, why not take these 7 characteristics and turn them into something that your team can use to guide them through the project. Perhaps a Project Charter or Mission Statement or something similar that you can come back to from time to time. It will serve as guidance during the planning process and remind you of what’s important throughout your project.
Automated workflows don't work for print!
What?!? Yes they do! But all the hard work you've put into creating an automated workflow is being undone. Find out where, why and how you can fix this.