When a company decides it needs a new system, the conversation usually starts with the software.
What does it cost? What features does it have? Which vendor is better?
Those questions matter, but I think there is a more important question to ask first:
What are we actually trying to change?
A company might say it needs a new system because reporting is difficult. But the real problem could be inconsistent processes, poor data, departments working differently, or simply that the company has outgrown the way it used to operate.
New software by itself will not fix those problems.
Start With the Problem
Before looking at products, understand why change is needed.
What isn't working today?
What is making people's jobs difficult?
What information is missing?
What would a better process look like?
This sounds simple, but it can completely change the software selection process.
Instead of looking for the system with the longest list of features, you're looking for the system that best supports what the organization actually needs.
Talk to the People Doing the Work
A company-wide system affects a lot of people.
Accounting may use it one way. Operations may use it another way. Managers may depend on it for reports, while employees may use it every day to complete their work.
That means these people should be involved early.
IT can understand the technology, but we don't always see every problem employees deal with in their daily work.
The people closest to a process often know exactly where the problems are.
Understand Before You Fix
In IT, when someone says something isn't working, we normally don't replace everything immediately.
We troubleshoot first.
Organizational change should work the same way.
If reporting is bad, find out why.
If employees are using spreadsheets instead of the current system, find out why.
If two departments handle the same process differently, understand why before forcing everyone into a new system.
Diagnose the problem before prescribing the solution.
Implementation Is More Than Installation
Once a system is selected, another challenge begins.
People have to change how they work.
Some processes may disappear. Others may change completely. Employees may have new responsibilities or need training. There may also be resistance, especially when people have been doing something the same way for years.
This is why organization-wide software should be treated as planned change, not simply a technology installation.
Communication, training, employee involvement, and leadership support can be just as important as the software itself.
Going Live Doesn't Mean You're Done
Getting the new system running is an important milestone, but it doesn't automatically mean the change was successful.
Go back to the original reason for making the change.
Did reporting improve?
Are employees spending less time on manual work?
Is the information more reliable?
Are departments working together better?
Did the new system actually solve the problem?
If not, learn from what happened and make adjustments.
People, Process, and Technology
The more I work with business technology, the more I believe successful change comes down to three things:
People. Process. Technology.
Technology is only one part.
You can buy great software and still have a poor outcome if the organization doesn't understand the problem, involve the right people, or prepare employees for the change.
So before asking:
"Which software should we buy?"
Start by asking:
"What are we trying to improve?"
That one question can lead to a very different—and much better—conversation.