5 Reasons Your New Software Project Sucks


You’ve written a requirements document.

You’ve done your due diligence.

And now, you’ve selected a new app to run your business on.

You can almost taste success.

Salesforce, HubSpot, NetSuite, Intact, you name it.

Heck, even Quickbooks if you’re just starting out.

Now that you’ve chosen the software your company will run on.

You’ll need to implement it.

And that’s when things start going south.

Here are the 5 reasons why your new software project is going to suck and what do about it.

Time Estimation

Expectations are everything.

Be realistic about how long the project is going to take.

It may be months.

It may be a year.

But it’s going to take some time if you want to do things right.

Heck, you may not want to estimate at all.

Using a process methodology like Agile could help you complete your project in nice bite-sized chunks.

Whatever you do.

Don’t pick a go-live date too soon.


Lack of focus can kill a new software project like nobody’s business.

Pick someone in your organization or hire someone to run your project for you.

Don’t use the vendor.

You need to own the software project.

Whether it’s insourced or outsourced.

Put someone qualified and experienced with software project management skills at the helm.

Not Keeping Everyone In The Loop

Communication is critical in any business endeavor.

New software implementation is no different.

Regular status updates that provide key information help to keep everyone in the loop.

Assigning tasks and making sure people are completing tasks is also important to close the loop.

Loose ends can derail a software project quickly.

Scope Creep

Do I really need to even mention scope creep?

Yes, I do.

If you did your due diligence correctly upfront there should be little to no scope creep.

Scope shrink is your friend.

Keep things simple.

Your process, your needs, and your scope.

It makes for a better implementation.


The best way to handle training is by documenting your business process.

Training your staff on a process will help you implement software faster.

That’s because if your staff already knows the process…

The tool or app is then only a vehicle to complete the process.

Before starting any software project make sure you’ve documented all of your relevant processes.

Well, there you have it.

The 5 reasons and hopefully some tips that will help your next software project to not suck.

Happy implementing.