Your Systems Integrator Can't Own Your Business Readiness. Here's Why.

Organizations undertaking major ERP transformations invest substantial time and money selecting the right systems integrator (SI).

They evaluate experience, methodologies, technical capabilities, industry expertise, staffing models, references, and commercial terms. They negotiate contracts defining responsibilities, deliverables, milestones, and acceptance criteria.

Then they entrust the implementation to a firm experienced in delivering complex enterprise technology solutions.

It's a sensible approach.

But it can create a dangerous misunderstanding.

Hiring a capable systems integrator does not transfer accountability for the successful operation of your business.

Yet in many transformations, that's precisely what happens—at least implicitly.

The SI becomes responsible not only for delivering a functioning solution but, in the minds of some executives, for ensuring that the enterprise will be prepared to operate when the new system goes live.

Those are fundamentally different responsibilities.

Delivering a System Isn't the Same as Preparing a Business

Systems integrators provide expertise that most enterprises cannot economically maintain internally.

They understand the technology, its configuration, integration requirements, implementation methodologies, and many of the challenges associated with replacing complex legacy systems.

Their delivery methods typically organize implementation work around activities, deliverables, milestones, and acceptance criteria.

These disciplines are essential.

But consider two questions:

Has the implementation team completed the required testing?

Can the business accurately execute its critical transactions at expected volumes and service levels after Go-Live?

Or:

Has the training program been delivered?

Can employees independently perform their responsibilities using the new processes and systems?

The first question in each pair concerns implementation activity.

The second concerns operational capability.

Completing the first does not necessarily establish the second.

This is the distinction between project status and business readiness.

The Accountability That Cannot Be Outsourced

In more than three decades of leading and advising major enterprise transformations, I've seen organizations place considerable reliance on their implementation partners.

That reliance is understandable.

Most companies undertake transformations of this magnitude relatively infrequently. Their executives and business process owners may have limited firsthand experience with the extraordinary complexity involved.

The SI, by contrast, may have completed dozens or hundreds of similar programs.

But implementation experience does not give the SI authority over the client's business operations.

The SI cannot independently determine whether customer data is sufficiently accurate, whether a redesigned process adequately serves the enterprise, whether employees possess the necessary competencies, or whether the business should accept the consequences of a troubled deployment.

It can advise, design, facilitate, implement, test, train, and provide evidence. Depending on its contract, it may assume substantial responsibility for delivering many of these capabilities.

But the ultimate accountability for business outcomes remains with the enterprise.

A company can outsource implementation activities. It cannot outsource accountability for the health of its business.

And an enterprise that cannot operate effectively without extraordinary ongoing support from its systems integrator has not necessarily completed its transformation—even if contractual implementation milestones have been achieved.

Why the Distinction Gets Lost

Several conditions contribute to this misunderstanding.

First, contractual completion can become a substitute for operational success.

Implementation contracts necessarily define activities and deliverables that can be described, measured, and accepted. These provide clarity for both parties.

But completion of the contracted work does not, by itself, establish that the integrated business environment will perform successfully.

Second, implementation expertise can overshadow business judgment.

Over time, the SI's assessment of progress may become more influential than the perspectives of the business stakeholders who must ultimately operate the solution.

Third, business participation is often confused with business accountability.

Business leaders assign personnel, approve requirements, participate in testing, and attend governance meetings.

Yet they may not fully appreciate their continuing responsibility to establish that the organization is operationally prepared.

Finally, project reporting reinforces the confusion.

Milestones achieved, deliverables accepted, defects resolved, and training completed are visible and measurable.

Whether the enterprise can actually perform a day's worth of business in a day is considerably harder to establish.

That requires a different kind of assessment.

When the Project Team and the Business Disagree

One of the most revealing warning signs in a transformation is a significant difference between the confidence expressed by the implementation team and the confidence expressed by business stakeholders.

I recall a major ERP implementation in which we conducted a structured readiness assessment before entering system testing.

The results revealed a striking disparity.

Nearly all members of the program organization assessed their readiness as Green or Yellow.

Most business users, however, assessed important conditions as Red or Yellow.

Both groups were participating in the same transformation, but their perspectives were dramatically different.

The implementation team was largely evaluating progress toward delivering the solution.

Business stakeholders were confronting what it would actually take to operate it.

That disparity wasn't something to average into an overall program score.

It was evidence of an important readiness concern that warranted investigation and action.

When the people building the solution are confident but the people expected to operate it are not, executives should pay close attention.

The objective isn't to determine whose opinion prevails.

It's to identify what remains unproven, understand the operational consequences, and establish the actions required to close the gaps.

A successful readiness assessment makes these differences visible early enough for the organization to do something about them.

The Business Must Define What Ready Means

One way to avoid these problems is to define readiness in terms of the business conditions that must exist for successful operation.

At Inflective, we describe these conditions as Future Truths.

A Future Truth isn't simply a task to complete or a document to approve.

It's a condition that must become true for the enterprise to operate successfully.

For example:

• Customer orders can be received, fulfilled, invoiced, and collected within required service levels.
• Financial transactions can be accurately processed, reconciled, and reported.
• Critical business data is sufficiently accurate and complete to support operations.
• Employees can perform their assigned responsibilities using the new processes and systems.
• Business continuity arrangements can protect essential operations when unexpected problems occur.

These conditions must be supported by explicit expectations, credible evidence, and assessments from accountable stakeholders.

Completing an order-management testing cycle, for example, may provide important evidence.

But the more consequential question is whether the organization has demonstrated that its people, processes, data, technology, controls, and supporting services can collectively execute the required business activity.

The SI has an important role in producing that evidence.

The business must determine whether the evidence demonstrates sufficient readiness to operate.

A Better Model for Accountability

Successful transformations require complementary responsibilities across the enterprise and its implementation partners.

The systems integrator is accountable for delivering its contractual commitments to the agreed standards of quality.

The program leadership team is accountable for coordinating delivery, integrating workstreams, identifying and escalating issues, and maintaining credible visibility into progress.

The CIO and technology organization are accountable for their assigned technology responsibilities, including the readiness of the supporting technical environment.

Business process owners are accountable for establishing that the processes, people, data, controls, and operational capabilities within their areas of responsibility are ready.

The executive sponsor and designated business leadership must ensure that significant operational risks are understood, addressed, or explicitly accepted by those authorized to make the decision.

Independent readiness assurance can strengthen this model by challenging assumptions, evaluating evidence, identifying unresolved conditions, and making differing stakeholder assessments visible.

Importantly, independent assurance doesn't replace business accountability.

It helps executives exercise that accountability with greater confidence.

From Reported Confidence to Rational Certainty

Every major transformation involves uncertainty.

No organization can eliminate every defect, resolve every exception, or anticipate every possible operational problem before deployment.

Nor should it try.

The objective isn't perfection.

It's to understand the conditions necessary for successful operation, establish which conditions have been satisfied, identify the remaining deficiencies, and make informed decisions about the consequences.

I call this Rational Certainty.

It differs from the confidence that may come from a green project dashboard or a favorable implementation status report.

Rational Certainty requires credible evidence, knowledgeable stakeholder judgment, candor about unresolved issues, and sufficient preparation to manage remaining risks.

It also requires executives who genuinely want to know whether their enterprise is ready—even when the answer is uncomfortable.

This is why we developed ASSERT™ Transformation Certainty: to complement implementation methodologies with a disciplined approach to establishing the conditions required for successful business operation.

The objective isn't to create another layer of project management.

It's to connect implementation activity with the business capabilities the transformation must deliver.

Two Organizations, One Successful Transformation

None of this diminishes the importance of a capable systems integrator.

A strong SI can make an extraordinary contribution to the success of an ERP program.

But success requires more than delivering technology, completing activities, and meeting contractual obligations.

It requires a business that's prepared to operate.

The SI and the client should work toward that outcome together, with clear responsibilities, transparent reporting, credible evidence, and business leaders who remain accountable for the consequences of their decisions.

The distinction is straightforward:

The systems integrator must deliver the solution. The enterprise must be ready to operate it.

Both responsibilities are essential.

And as Go-Live approaches, I encourage every executive sponsor to ask two questions:

Has our systems integrator delivered what it committed to deliver?

And, more importantly:

What evidence demonstrates that our business can do a day's worth of business in a day?

The first question addresses implementation delivery.

The second addresses operational readiness.

A successful transformation requires credible answers to both.

Tom Hensler is Founder and Senior Principal of Inflective, Inc., bringing more than 30 years of experience leading complex ERP and enterprise transformations. Through executive program leadership, independent readiness assurance, and ASSERT™ Transformation Certainty, Inflective helps organizations improve the predictability of major digital transformations and establish confidence that their businesses are prepared to operate successfully.