Why New Technology Doesn't Always Make a Company Easier to Run

The new system is live. Why is the company still doing so much of the old work?

The ERP implementation is complete. The CRM has been deployed. Warehouses have new systems. Management has new dashboards. Automation performs tasks that previously required people.

Yet orders still need intervention. Employees reconcile information between functions. Invoices are corrected. Exceptions move through the same approvals. Managers continue resolving work that arrives incomplete or cannot be executed.

The technology may be substantially better.

The company may not be easier to run.

I distinguish three achievements that management should never confuse:

Technology completion. Operating conversion. Economic conversion.

Each requires different evidence. Passing one does not establish that the next has been achieved.

My central proposition is that technology can modernize the instruments of work without changing the operating arrangement that makes the work expensive.

A company can automate the movement of work without changing why that work must move.

That is where I begin my structural examination.

1. Three achievements, three different tests

A technology project can satisfy its requirements while the enterprise continues to perform many of the same corrections, approvals and reconciliations.

In my Business Structural Drag framework, Structural Drag is work a company repeats because of how it is arranged—work a different arrangement could remove without changing what the customer receives or what the business must protect.

Technology can accelerate productive work. It can also accelerate unnecessary repetition.

The relevant distinction is not whether the software works. It is whether the work and economics surrounding the software have changed.

Consider a sales process requiring three approvals before a customer commitment can be accepted.

A new platform may make those approvals electronic and faster.

That is an improvement.

But the company still needs to establish whether all three approvals are necessary, whether the relevant authority is placed correctly, and whether the work that follows can be executed without further clarification.

The same distinction applies to manufacturing, distribution, service delivery, acquisition integration and AI.

The investment is not the operating outcome. The operating outcome is not yet the economic return.

2. Four public-company situations that reveal different conversion questions

I examined public disclosures from Tennant, DNOW (including its combination with MRC Global), embecta and TransUnion.

They are deliberately different examples: a disrupted ERP cutover, post-acquisition stabilization, stand-alone business creation, and a transformation combining technology with operating-model change.

I have not assessed these companies internally or assigned them Structural Drag profiles. The reported facts belong to the companies; the structural questions are my professional interpretations.

3. What I conclude across the four situations

The four examples do not establish one universal failure.

Tennant demonstrates the operating consequences of a difficult implementation.

DNOW identifies the work involved in moving from stabilization toward optimization.

embecta shows that systems and organizational investments may be necessary to create legitimate operating capabilities.

TransUnion reports savings from a combined operating and technology transformation.

The common analytical question is more useful than forcing a common diagnosis:

What exactly changed between paying for the technology and obtaining the economic result?

I distinguish five kinds of evidence along that path: system capability, changed work, changed resource consumption, changed delivered output and verified financial effects.

The three thresholds in Figure 1 organize the investigation; the five kinds of evidence test whether each conversion actually happened.

A successful implementation might satisfy only the first threshold.

An operational improvement might satisfy the first two while releasing capacity the company has not yet redeployed.

An economic improvement may involve cost reduction, increased throughput, improved service economics or better cash conversion.

The missing conversion may not be inside the technology.

It may be in the relationship between the technology and the work surrounding it.

4. Where Structural Drag could enter

My Business Structural Drag framework offers six competing explanations, none of which I assign to the named companies.

No Structural Drag established is equally legitimate. The issue may be technical defects, necessary transition expense, insufficient training, demand, complexity or protective controls.

Two similar technology disappointments can require opposite decisions.

A configuration defect should not automatically trigger organizational redesign. Repeated work caused by incompatible decision rules should not automatically trigger another software purchase.

The distinguishing evidence determines the decision.

For the full profile illustrations and diagnostic distinctions, see Research 01 — Why Growing Companies Become More Expensive to Run.

5. Where paid capacity goes after technology changes

One of the most important consequences of technology investment can remain invisible inside ordinary payroll.

A billing employee corrects invoices. A warehouse supervisor reconciles incomplete information. A project manager resolves contradictory commitments.

These activities may become faster after implementation without becoming unnecessary.

I use the same paid-capacity distinction introduced in Research 01.

My three established economic ledgers remain separate: verified financial effects, paid capacity consumed and contribution not earned.

I do not equate time saved with profit earned.

The connection to the Renergy™ Conversion Chain is straightforward:

Paid capacity → Usable capacity → Delivered output → Operating profit → Cash → Enterprise value

A technology gain that releases time must still become usable capacity. That capacity must then support valuable work before an additional economic contribution can be claimed.

Technology can reduce cost without increasing output, or increase output without reducing cost. Either may be valuable.

The evidence must establish which one happened.

6. Give this to your CFO, COO and technology leader

The Technology Conversion Review

Before approving a major technology investment—or declaring a transformation complete—I would require one joint report addressing seven questions.

1. What operating result did we purchase? Define the expected change in delivered work, quality, capacity, expense or cash separately from the software's technical requirements.

2. What changed in the same unit of work? Compare orders, projects, invoices, cases or other delivered units before and after implementation. Control for complexity, quality, demand and outsourcing.

3. Where does work still stop or return? Identify incomplete releases, manual escalations, repeated corrections and decisions that require intervention.

4. What work is no longer necessary? Distinguish eliminated effort from work that was merely accelerated, reassigned or transferred to another function.

5. What necessary obligations remain? Preserve safety, quality, financial controls, customer commitments and compliance.

6. Where did the released capacity go? Determine whether it became more delivered output, reduced cost, improved service, shorter lead times or unused availability.

7. What financial effect can we verify? Reconcile recurring savings, implementation expenditures, additional contribution, working capital and cash. Avoid double counting.

Four decisions are legitimate: continue technical stabilization; redesign the operating arrangement; combine technology and structural change; or deliberately change nothing.

The purpose of the review is not to justify the investment after the fact. It is to determine what the investment actually changed.

7. What would change my conclusion?

I would weaken a Structural Drag hypothesis if temporary errors disappear with technical stabilization, or if comparable work is demonstrably completed with less effort while necessary controls remain intact.

I would also weaken it if financial performance can be explained by pricing, product mix, demand, necessary investment or other conditions without an arrangement-created explanation.

I would strengthen the case for structural investigation where a technically stable system still requires repeated corrections, reconciliations and avoidable decision escalations to complete comparable work.

The decisive evidence is not the size of the technology budget.

It is the actual work performed—and whether that work would remain necessary under a different operating arrangement.

8. Before the next technology investment

A manufacturer can install a new ERP and still release incomplete work to production.

A distributor can unify technology platforms while locations continue using incompatible pricing and fulfillment rules.

An acquirer can connect systems without integrating operating decisions.

An AI tool can accelerate work that still requires the same approvals, verification and downstream corrections.

Or a company can invest in technology alongside operating-model improvements and produce measurable economic benefits.

Those situations require different decisions.

For readers focused specifically on AI, my companion work is Speed Without Conversion — The Economics of AI When You Keep Your People, with an inside-the-operation illustration in Field Case 13, Everyone Got Faster. Nothing Arrived Sooner. (a fictional composite).

My question is not whether a technology project has been completed.

My question is how much of the work surrounding that technology would still be necessary if the business were arranged differently.

A successful investment should be judged by what the technology can do, what the organization no longer needs to do, and what the company can now accomplish with the resources it already has.

Gower Idrees

Creator of the Business Structural Drag framework and the Renergy™ management framework

Sources, Evidence Notes & Research Methodology

Evidence reviewed through November 2, 2026