Enterprise Implementation
Enterprise Software Transformation Across 225+ Locations
Why a successful rollout depended less on the software itself than on requirements, communication, training, and operator adoption.
- franchise locations
- 225+
The problem
A distributed franchise organization needed to move to a company-wide operating platform.
Unlike a centralized software rollout, hundreds of independently operated locations had different workflows, different levels of technical comfort, different operating habits, different priorities, and different levels of trust in the change.
A technically functional platform could still fail if the people using it did not understand why the change mattered or how it fit into their daily work.
My role
As IT Project & Implementation Manager, I owned end-to-end delivery across 225+ franchise locations.
Responsibilities included requirements gathering, implementation planning, cross-functional coordination, vendor management, product / development partnership, rollout planning, risk and issue management, training, adoption, and reporting and executive visibility.
How I approached it
Requirements before configuration
I worked to separate what users asked for, what problem they were actually trying to solve, what the platform could support, and where process change was better than customization.
Segment the adoption problem
Not every user needed the same support. Implementation materials and communication needed to account for technical capability, role, workflow, urgency, and resistance to change.
Create visibility
I built reporting and implementation frameworks so leadership and delivery teams could see rollout progress, risks, blockers, adoption, and where additional support was required.
The system / workflow
Outcome
The transformation was deployed across 225+ franchise locations, creating a common operating platform and a more scalable implementation framework for a distributed network.
What I learned
A software implementation is not complete when the technology is live. It is complete when the new behavior becomes normal. This experience strongly shaped how I later approached AI deployment.