A program goes live. The system works. Yet teams quietly continue using spreadsheets and following the old ways of working. This happens in more IT implementations than we like to admit.
IT implementations are rarely just system deployments. They reshape how people work, make decisions, and collaborate across the organization. Processes change. Responsibilities shift. Sometimes entirely new capabilities and teams emerge. When adoption is treated as a separate workstream, these human and organizational realities are addressed too late. At OXYGY, we approach implementations differently. Every phase of delivery becomes an opportunity to prepare people, build ownership, and strengthen adoption. The goal is straightforward: help individuals become confident, competent, and committed in the new environment. Transformation happens person by person. One size does not fit all. One size fits one. Every interaction with people during the program becomes an opportunity to build adoption and shape how they experience the change.
1. Planning & Discovery: When the future becomes visible
Planning and discovery set the direction of the transformation. Leaders align on scope, timeline, and architecture. Still, many programs treat discovery as a technical preparation phase. Attention stays on system capabilities instead of the people who will operate them. When the human impact is overlooked, leaders underestimate how daily work will change. Later, teams experience the transformation as something imposed on them rather than something they understand.
➡️ Discovery should guide leaders and teams through what the future design means in practice. Which decisions move from local to global? Which roles gain responsibility and which ones lose it? What will look different in daily operations on the first Monday after go-live? When leaders speak openly about these shifts, people gain direction. They understand why the transformation matters and what it means for them in their own work.
2. Fit-Gap & Local Discovery: Global design begins to turn into local ownership.
Fit-gap analysis connects the global template with the reality of local operations. It helps teams understand how the future processes will work across markets, functions, and roles. Many implementations approach fit-gap as a top-down exercise. The global design is presented and local teams are asked to comply. Resistance often follows. Teams feel their expertise is overlooked, and discussions drift into negotiations about exceptions.
➡️ Organizations need to move beyond simple top-down rollouts. Local teams should be guided through a structured discovery process. They examine how the global process works, identify where it affects their operations, and recognize the adjustments required in their own environment. When teams reach these insights themselves, ownership grows. The transformation becomes something they understand and can stand behind.
3. Functional & Process Design: When people start shaping the way they will work
Process design translates strategy into the way work will actually happen. It defines how teams interact, how decisions are made, and how responsibilities move across the organization. Too often design becomes a documentation exercise. Experts produce detailed specifications and assume the organization will follow them later. When leaders and teams are not involved, the design remains abstract. Employees see the process as someone else’s idea rather than their own future way of working.
➡️ Design sessions should actively involve the people who will run the future process. When functional leaders and subject matter experts shape the solution themselves, their perspective shifts. They prepare their teams earlier. They answer questions with confidence. They reinforce the design decisions consistently. Ownership built during design often turns into commitment during implementation.
4. Data Migration & Governance: Trust in the system begins with trust in the data
Reliable data is the foundation of daily operations in any system. Yet data migration is often treated as a technical activity handled by specialists. When ownership and governance are unclear, problems surface after go live. Teams lose confidence in the system. Parallel spreadsheets appear. Local corrections become common.
➡️ Data needs to be treated as a leadership responsibility. Clear ownership for each data domain must be defined, and accountability for quality made visible. When people trust the information in the system, they rely on it to make decisions. Trust builds confidence. Confidence strengthens adoption.
5. Testing: The future way of working is experienced for the first time
Testing confirms that the system and processes function as intended. Just as importantly, it allows the organization to experience the future way of working before the system goes live.
Testing often begins with scripts and technical validation. Users evaluate the system through the lens of current practices instead of the future design. Confusion follows because the system is judged against processes that are meant to change.
➡️ People need to be prepared before testing begins. Users should understand the future process and the logic behind it so they can assess the solution in the right context. Testing should become a rehearsal of future work. Teams run realistic scenarios, interact with other functions, and experience the new flow of decisions. Through repetition they become familiar with the future system and more confident in how it supports their roles.
6. Training: Where knowledge turns into real capability
Generic training programs often focus on system features rather than real tasks. Participants leave with theoretical knowledge but little confidence in applying the new processes under real operational pressure.
➡️ Training should reflect the reality of each role. A planner needs to practice planning cycles. A country manager needs clarity on decision rights and performance indicators. A finance controller must rehearse the closing process. When people practice the activities that define their job, they become competent and confident in the new system.
7. Hypercare: The new way of working becomes the new business-as-usual.
Hypercare ensures that teams continue using the system as intended while operational pressures return.
Without active reinforcement, familiar habits reappear. Spreadsheets return. Workarounds spread. The intended processes slowly weaken.
➡️ Hypercare should focus on reinforcing the new way of working. Leaders track where deviations appear and address them quickly with their teams. Progress becomes visible as people gain confidence and teams rely more consistently on the system. Over time the organization stabilizes and the new processes become part of daily work.
Conclusion
When IT implementations are approached through a change leadership lens, every phase of delivery becomes an opportunity to prepare the organization. Discovery builds understanding of the transformation. Local exploration creates ownership. Design establishes commitment. Data governance builds trust. Testing rehearses the future. Training develops capability. Hypercare stabilizes new behaviors.
The program still delivers technology, but the real outcome is different. People across the organization become confident in the system, competent in their roles, and committed to the new way of working.
That is how adoption grows.
Not through a separate workstream, but through every interaction with people throughout the implementation. The system may go live on a specific date. Real transformation has happened if people start working differently the next morning.
About the Author
Arne Buthmann is Co-Founder and Board Member at OXYGY and Practice Lead for IT-enabled Transformations.
