Technology gets handed to operations. Nobody checks if operations is ready for it.
Technical projects get scoped to delivery date and technical functionality. Operational readiness, whether the people and processes can absorb the change, rarely gets assessed formally. The result is technically successful implementations that become operationally disruptive ones, and an organization that learns to be skeptical of technology change rather than confident in it.
Where you sit today
What a COO sees on the floor.
Three situations a COO may recognize.
People work around the systems they are supposed to use
Adoption never fully happens. Manual workarounds emerge. The investment that justified the system never gets realized.
Technology gets handed over before operations is ready
Go-live is decided on technical criteria. Operational readiness is informal at best. The disruption that follows is a known risk.
Nobody has a complete picture of what is running
Departments bought their own tools. Some overlap. No one keeps a complete list. When something breaks, it is unclear who owns it.
What changes with Preside
Three changes to how technology reaches operations.
Readiness assessed before go-live
We recommend a written readiness assessment before any go-live. It covers process redesign, role definition, training, and supporting infrastructure, and operations owns it. The assessment records the decision either way. It does not block it.
Change management as a discipline
Adoption tracked as a measurable outcome with named ownership. Failure modes anticipated from accumulated experience. Communication architecture designed before launch.
One view of technology across departments
Inventory, ownership, and support escalation for tools that departments bought on their own. The Vendor Rationalization Initiative maps the vendor portfolio and shows where tools overlap.
A sample report
Example: an operational readiness scorecard
A readiness view for a mid-implementation CRM rollout. Each dimension is evaluated and recorded in writing before go-live becomes a decision.
Project
CRM consolidation, sales operations rollout
| Dimension | Owner | Status | Readiness note |
|---|---|---|---|
| Process redesign | RevOps | Ready | Sales motion documented end-to-end. Stage gates aligned with the new system. |
| Role definition | HR + Sales leadership | Ready | Team structure approved. Comp plan adjustments signed. |
| Training | Enablement | At risk | Curriculum complete. 38% of reps not yet certified on the new workflow. Two-week extension required. |
| Data migration | IT + Data team | Ready | Test cutover passed. Reconciliation report attached to readiness packet. |
| Support escalation | IT Service Desk | At risk | First-line support guides not yet finalized. Post-launch support staffing needs sign-off. |
| Communication | Internal Comms | Ready | Three-touch cadence ready. Executive sponsor message scheduled day-zero. |
Your recommended Initiative
Three-week Change Readiness Initiative
The deliverable
An organizational readiness assessment for an upcoming technology project, plus a change management plan with named owners, milestones, and adoption metrics.
See the Change Readiness Initiative →Our view
One common cause of disruptive rollouts is that technology reaches operations before operations is ready for it. We recommend a delivery model in which operational readiness is reviewed in writing before go-live, with the same standing as a financial or legal review on a major project.
What COOs ask first
The four questions before the engagement.
Isn't this just project management with new branding?
Project management tracks delivery to plan. Readiness assessment evaluates whether the receiving organization can absorb what is being delivered. They are different disciplines with different success criteria.
We already have a PMO. How does this fit?
The PMO keeps its role, and we work alongside it. The PMO runs the project. We produce the operational readiness assessment that the PMO's charter does not cover. The two work together: adoption risk moves off the PMO's plate and its charter stays the same.
What's the relationship to my IT team?
IT owns implementation and keeps authority over it. We produce the operational readiness assessment. When IT and operations disagree on go-live, the assessment gives operations a documented basis for the call. It makes clear who is responsible for adoption.
What if leadership wants to push go-live regardless?
The assessment does not stop leadership from going live. It records the decision. If go-live happens on a red readiness scorecard, that is on the record. The scorecard makes the decision explicit either way.
If you are a COO at a PE-backed company
Four pressures specific to the PE-portco operations seat.
If your company is PE-backed, four things change for the COO.
- Add-on integration tempo. Add-ons arrive faster than the operations integration plan. The COO carries the operational seam between the new entity and the platform.
- Adoption mechanics under PE-driven timelines. PE-backed change projects compress timelines that operations is asked to absorb. The change-readiness work has to land ahead of the rollout, not at it.
- Operating documentation for exit. Buyers’ diligence teams may ask for the documented operating model. What the COO has built during the hold is what gets handed to the buyer.
- Cost room by hold stage. Early in a hold, operations has more room to change cost than it does 12 months before exit. The work is timed to where the company sits in the hold.
Start with a readiness assessment. Three weeks, fixed scope.
A readiness assessment and a change management plan before the next go-live. If it changes how operations and IT hand off, the Technology Operating Partner Program continues the work.