Implementation is something the buyer and provider produce together.

Purchasing software and implementation services does not transfer every condition required for implementation success to the provider. The buyer still contributes decisions, operational knowledge, information, authority, process design, testing, stakeholder participation, change readiness and governance. Implementation capability therefore depends on how buyer and provider contributions work together.

Evidence breadth

Multi-Case + Structural Synthesis

Where this applies

CMMS implementations, reimplementations, migrations, major upgrades and phased rollouts that require buyer participation in decisions, information preparation, workflow design, integration, testing, training, adoption or governance.

Last evidence review

September 22, 2026

What happened

Guelph had purchased Maximo in 2020 but later evaluated whether to replace it with a new EAM or engage a new implementation partner to more fully realize the existing platform. City budget reporting separately showed that EAM implementation was part of a multi-year enterprise program and included change-management activity intended to support organizational readiness.

Why it matters

Purchasing software and external implementation services does not eliminate the organizational work required to turn technology into operational capability. Providers can supply technology and external expertise, but implementation can still depend on decisions, information, authority, operational knowledge, stakeholder participation and change readiness that must come from—or be enabled by—the buyer.

What a buyer should do

Before committing to an implementation plan, identify what the provider must supply and what the organization itself must supply. Assign owners, capacity and decision authority to the buyer-side work, establish when each contribution will be needed, and verify that those contributions can actually be available when the implementation depends on them.

Treat implementation as a division of responsibilities rather than a handoff. Identify what the provider must contribute, what the organization must contribute, who owns each contribution, when it is required and whether the necessary capacity and authority will actually be available.

What this evidence does and does not establish

This evidence does not establish that buyer and provider responsibilities should be equal, that buyers should perform technical work assigned to qualified providers, that Guelph's earlier implementation outcomes were caused by insufficient buyer participation, or that a particular implementation approach ultimately succeeded. The required contribution from each party depends on the implementation scope, delivery model, organizational capability and assigned responsibilities.

What happened

Why it matters

What a buyer should do

What this evidence does and does not establish

Documented evidence