Why Smaller Tech Implementations Stall Inside The Client (And One Role to Fix It)
Smaller tech implementations often stall because of stakeholders inside the client. A Delivery Manager combines engagement management and change management in one role, so adoption gets owned without a full-time hire.
When FoxMeyer Drugs decided to invest in new technology in 1993, it did what ambitious companies are supposed to do: the distributor bought an SAP system and a warehouse automation system to increase efficiency.
What FoxMeyer didn’t plan for was the people on the warehouse floor. The employees whose jobs were affected didn’t support the project, and at the first automated warehouse, workers damaged inventory and orders went unfilled. FoxMeyer was bankrupt by 1996. Post-mortems point to an aggressive timeline, a system that underperformed, and employees who never bought in.
Technology rarely fails in the server room. It fails when a sponsor mistakes silence for support, or when the people whose work is about to change are the last to hear about it.
This pattern isn’t limited to big programs; it shows up on small ones too, where there’s even less room for error. That’s why, when an engagement calls for it, Studio Change combines Engagement Management and Organizational Change Management into a single role called the Delivery Manager, so smaller implementations get the adoption support they need (without the cost of a full-time hire).
Here’s what that means and why it works.
What Is A Combined Engagement and Change Management Role (the Delivery Manager)?
At Studio Change, a Delivery Manager is one person who owns both delivering an implementation and making sure the people affected by it are ready to use it: scope, timeline, budget, and risk alongside stakeholder alignment, communications, and adoption. We call it delivery because, for us, delivery includes adoption.
Traditionally, those are two jobs held by two people. On a smaller engagement, the second one rarely gets funded and is often the first to be cut.
When one person plays both roles, it means:
One plan. Delivery milestones and change activities live on the same timeline, so training and communications are sequenced around the real go-live, not a guess.
One point of contact. The sponsor and client team talk to a single person about progress, risks, and people concerns.
One status conversation. Adoption risks show up next to schedule and budget risks, where decisions actually get made.
The result is fewer handoffs, less duplication, and fewer surprises. The person who knows the plan best is also the person working the room.
Why Does One Role Work Better On Smaller Engagements?
BCG's 2020 research found that only 30% of digital transformations met or exceeded their target value and created sustainable change. A McKinsey report found that among companies that failed to engage line managers and frontline employees, only 3% reported success. Both findings point to the same thing: outcomes depend on people, and someone has to be responsible for them.
On a smaller engagement, a combined role is how that responsibility gets assigned. Here’s why it works:
Proximity To The Sponsor - in our experience, the person running the engagement is usually closest to the sponsor and the internal team. They know the scope, the tradeoffs, and the politics, so they can have the honest conversations that move a sponsor. Give that same person responsibility for the change, and that influence gets pointed at adoption, not just the schedule.
Messaging That Builds The Sponsor’s Credibility - sponsors often live with a change for months before anyone else hears about it, so it feels settled to them and sudden to everyone else. We close that gap early by sharpening the sponsor’s message and preparing them for executive conversations before the wider team is involved, so they walk in prepared and credible.
Change Work That Can’t Be Cut - budgets tighten, and a standalone change line item can look like an easy trim. when adoption stalls, it’s the product that looks like it failed, not the budget cut.
Here’s what that looks like on a real engagement.
Case Study: Vendor Management Software For A Small Oil And Gas Company
A technology provider was implementing a vendor management solution for an oil and gas company of about 100 employees. The change affected roughly 20% of the company, and the six-month project depended on cross-functional data cleanup. The tech provider knew from previous implementations it had managed that it didn’t have the skills to engage leadership inside its client’s organization, so it brought Studio Change in as its implementation partner.
Placing a single Delivery Manager made sense for two reasons. The engagement was too small for two part-time roles, and internal stakeholder management was the biggest threat to success. That made it an engagement problem and a change problem at the same time.
Before the official kickoff, we used our standard onboarding and key messages definition to build a walking deck with the sponsor. We refined the message together and prepared them for executive presentations, so they could start socializing the change with leadership before the wider team was involved. The same person produced the plans and the communications, so the message always matched the timeline.
There were no direct-report relationships among the internal client team, so buy-in had to come through peers. The sponsor told us they appreciated the support and the buy-in we helped build.
How Do You Know If A Delivery Manager Role Is Right For Your Next Engagement?
A combined role isn’t the answer for every implementation. It tends to work best when:
The scope is small to mid-sized. There isn’t enough work to keep two people busy, but there’s enough change to need real attention.
The biggest risk is internal. Success depends more on stakeholders inside the client organization than on technical complexity.
Sponsorship is unclear or still forming. Someone has to help the sponsor find their footing, or help identify who should carry the change.
There’s no change bench to draw on. Adding a separate change lead would be out of proportion to the engagement, or isn’t an option.
It’s a poorer fit when a program spans multiple business units, touches a large share of the organization, or needs sustained change activity across many workstreams at once. At that scale, dedicated change capacity is worth the investment.
Delivery And Adoption Are The Same Job
A system isn’t delivered when it goes live. It’s delivered when people use it.
For boutique firms with strong technology teams and a thin change bench, Studio Change can meet you where you are.
Some firms want a partner to carry the whole load. In our full methodology and implementation model, we embed in your engagement and drive delivery and adoption together. Others would rather build the capability themselves, and our advisory work helps you bring this approach into your own engagements. And when what you need is an extra set of experienced hands, our staff augmentation places a practitioner directly on your team.
Whichever approach fits, the goal is the same: a sponsor who feels prepared, a team that feels heard, and a go-live that people actually use. If you have an engagement coming up where the people side worries you, we’d welcome a conversation.
More from Change in Practice:
