ITSM, CSM, OCM
Professional Services Technology
ValueCentrix Editorial Team
2 ServiceNow modules | 4 months Kickoff to handoff | Week 5 First module live | 0 Technical escalations |
The Challenge | Changing Habits, Not Just Systems
A mid-market professional services technology company with a distributed internal team and a customer base accustomed to email-based support had outgrown its legacy helpdesk platform. It needed a modern, centralized solution to handle both external customer service and internal IT requests.
The engagement called for two ServiceNow modules - Customer Service Management and IT Service Management - to be designed, built and launched inside a single five-month window.
The technology challenge was straightforward. The human challenge was not.
Years of email-based habits meant internal users defaulted to contacting individuals directly rather than submitting through a portal. A system launch alone would not change that behaviour, and without adoption even a flawless implementation would underdeliver. The client needed both modules live on schedule, users actually using them, and no disruption to ongoing operations along the way.
What would decide the outcome was organizational change management, not configuration.
The Approach | Delivery and Adoption in Parallel
ValueCentrix structured the engagement around two disciplines running side by side: platform delivery and organizational change management, resourced and sequenced as equal tracks rather than one supporting the other.
Two tracks, one engagement
Delivery track ● CSM sequenced first to create a working proof point ● CSM live five weeks after kickoff ● ITSM launched onto a foundation of earned confidence ● Unfinalized requirements moved to a managed services backlog | OCM track ● OCM plan designed before go-live, not after ● Internal change agents equipped with specific redirect language ● Users met on the channel they already used - email ● Client team enabled to run the plan without vendor support |
On the delivery side, we sequenced the build to get CSM live first, establishing a working proof point for the organization before ITSM launched. That early win built internal confidence and gave the ITSM launch a credibility foundation it would not otherwise have had.
On the OCM side, we did not wait for go-live to start managing the change. We built a four-phase OCM plan during delivery and handed it to the client’s internal team to execute without ongoing vendor support.
The four-phase OCM plan
1 Pre-launch awareness building | 2 Change agents briefed internally | 3 Go-live announcement | 4 Reinforcement two-week check-in |
WHAT THE OCM TRACK COVERED ● Awareness raised with the user base before the build was finished ● Internal change agents identified and briefed - with the exact words to redirect a colleague who emailed instead of raising a ticket ● A launch communication sequence timed to go-live ● A two-week reinforcement check-in after each module went live ● The whole plan documented so the client team could run it, and every subsequent change, without us |
The plan was deliberately simple: meet users where they already were, equip internal change agents with specific redirect language rather than general awareness, and define success as gradual adoption rather than overnight compliance.
On scope, we stayed focused on what the client needed most. Where requirements were not finalized, or work belonged in a post-launch phase, those items were documented and moved to a managed services backlog - keeping the core engagement clean and the go-live timeline intact.
The Results | Two Modules, Both On Schedule
Kickoff to handoff ran from 26 January to 29 May 2026 - seventeen and a half weeks, inside the five-month window. The first module was live in week five, both go-lives hit their dates, and both hypercare periods closed without a single technical escalation.
Engagement timeline — to scale
Milestone | Date | Outcome |
Project kickoff | 26 Jan 2026 | — |
CSM go-live | 2 Mar 2026 | On schedule Week 5 from kickoff |
CSM hypercare | 2–13 Mar 2026 | Zero escalations Two weeks, closed cleanly |
ITSM go-live | 15 May 2026 | On schedule Per original SOW milestone |
ITSM hypercare | 15–29 May 2026 | Zero escalations Two weeks, closed cleanly |
Post-launch adoption | 30–60 days | OCM outcome Portal submissions received; email volume to internal owners decreased |
Close & handoff | 29 May 2026 | Client-run OCM plan executed independently — no ongoing vendor support |
Two modules. One engagement. No fires. |
Why It Worked | Speed Without Shortcuts
Speed without shortcuts. Sequencing CSM first gave the team a real go-live under their belt before ITSM launched. It also gave the client a working system to point to when communicating the change internally. That proof point mattered.
OCM built in, not bolted on. Most implementations treat change management as an afterthought - something to arrange once usage numbers disappoint. We designed the OCM plan before go-live, not after. And equipping internal change agents with specific language rather than general awareness is what moved behaviour at the individual user level.
The Takeaway | A System Nobody Uses Isn’t a System
If you are evaluating a ServiceNow implementation partner, the questions worth asking are not only about technical capability. They are about what happens when the system goes live and people have to change how they work. Most partners will configure the platform. Fewer will own the change.
ValueCentrix delivers on schedule. We also deliver the organizational change management that makes it stick - because a system nobody uses isn’t a system.
Planning a ServiceNow rollout that people actually have to adopt? Talk to us about OCM.