ERP Is Not Digital Transformation

03/08/2026

ERP is a technology investment. Digital transformation is management's resolve to redesign how the company works.

The company had an ERP system. Production planning was done in Excel, inventory balances were validated through physical counts, purchase orders were confirmed by phone, and management reports were assembled from separate files.

Orders entered the system and invoices were issued. Yet any manager who wanted to know what was really happening still had to rely on personal spreadsheets and verbal confirmation.

What was missing was not another software package. What was missing was a shared operating discipline for processes, data, accountability, and decision-making.

My experience with ERP began in 1993 with ETA and later continued across Logo, Mikro, Tiger, IAS caniasERP, Workcube, and SAP. I was not simply a user. I led the design of processes, directed implementation, and remained accountable for whether the system produced business results.

Across more than three decades, one truth has remained constant: if process ownership, data discipline, and management commitment are not in place, changing the software does not change the outcome.

What Can Software Standardize If the Process Has Never Been Defined?

One of the most common mistakes in ERP programs is moving the existing way of working into the new system without first challenging it. If the same transaction is handled differently across departments, approvals add no real control, or accountability depends on specific individuals, the software will not correct those problems on its own.

A process that requires five signatures on paper can easily become a process that requires five digital approvals. The work does not become more accurate. The same delay simply continues on a screen.

The first question should not be, "Which modules should we buy?" It should be, "How should this company work?" The target process, process owner, decision authority, control points, and management reporting needs must be defined before configuration begins.

If No One Owns the Data, No One Owns the Truth

An item master, bill of materials, customer terms, pricing record, supplier lead time, or inventory location is not merely an IT record. Each one is the digital expression of a commercial or operational decision.

Creating several item codes for the same material fragments demand, hides available inventory, and distorts purchasing recommendations. Who creates the item? Who approves the bill of materials? Who may adjust inventory? Who corrects an error?

If the data has no owner, the error in the system has no real owner either.

Why Can MRP Calculate Correctly and Still Recommend the Wrong Action?

MRP builds its plan from demand, on-hand inventory, bills of materials, open supply, and lead times. The calculation engine may work exactly as designed, yet the business recommendation may still be wrong when the inputs do not reflect reality.

If inventory records cannot be trusted, the system may recommend buying material that is already in the warehouse. If production completions are posted late, capacity and availability become invisible. If sales forecasts are unrealistic, the system plans the wrong demand.

An MRP result can never be more reliable than the data entered into it or the operating discipline behind that data.

Not Every User Objection Is Resistance to Change

When an implementation struggles, the easiest explanation is that employees are resisting change. Sometimes they are. But the system may also fail to reflect the real workflow, require the same information more than once, or ask users to enter data without showing which decision that data supports.

Excel is valuable for analysis and rapid scenario work. The problem begins when critical inventory records, production plans, prices, or customer terms live in personal files. The real question is not whether people use Excel. It is whether the company still searches for the truth in Excel despite having an ERP system.

ERP Is Not an IT Project. It Is a Management Project.

The process owner defines how the work should flow. The data owner protects master data quality. IT ensures technical continuity and security. Consultants explain system capabilities. Senior management decides which processes will be standardized, which controls are required, and which decisions must be made from system data.

When these roles are blurred, the project can move forward technically while remaining ownerless organizationally. If management continues to treat personal reports as the "real" numbers, it cannot credibly expect the rest of the company to follow system discipline.

Let's Pull a Rabbit Out of the Hat

Many companies expect an ERP program to deliver something close to magic. Processes remain undefined, roles depend on individuals, inventory records are unreliable, and bills of materials are outdated. Even so, everyone assumes the problems will disappear once the new system goes live.

The software vendor is effectively expected to pull a rabbit out of the hat.

Digital transformation, however, is not magic. It is the result of management decisions made in the right sequence. I call the approach I have developed over the years—and tested in the field across different companies, ERP platforms, and transformation programs—the TAVŞAN Model.

A note for English-language readers: TAVŞAN means "rabbit" in Turkish. The Turkish acronym is retained because it preserves the six original steps of the model.

1. Management Foundation

Teşhis Et | Diagnose Reality

Do not begin with the process described in a procedure manual. Observe how the work actually gets done. Map critical flows end to end, expose off-system spreadsheets, manual controls, phone confirmations, informal decisions, and the gap between official process and field reality.

Akışı Sadeleştir | Simplify the Flow

Do not migrate the current process as-is. Remove approvals that add no control, duplicate checks, repeated data entry, and steps maintained only by habit. Define the target process, decision rights, control points, and management reporting requirements before the system is configured.

Şirketin Sahiplik Haritasını Kur | Build the Ownership Map

Assign a clear owner to every process, data domain, and decision. Separate the process owner, data owner, decision authority, and system administrator. Authority and accountability must meet in the same operating model.

2. Data and System Design

Veriyi Güvenilir Kıl | Make Data Trustworthy

Standardize item, customer, and supplier masters; bills of materials; prices; lead times; and inventory locations. Remove duplicates and outdated records. Connect sales, production, purchasing, warehousing, quality, finance, and shipping. Align access rights with actual responsibilities, and distinguish the standard flow from exception rules.

The system should not be treated as a place where data is stored. It should be the institutional infrastructure through which the right workflow is executed with the right authority and the right controls.

3. Use and Learning Discipline

Alışkanlığa Dönüştür | Make It the Way Work Gets Done

Teach users more than which field to complete. Show how a production posting affects inventory, purchasing, cost, customer commitments, and cash. Train with real scenarios, make timely data entry a daily operating standard, and maintain user support after go-live. Senior management must also make decisions from system data.

Neticeyi Ölç ve Geliştir | Measure and Improve Results

Track inventory accuracy, timely data entry, the share of critical transactions completed in the system, manual corrections, master-data defects and duplicates, system-generated management reports, and dependence on critical spreadsheets. Use the KPIs to identify root causes and improve the process—not merely to audit users.

Until the system becomes the company's daily way of working and making decisions, the project may go live, but the company has not transformed.

The First 90 Days with the TAVŞAN Model

DAYS 1–30
SEE REALITY

DAYS 31–60
DESIGN THE TARGET

DAYS 61–90
PILOT, MEASURE, IMPROVE

Review critical processes and actual system use. Identify off-system spreadsheets, master-data defects, inventory discrepancies, reporting gaps, and operational risks.Output: a current-state map of processes, data, and system use.

Simplify priority processes. Assign process and data owners. Define the data-cleansing plan, authority matrix, control points, and management reports. Select a pilot.Output: an approved target process and accountability design.

Launch the pilot. Train users with real scenarios. Measure data quality and core KPIs. Establish a weekly review cadence and a roadmap for scaling.Output: a tested pilot, measurable results, and a transformation roadmap.

Conclusion

The company at the beginning of this article did not have an ERP availability problem. It had an operating-model problem—one that made Excel planning, physical inventory verification, and phone-based purchasing confirmation necessary. The software had been installed, but process, data, and accountability had not become a shared management system.

The purpose of the TAVŞAN Model is not simply to install another platform. It is to build the management foundation first, make data and system design trustworthy next, and then turn use and learning into an enduring discipline. The first 90 days begin the diagnosis, design, pilot, and measurement cycle. The real change occurs when management continues to make decisions from system data after the project team has left.

The rabbit that needs to come out of the hat is not ERP. It is a company whose data can be trusted, whose processes can be traced, whose accountabilities are clear, and whose decisions can be measured. ERP is a technology investment; digital transformation is management's resolve to change how the company works.

Editorial, Legal, and Intellectual Property Note

This article is an original management essay prepared from Orkun Akçasarı's experience since 1993 in executive leadership, process design, ERP implementation, operating-model development, and organizational transformation across multiple industries and systems.

The TAVŞAN Model described in this article was developed by Orkun Akçasarı over time and shaped through field application across different companies, ERP platforms, and transformation programs. The name of the model, the sequencing and grouping of its six steps, its three-layer architecture, the First 90 Days application structure, the explanations, terminology, written presentation, and the arrangement of these elements as a whole are attributable to the author.

The model is a management framework derived from professional practice. It is not presented as an academically validated universal standard, a legal opinion, or a ready-made prescription that can be applied identically to every organization. Any application should be adapted to the company's ownership structure, scale, regulatory environment, data maturity, risk profile, and operating needs.

The company and field examples in this article have been anonymized. To protect confidential information, trade secrets, personal data, and organization-specific details, certain passages may synthesize lessons drawn from more than one experience. The article is not intended to target, accuse, criticize, or damage the reputation of any company, shareholder, employee, executive, software provider, or consulting organization.

ETA, Logo, Mikro, Tiger, IAS caniasERP, Workcube, SAP, and any other product, company, or brand names mentioned in the article belong to their respective owners. They are referenced solely to describe the author's professional experience and the context of the subject matter. Their inclusion does not imply representation, endorsement, sponsorship, partnership, certification, or any other commercial relationship.

This article offers a general management, process, data, and organizational perspective. It does not constitute legal, financial, tax, accounting, cybersecurity, technical architecture, software-selection, or implementation advice for any specific company. Qualified professional advice should be obtained before making decisions that create legal, financial, technical, or operational obligations.

Except to the extent permitted by applicable law, no part of this article—or any substantial part of the TAVŞAN Model as expressed in this article—may be reproduced, translated, adapted, renamed, republished, distributed, incorporated into training, consulting, presentations, reports, software, digital tools, methodologies, or other commercial products without the author's prior written permission.

Limited quotation for review, commentary, research, or educational purposes must clearly identify the author, the full title of the article, the publication date, and the active source URL. Any commercial use, institutional implementation, licensing, republication, derivative work, or use of the model name in a manner that suggests authorization, affiliation, or endorsement requires prior written permission from the author.

This notice does not create protection beyond the rights available under applicable law. Questions concerning copyright registration, evidentiary deposits, trademark protection, licensing, or enforcement should be reviewed with qualified legal counsel.

Bibliography and Source URLs

All web addresses below were verified on August 3, 2026. URLs are displayed in full for publication transparency and direct access.

Technical and Institutional Sources

Oracle — Material Requirements Planning

Technical overview of MRP inputs, including master schedules, bills of materials, scheduled receipts, on-hand inventory, lead times, and order modifiers.

https://docs.oracle.com/cd/E26401_01/doc.122/e48795/T478564T478850.htm

Oracle Türkiye — What Is ERP Implementation?

Overview of ERP implementation and the organizational requirements surrounding adoption, process alignment, and data quality.

https://www.oracle.com/tr/erp/what-is-erp/implementation/

SAP — What Is Master Data Management?

Overview of master data management, trusted enterprise data, standardization, governance, and duplicate prevention.

https://www.sap.com/resources/what-is-mdm

Microsoft Learn — Plan a Dynamics 365 Implementation Strategy

Guidance on process definition, implementation ownership, integrations, security, reporting, training, and change management.

https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/implementation-strategy

Microsoft Learn — Manage Changes During Transition and Handover

Guidance on adoption and measurement after go-live, including operational use and transition to business ownership.

https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/change-management-transition-handover

Microsoft Learn — Manage Changes in the Project Plan

Guidance on user participation, resistance, communication, process design, and integrating change management into the implementation plan.

https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/change-management-project-plan

IBM — What Is Digital Transformation?

Overview of digital transformation as a business strategy that extends beyond technology implementation to processes, operations, products, and organizational change.

https://www.ibm.com/think/topics/digital-transformation

Copyright and Trademark Sources

Republic of Türkiye Ministry of Culture and Tourism, General Directorate of Copyright — General Questions

Official information concerning authorship, economic and moral rights, and copyright protection under Turkish law.

https://telifhaklari.ktb.gov.tr/TR-332449/genel-sorular.html

Republic of Türkiye Ministry of Culture and Tourism, General Directorate of Copyright — Voluntary Registration and Recordation

Official information concerning voluntary registration as an evidentiary mechanism.

https://telifhaklari.ktb.gov.tr/TR-332370/istege-bagli-kayit-tescil.html

Turkish Patent and Trademark Office — Trademarks

Official information concerning trademark registration and protection.

https://www.turkpatent.gov.tr/tr/marka

Turkish Patent and Trademark Office — Trademark Search

Official trademark search interface.

https://www.turkpatent.gov.tr/arastirma-yap