A few years back I got a call from a $500M retail distribution company in the middle of a NetSuite implementation that wasn’t going well.
They hadn’t gone live yet and were already losing confidence. Leadership wasn’t sure if they had picked the wrong software, chosen the wrong partner, or both. So they brought me in to find out.
I did a full analysis. Talked to stakeholders across the business. Reviewed the selection process. Looked at what the partner was doing and what the client team was doing.
Here’s what I found: NetSuite was the right call. The selection process had been solid. The tool fit where they wanted to go.
The problem was the implementation itself. The partner understood the technology but had never built trust with the organization. The right people weren’t in the room early enough. Decisions were being made around the client team instead of with them. By the time I got there, key people had already mentally checked out.
I stayed. I helped PM the rest of the implementation. Made sure the right people were at the table from the partner’s side, and that the client’s team was engaged and doing what they needed to do.
The project finished. It worked, but it almost didn’t, and the technology had nothing to do with why.
The Buy-In Gap
I have seen this pattern constantly throughout my career.
Whether it’s an ERP implementation, a new AI initiative, a major process redesign, or any other transformation effort, organizations will spend months evaluating technology and very little time thinking about how to get people to buy in.
Buy-in is not a soft skill. It is the variable that determines whether the project succeeds or fails.
I know that sounds counterintuitive when you’re deep in a technical implementation, but it’s true. The best software in the world is worthless if your team quietly decides it’s not going to work.
Most employees understand that leaders have to make difficult decisions. They understand that not every opinion can become the final direction. What creates resistance is feeling excluded.
When people are invited into the conversation early, they feel respected. When they understand how decisions are being made, they begin to develop ownership. They become invested in the outcome because they can see themselves in the process.
This holds true even when the final answer isn’t the one they initially wanted.
The Irony of Technical Projects
What I find fascinating is how the success of highly technical projects is won or lost on human and non-technical skills.
Think about a company moving from QuickBooks and spreadsheets into NetSuite. A large technical project, right? Wrong. There are integrations to build, data to migrate, workflows to redesign, and countless technical decisions, but that’s only half the problem.
The other half has nothing to do with software. It’s getting people to actually care about what you’re building. That means communication, trust, and bringing the right stakeholders in early enough that they feel ownership, not obligation. Skip that part and it doesn’t matter how good your consultants are.
You need technical expertise. Strong architects, solid implementation specialists, and people who can solve complex problems. That’s the floor, not the ceiling.
What Great Implementation Partners Actually Do
Most companies evaluate implementation partners on technical capabilities. Certifications, methodologies, years of experience, platform expertise. All important things. You absolutely want a partner who knows the technology inside and out.
But technical fit and organizational fit are two different things, and most companies only screen for one of them.
Every implementation is a long journey. You are going to spend months working together, solving problems together, and navigating difficult decisions together. Communication style matters. The way a partner handles conflict, delivers bad news, and responds when something goes sideways matters just as much as whether they can configure a workflow correctly.
Every project hits bumps, and when those moments arrive, your team is not going to lean on the partner’s certifications. They are going to lean on the relationship they built with them.
The right partner is not always the most credentialed one. It is the one your people believe in.
Technology Enables Change. People Make It Stick
I have watched businesses succeed with imperfect tools and fail with excellent ones. The tool was never the variable; the people were.
Technology creates opportunities. It can automate work, sharpen your visibility, and make the business more effective. Technology does not transform anything on its own; people do. People will not use what they do not trust.
So here is what I want you to take from this. Before you sign the next contract, before you kick off the next initiative, before you send the next project update, ask yourself one question: do the people who have to live with this change feel like they are part of it?
Not informed. Not updated. Actually part of it.
Buy-in is not a box you check after the decision is made. It is the work that starts at the beginning and runs the entire length of the project. Match your investment in the people side to your investment in the technology side. Not close to equal, actually equal.
Transformation happens when people decide to move forward together. Everything else just clears the path.
If you are in the middle of a transformation right now and something feels off, let’s talk. Sometimes it takes ten minutes with someone who has seen it before to figure out where the real problem is.