.avif)
If your implementation team can't prove its impact on customer outcomes, it risks being treated like a cost center.
Not a growth engine.
Not a strategic function.
Just another delivery team.
That's the challenge Kevin Stanley, Global Director of Implementation at MaintainX, posed to implementation leaders at Propel 26.
For years, implementation teams have measured success through operational metrics:
- Projects completed
- Go-lives achieved
- Budgets maintained
- Timelines met
Those metrics still matter. But they're no longer enough.
Because customers don't buy software to complete implementations.
They buy software to change how their business operates.
And increasingly, leadership teams want proof that transformation actually happened.
Why Project Completion Metrics Don't Prove Implementation Value
Most implementation organizations are exceptionally good at measuring delivery.
- Time-to-value.
- Implementation duration.
- Project profitability.
- Utilization.
- Resource efficiency.
These metrics help leaders run their organizations effectively.
But they only tell part of the story.
A project can launch on time and still fail to create lasting value.
A customer can complete every milestone and still struggle with adoption.
An implementation can finish within budget and still fail to deliver the business outcomes that justified the purchase.
This is the challenge Kevin highlighted throughout the session.
Implementation teams often measure activity.
Customers measure impact.
Those aren't always the same thing.
The implementation leaders who are having the greatest influence within their organizations are learning how to connect the two.
They're proving not just that work was completed.
But that it mattered.
Understanding the Delivery-to-Transformation Shift
One of the most important ideas from the session was a simple reframe.
For years, implementation leaders have asked: Did we deliver?
Today, the more important question is: Did we drive transformation?
That's what we can call the Delivery-to-Transformation Shift.
It's the evolution from measuring project success to measuring customer success.
Delivery still matters. Predictable execution is the foundation of customer outcomes.
Projects need to stay on plan. Budgets need to remain healthy. Customers need to reach go-live successfully.
But implementation doesn't end there.
The most valuable teams continue to think about adoption, workflow changes, and customer impact long after the project plan is complete.
Because transformation isn't created by milestones.
It's created by behavior change.
Why Adoption Is an Implementation Metric?
Traditionally, adoption has been viewed as a Customer Success responsibility.
Kevin challenged that assumption.
Implementation is where customers learn how to use the product.
It's where habits are formed. It's where workflows are introduced.
And it's where expectations about value are established.
That means implementation teams have tremendous influence over whether customers become successful long-term users.
The strongest organizations don't treat adoption as something that begins after go-live.
- They build adoption into implementation itself.
- They establish success criteria early.
- They identify key workflows.
- They track engagement.
And they create momentum before Customer Success takes over.
This creates a much stronger foundation for retention, expansion, and long-term customer health.
Because adoption isn't a post-implementation activity.
It's an implementation outcome.
How Implementation Teams Become Transformation Advisors
AI was another major theme throughout the session.
But Kevin's perspective wasn't focused on replacing implementation teams.
It was focused on elevating them.
As administrative work becomes easier to automate, implementation professionals gain more time for higher-value activities.
That includes:
- Business process discovery
- Outcome planning
- Change management
- Adoption strategy
- Executive alignment
The future implementation leader won't simply understand how software works.
They'll understand how customers work.
And they'll help customers rethink processes, behaviors, and operating models to achieve better outcomes.
That's a different role than traditional implementation.
It's closer to transformation consulting.
And it's becoming increasingly important as customers demand measurable value from every technology investment.
Why Customer and Product Teams Need Implementation Insights
Kevin also emphasized the importance of stronger connections between implementation and product organizations.
Implementation teams sit in a unique position.
They see:
- Customer challenges
- Adoption barriers
- Workflow friction
- Feature requests
- Process gaps
Every implementation generates valuable insight.
But many organizations fail to capture it.
When implementation teams create stronger feedback loops with product teams, those insights become opportunities.
- Opportunities to improve the product.
- Opportunities to improve onboarding.
- Opportunities to improve customer outcomes.
- Implementation isn't just a delivery function.
It's one of the richest sources of customer intelligence in the business.
4 Key Takeaways from the Delivery-to-Transformation Shift
Kevin Stanley's session challenged implementation leaders to rethink how they define success.
Here are four lessons from his approach:
1. Project completion doesn't prove value.
Customers judge success based on outcomes, not milestones.
2. Adoption starts during implementation.
The habits customers build during onboarding directly influence long-term success.
3. AI creates space for higher-value work.
As routine tasks become automated, implementation teams can focus on strategy and transformation.
4. Implementation is becoming a strategic growth function.
The teams that influence adoption and customer outcomes will have a greater impact on retention and expansion.
Conclusion
The role of implementation is changing.
Customers still expect projects to be delivered on time and within budget. That operational excellence remains essential.
But implementation leaders are increasingly being asked to prove something bigger.
Did the customer adopt?
Did workflows improve?
Did the business achieve the outcomes it expected?
Those questions represent a shift from delivery to transformation.
And they may become the most important questions implementation teams answer over the next decade.
The organizations that succeed won't simply be the ones that launch customers faster.
They'll be the ones that create measurable change—and can prove it.
That's how implementation evolves from a delivery function into a growth engine.
.webp)