Ensuring your project success

Introduction

After 25+ years of analysing, scoping and implementing software projects, I’ve realised a critical key to project success lies with the engagement of you- the end user and client.

Over time, it’s become clear that the most successful projects have the highest level of client engagement, and the projects where we’re struggled to get the project over the line, or to fully realise the expected benefits have had a lower level of ownership taken by the end users.

Don’t get me wrong, selecting the right vendor/product is still incredibly important, but you have more control over the success of your next project than you might think - and you dont need to be a software developer or a project manager to make this happen.

Read on for practical tips and tricks to ensure a winning implementation.

 

Requirements gathering

No one would think of building a house without at least a rudimentary plan - nor would you interview someone without a clear job description.

Only you know what you want.

Now, what I often hear when talking about this subject is...

“but I don’t know what I dont know”

...meaning they don’t know what feature a new system is going to offer them.

The good news is - you dont need to!

Your requirement might be “I want to integrate new Leads from my website, email and Facebook’.

That’s a nice solid requirement. At this stage, you don’t need to know HOW your vendor is going to do this, only that you need it done.

This is also one method you can use to measure your vendors. Have they just given you a price for this requirement?

Have they talked to you about the different options? Have they made any clever suggestions about a slick way to handle your requirement?

A good set of business requirements covers three aspects:

  • Functional requirements - ie: what the system needs to do.

  • Non-functional requirements - covers items like the applications security settings, uptime requirements,how you’d like to handle training etc.

  • Vendor requirements - do you need onsite support, or access to a 24x7 helpdesk? How does the Vendor’s culture align with your own?

Non-functional and Vendor requirements are equally as important to the success of your project as what the system is actually going to do for you.

If you’re hesitant about this process, consider engaging a Business Analyst to help. You can also find templates online, including my own, specifically for CRM, Sales and Marketing tools.

Here are some examples of how good vs bad business requirements have played out for me in real life.

“Thats not what I wanted!”

A major transport operator here in NZ had an ERP system implemented by the company I worked for. They requested some enhancements, so I drafted up a document that included their requirements and how I planned to solve them. I included screen shots, a written description of the new process, and a process flow diagram. This was duly signed off, implemented and tested.

When I handed the system over to the client for User Acceptance Testing, my contact there literally said “but that’s not what I wanted”. It was however, exactly what I had specified. He confessed to not reading the document because he was too busy.

“Well, thats not going to work!”

(a.k.a. my worst implementation ever)

A manufacturing client needed a new ERP system. I was assigned to a Consultant that worked for them to develop the requirements which included some very costly customisations. The Statement of Work was duly delivered and signed off and we implemented the system.

On the first day of training I sat down with the warehouse team and introduced myself as I hadn’t met any of them before. I outlined an overview of the system, and started to get down into the detail. I hadn’t been talking for more than 5 minutes when the Production Manager stood up and said “Well, thats not going to work”.

While the Consultant responsible for developing the requirements with me had loads of experience in the business, it was all at a high level, and he had no clue as to how things operated on the factory floor

Best project ever

On the flip side, the best project I ever ran had a project champion who was 100% percent involved in all aspects of the project. She involved her team members, and took responsibility for all internal actions like data cleansing and communicating to the wider team.

She turned up to all the meetings, and asked a lot of questions.

The project came in on time and under budget - and was considered so successfully implemented that I received an award from the Vendor of the software I implemented.

The case study was used around New Zealand and Australia as an example of how a truly slick project implementation looks.

All three of these projects occurred within two years of each other. In each case I delivered excellent requirements documentation, and a high quality product - the biggest difference between the projects that went well and the ones that did not was the level of engagement from the client

Vendor Selection

Once you have a documented set of requirements, you can use these to measure and compare different products or vendors against each other.

Simply add a column to the right for each vendor or product, and rate them out of 10 on their ability to deliver on this requirement.

A proactive vendor will make suggestions and will let you know how your requirements have played out in other, similar businesses.

Where possible, consider having more than one person in your organisation participate in this exercise, this helps to smooth out any innate biases.

The end result allows you to make a data based decision, rather than an emotion based decision.

Project Structure

Key Components of a Project Team

Any sizeable project should have someone to fill these roles:

  • Project Sponsor - normally the business owner/CEO. This role is responsible for signing off on the requirements, the budget and authorising any additional expenditure if required.

  • Project Manager - The Vendor should provide a project manager to ensure that tasks are completed in a timely fashion, the schedule is adhered to, and the deliverables are being met. You, the client should also have a project manager. This person is responsible for project tasks such as:

  • Communicating to the wider business

  • Co ordinating the internal project team’s activities

  • Mediating/resolving resource conflicts

  • Managing and resolving requirement conflicts

  • Removing blockages preventing the internal project team from meeting project deadlines.

  • Ensuring users are available for scheduled training

  • Subject Matter Experts (SME’s) - there should be a representative of each affected department on the project team. They bring their in-depth knowledge of how their department operates. They should raise any concerns they have about the project to the project manager for resolution. They should also be keeping an eye on how the project will impact the other systems or manual processes in their department.

SME’s will also be heavily involved in testing the system before it gets released to the wider business.

Testing

Your software provider should absolutely be testing all the processes, integrations and workflows they’ve set up for you.

BUT

You know your business better than they do.

I’ve come across the following scenario several times when implementing a project.

The client will say “we need the system to x, y and z”, and I say - “of course, no problem”.

I then test the requirement thoroughly and pass it to the client for their review. And, there is a problem. Not with ‘what’ the process is designed to do, but rather HOW we’ve designed it to work.

There’s also an old adage that a software developer should never test their own work, and the same applies to implementation consultants too.

Unless we’ve been told otherwise, we’ll test it the way we’ve designed the process to work, which may not be the same way your team will ultimately use it.

Even something as small as using the Enter key instead of clicking with a mouse can have an impact of how the system interprets your commands.

We recommend that you collaborate with your vendor on designing the test plans to eliminate risk, process uncertainty, and therefore rework and cost.

A well document set of test plans serve two other purposes as well.

They can be used as a resource to check for downstream implications   (if you’re considering making a change after implementation), and they’re very handy if a software upgrade is required.

A well defined test plan should include:

  • The requirement/process being tested

  • How this should be tested

  • Other systems or manual processes it touches on

  • Expected outcomes.

Training - the unsung hero

A well-structured training program ensures employees feel confident using the new system. This includes hands-on training, ongoing support (e.g., help desks, super-users, or knowledge bases), and reinforcement to prevent frustration or skill gaps.

The level of training provided can be the difference in the project succeeding with the wider business, or not.

I once had a friend come to me, nearly in tears. They worked as a salesperson for a large, multi million dollar company who had just replaced their CRM system and quoting tool.

The sales team were given 1 hours training on the new system.

One lousy hour for the people responsible for generating revenue for this substantial corporation.

It’s almost like the company did not want the sales team to succeed.

Make sure the training plan is tailored to your team, your business, and your requirements.

Here are some tips to increase your success at this critical project stage:

  • Use your SME’s as a resource to assist other team members. If they’ve been involved in the system design and testing, they know enough to be able to help others with minor questions.

  • Schedule the training for as close to Go Live as practical so that the teams retains as much knowledge as possible.

  • Consider printing and laminating Quick Guides to keep at their desk to remind them of the key steps.

  • Remember that people will stop learning after two hours in a training session.

  • Consider ongoing training to ensure  there’s no degradation of the knowledge learned.

  • Can you create training videos so that new staff have access to great training too?

Managing the Human Element in a time of change

A beautiful, well designed software project can still fail spectacularly if the user/staff needs aren’t understood and met. Here are some ways to increase the system uptake, and manage the stressors of going live with a new system.

Employee Buy-In & Communication

Clear, transparent communication is essential to reduce resistance and build enthusiasm. Employees need to understand the ‘why’ behind the change, how it benefits them, and what support they will receive. Engaging employees early, addressing concerns, and involving key stakeholders can dramatically improve adoption.

Change Readiness & Culture Fit

Assessing the organisation’s change readiness helps identify potential roadblocks. Leadership must champion the change, and understand that fear of change is one of the leading causes for slow/lack of adoption.

Understand the Root Causes of Fear

1.  Employees often resist change because of:

  • Fear of the unknown – They may not understand why the change is happening or how it will impact them.

  • Job security concerns – Some may worry that automation will replace their roles.

  • Lack of confidence – They might feel they don’t have the skills to adapt to the new system.

  • Comfort with the status quo – People tend to prefer familiar processes, even if they are inefficient.

 

2. Proactively address concerns

  • Communicate early and often – Use clear messaging to explain the why behind the software change. Be transparent about benefits and challenges.

  • Acknowledge fears – Create open forums (Q&A sessions, anonymous surveys) where employees can voice their concerns without judgment.

  • Highlight personal benefits – Show how the system makes their work easier, increases efficiency, or provides new opportunities for growth.

3.    Involve Employees in the Process

  • Identify change champions – Engage influential employees early to act as advocates.

  • Encourage participation – Let employees provide input on implementation, training, or customization to improve buy-in.

  • Use pilot programs – Rolling out the system in phases helps people adjust gradually and provides opportunities for feedback.

 

4.    Lead with Empathy & Culture Alignment

  • Encourage leadership involvement – When managers use and promote the system, employees are more likely to follow.

  • Align the change with company values – If collaboration and innovation are key values, show how the new system supports them.

  • Be patient and flexible – Change takes time. Acknowledge frustrations and adapt support strategies as needed.

So, in a nutshell:

  • Select some system champions early in the process. Not only do they have valuable insight into how things are done now, they will become your first line of support.

  • Communicate, communicate, communicate. You already know which of the people in your business are going to struggle with change. Sit down and have a chat.

  • Ensure you have an ONGOING training and support programme

  • Understand that everything will be a little bit (or a lot) slower to start with

Written by guest-blogger Megan Cunningham-Adams, Onion CRM

Next
Next

Facebook did what?