In summary
  • An error in the master data (customer, supplier, item) is repeated in every order and document that refers to them, generating delays, rework, and searches.
  • Lean addresses the metadata at the source with three levers: shared standards for content, a person responsible for each metadata field, and controls at the time of creation.
  • Adverse record-keeping errors lead to the classic waste (muda) of the Lean Office: waiting, defects, unnecessary movements, redundant paperwork, overproduction of codes, and untapped talent.
  • Poka-Yoke and Jidoka applied to offices, for example pull-out menus and the reporting of duplicates, reduce corrections downstream.
  • Before introducing ERP, APS, MES, or artificial intelligence, the records need to be updated; otherwise, the waste is only digitized.
Index

Incorrect records block the flow because an error in the master data (customer, supplier, item) repeats in every order, document, and plan that calls them up, turning them into waits, reworkings, and searches. Lean brings master data management to its source: Shared standards on what each data item must contain, a single person responsible for each record, and controls on data creation instead of corrections downstream.

An example: an order is ready to be processed, but an information is missing in the customer’s record. The sales office requests a verification from the administration, someone retrieves an old email and the case remains pending. Meanwhile, a colleague notes the correction in a personal file so that he can start again more quickly the next time.

It is an illustrative example, but it makes visible a precise mechanism: a defect in the data can generate additional work at multiple points in the process. The correction takes a few minutes; the interruption, the handovers, and the waiting for the response can weigh much more on the overall time.

For those involved in continuous improvement, the records deserve the same attention as the other elements that influence the flow. The quality of the master data affects the ability to work without stopping, to repeat tasks, or to search for information that should already be available.

Addressing the issue with a Lean approach means observing where the data originates, how it is used by the offices, and what conditions maintain its reliability.

What are master data and why do they concern offices?

Master data are the reference data that are used repeatedly in business processes. They include, for example, the personal data of customers, suppliers, and materials, along with information such as classifications, units of measurement, and payment terms. master data management (MDM) It is the set of rules, roles, and processes by which a company creates, updates, and controls this data. It serves as the link between the business, which understands the meaning of the information, and IT, which manages the systems.

An order describes a specific operation; the ledger contains information that can be referenced by many orders. This difference helps to understand why an error in the ledger may recur in subsequent operations and involve different people.

The same data can serve multiple functions. Information entered by the salesperson may be necessary for administration or logistics. A material attribute can influence purchasing, planning, and warehouse activities. Therefore, the quality of the data must be evaluated in relation to the entire process that uses it.

The impact of the article metadata on operational processes

The weight of the records is clearly seen in the article record: some fields, filled out once, guide every day purchases, planning, and warehouse operations.

Some fields of the article taxonomy and their effect on the flow
Field What it is for If it is wrong
Lead time of procurement Deciding when to order Delayed material and a standstill in production, or early orders and unnecessary stock
Security Guard Protecting the service from changes in demand Stock or warehouse shortages inflated
Size of the lot Calculating how much to order or produce Excessive quantities compared to real demand
Equipment and processing times Plan capacity and delivery dates Unrealistic plans and promises that are not kept
Units of measurement and conversions Moving from purchasing to warehousing to production Incorrect quantities ordered or collected
Replacement material and end of use date Managing the transition from one code to another Purchases of obsolete or discontinued material due to a code that is no longer available

A field that is enhanced on its own does not guarantee that the information can be used. A given fact may be present but be superseded, formally correct but inconsistent with other attributes, or understandable only to the person who inserted it. The problem often arises when another person must use it to make a decision or complete an activity.

How an administrative error generates waste in the flow

In offices, many interruptions become confused with everyday work. Seeking confirmation, rewriting a given fact, or asking which version is correct can seem to be an inevitable part of managing a practice. Observing the process, these activities become recognizable as consequences of unreliable information.

These effects correspond to the classic ones. waste (muda) that the Lean Office It recognizes them in the offices. The table links them to typical examples related to the census records.

The waste generated by a wrong address
Waste (muda) As seen in the office Master data example
Waiting Files on hold awaiting confirmation Order blocked because the customer's payment condition is missing
Defects and rework Documents to be corrected and reinserted Invoices are filled out because the billing address has expired
Useless movements Research between emails, files and systems Telephone call to the purchasing department to find out which of the two provider codes to use
Transport Handover of documents between offices to clarify a given matter The request goes from the sales department to the administration and back
Stocks Parallel practices and archives to be reconciled Personal client files «with the right corrections»
Overproduction Anagrafic data created without their being needed New article code opened for a variant that already existed
Unexploited talent Qualified people engaged in reconstructing information A buyer who spends hours reconciling codes instead of working on suppliers

Pending expectations and practices

When a necessary data is missing, the activity can stop until a colleague, customer, or supplier responds. The actual time for correction can be short, while the practice remains suspended among other priorities. The accumulation of pending practices also makes it more difficult to understand which ones are truly ready to move forward.

Corrections and reworkings

An incorrect information may require the revision of documents or the reinsertion of already processed data. Correcting the error only on the operational document, leaving the address unchanged, exposes the operation to the same anomaly. The offices thus repeat the work without removing the cause.

Further research and passages

When systems return conflicting information, people must determine which is valid. Emails are consulted, files are compared, and other offices are involved. Each step consumes time and increases the number of activities required to complete the initial request.

Duplicate entries and parallel archives

To protect themselves from uncertainties, offices can build local lists and personal notes. These tools help to overcome urgency, but they require updates and reconciliations. If the versions differ, finding the correct data becomes even more complex.

The point to observe is the link between the defect and its consequences. Counting only the incorrect entries can underestimate the problem: a single error can generate several interruptions before someone identifies it and corrects it in a stable way.

Following the data beyond the boundaries of the individual office

Let’s consider a second illustrative example. If someone opens a new record, they register with the same provider using two different codes, because they don’t recognize the one that already exists. Purchases use one code, while part of the administrative documents use the other.

The offices must verify the matches and reconstruct the information. Often this difficulty is perceived as an administrative problem, although its origin lies in the creation of the registry and the rules used to recognize an already existing subject.

A Lean reading follows the complete process. What information was needed to avoid duplication? Was it available? Did people use common criteria? Did the system help recognize the existing record? Did the creation request arrive with sufficient elements?

These questions shift the focus to working conditions. Limiting oneself to asking for more attention to those entering the data leaves any ambiguities in the forms, criteria, or between functions unresolved.

The collaboration between those who generate the information and those who use it helps to make visible needs that, within the individual office, may seem secondary. An attribute that is not particularly relevant in the first step may be indispensable for the next step.

The “who creates / who uses” matrix for the master data

A simple tool to make this connection visible is the “who creates / who uses” matrix.”For each record, indicate which function creates it (C) and which uses it (U). Where there are many U's and no shared rule, it is best to act first. An example:

Matrix “who creates / who uses” (example)
Anagrafica Commercial Technical Office Purchases Planning Warehouse and logistics Administration
Customer C – – U U U
Supplier – – C U U U
Article U C U U U U
Distinct base and cycle – C U U – U
List price and terms of sale C – – – – U

C = creates the data · U = uses it. In every company the matrix changes and is reconstructed based on the Process maps.

Shared standards to make the data usable

Standardization helps different people and functions interpret and manage data in the same way. It requires clarifying what information represents, when it is needed, and what characteristics it must have to support the process.

In the data management master, standards can concern the meaning of fields, naming conventions, the allowed formats, and the conditions for creating or modifying a record. Their usefulness depends on the ability to meet the real needs of users.

Asking for many fields without a comprehensible purpose can increase the compilation work and favor values entered only to overcome a block. The choice of the necessary information must therefore be based on the activities that those data allow to be carried out.

The moment counts too. Some data may be available upon the request’s opening; others require subsequent verification. Making this distinction explicit helps to understand when an address record is ready for a particular use and when it still needs to be completed.

Standards must also be accessible and understandable. If the rules remain in the memory of only a few people, quality depends on their presence. A shared rule, on the other hand, allows for more continuous management of recurring situations and for recognizing those that require specific evaluation.

Clear responsibilities in master data management

An address book can be corrected at the time of creation and become unreliable over time. Commercial conditions, classifications or operational information change. For this reason, the management must also include updating, verifying and discontinuing the use of outdated data.

Responsibilities throughout this life cycle need to be made recognizable. What function determines the meaning of the data and the quality rules? Who is responsible for inserting and updating it? What role does it play in assessing changes that have effects on other functions, and to whom can those who discover an anomaly turn for help?

In Master Data Governance, the responsibilities regarding content and technical aspects must be clearly defined. Business functions know the meaning of information and its operational impact; IT makes applications, authorizations, and integrations available that are consistent with the defined requirements. In practice, the most common roles are two: data owner, the person responsible for the business of a data class (for example, the commercial area for customers), who decides on its meaning and rules, and data steward, We also talk about it in the article on the quality, requests and anomalies that are monitored every day. industrial data governance.

This collaboration avoids entrusting an organizational matter entirely to the configuration of the software. An application can make a field mandatory, but the decision on what it should contain requires knowledge of the process.

Clarity of roles should also simplify the management of anomalies. If every doubt generates a long chain of requests, the oversight of data risks becoming a source of waiting itself. Approvals should therefore be commensurate with the impact of the changes, with paths that are understandable for ordinary situations and for exceptions.

Source controls to reduce corrections downstream

Intercepting inconsistent information close to the moment it arises prevents it from entering subsequent activities. This is the link between data quality and error prevention: designing the work to make the correct insertion easier and anomalies more recognizable.

For example, a drop-down menu instead of free text reduces the number of writing variations of the same value. A warning about possible duplicates can help verify the existence of an address record before creating another one. A consistency check can highlight a combination of information that is incompatible with the defined rules.

These examples apply two Lean tools to offices: the Poka-Yoke, which makes it difficult to make mistakes, and Jidoka, The principle that work stops as soon as an anomaly appears instead of letting it flow downstream. It is the same way that quality is built into every phase of the production process. However, choosing control requires knowing the error to be prevented and the point at which it is most effective to intervene.

A formal control has precise limits. It can verify that a field is filled in or conforms to a format, without ascertaining that the content corresponds to reality. For this reason, application rules, knowledge of the process, and accountability must work together.

The five dimensions of quality in master data management

To choose the controls, it is advisable to start from the size of the data quality used in international master data management standards, such as the DAMA-DMBOKFor each of them, one asks what could go wrong and where to stop it.

Data quality: what to check at the source
Size The question Source control (example) Indicator
Completeness Are there all the fields that are useful to those who will use the data? Different mandatory fields for different types of data, only those that are useful % of complete records at the first entry
Uniqueness Does the subject already exist? Search for possible duplicates (VAT number, company name, address) before creating Duplicate found
Consistency Are the fields compatible with each other and with other systems? Rules that block incompatible combinations, for example units of measurement without conversion Anomalies reported downstream
Current Affairs Is the data still valid today? Revision date for data that changes: conditions, referents, prices Non-revised CVs submitted by the due date
Validity Does the value respect the accepted formats and values? Ribboned menu instead of free text; formal control of IBAN and VAT number % of requests rejected during verification

The effect on daily work must also be observed. An incomprehensible blockage can lead to requests for assistance or shortcuts. The control should help the person understand what is missing and how to obtain a valid response, while maintaining a balance between the risk of error and the effort required to prevent it.

Correcting the historical record and preventing new mistakes

Cleaning up existing records may be necessary to recover duplicate, incomplete, or inconsistent data. However, to maintain the benefits of these records, it is also necessary to intervene in the process that feeds and updates those archives.

If they continue to enter information with different criteria, the quality can deteriorate again. The historical correction and the ordinary data management master must therefore share compatible rules and recognizable responsibilities.

A useful sign is the recurrence of the abnormalities. When offices repeatedly correct the same type of error, it is worth asking what condition it reproduces. It could be an ambiguous field, an undefined responsibility, or an update that does not reach all the affected systems.

Improvement also requires information being returned to those who can act on the cause. Those who encounter the error downstream must be able to report it through a clear process; those who oversee the registry must be able to distinguish the isolated case from a recurring problem. A simple way is to bring recurring anomalies to the brief meeting of the registry team. Daily Management of the office, where it is decided who intervenes in the case.

This continuity transforms the correction into an opportunity for learning and allows for the updating of standards based on the problems actually observed.

Measuring the quality of the master data in the flow

To evaluate the results, it is useful to combine demographic indicators with those related to the process. Complete records are important, but they take on operational significance when they reduce interruptions and rework.

Indicators such as lead time, processing practices, and good first-pass activities allow us to read the operation of the process. Applied to the topic of records management, they help us observe whether the available information allows people to complete the work without subsequent corrections.

One can pay attention to the practices suspended due to name registration problems, to repeated requests for clarification, and to the time spent recovering information. The choice depends on the process and the ability to distinguish the causes: a delay can have different origins, and it is necessary to verify how much it actually depends on the data. For the process of creating the name registers, the coding time from request to usable name register is also measured, as well as the percentage of requests rejected or postponed due to missing information: they indicate whether the request arrives with what is needed.

The comparison must maintain consistent conditions and definitions. Counting all the blocked practices without understanding the reason can lead to intervening on the wrong problem. Even an initial increase in reports can reflect a greater visibility of the existing anomalies.

The purpose of the measurement is to identify where to act and verify whether the change facilitates the work. When offices devote less time to reconstructing information and more time to completing requests, the improvement in data quality becomes noticeable in the flow.

Master data and digital projects: first the data, then the system

The issue becomes even more evident when the company introduces a new ERP, an advanced planning system (APS), a MES, or artificial intelligence tools. These systems use the records to calculate needs, times, and priorities: if the distinctives or cycles are inconsistent, the APS produces unrealistic plans; if the product record is incorrect, the AI returns incorrect results with the same certainty as the correct ones. For this reason, master data management, with the cleaning of the records and the rules for maintaining them, must be set up in the first phase of a digital project and not after its launch: otherwise, instead of eliminating the waste, They are digitized.

Where to start to make the problem visible

For a first reading, it is advisable to focus on a recognizable process, in which interruptions are observable. The path of an order or a purchase request helps to see what data people use and where doubts or corrections emerge.

Comparing the functions involved allows us to reconstruct the link between the initial error and the subsequent work. This makes it possible to assess priorities based on their impact on the process, avoiding tackling all the details with the same urgency.

The initial questions can remain simple: what information forces us to stop? What errors recur? Who can update the official data? Will the correction also reach those who will use it later?

The answers help to narrow down the problem. Defining the solutions then requires integrating process knowledge, organizational skills, and system support. It is in this area that the data management master’s degree becomes an integral part of improving office operations continuously.

Deepen the improvement of office processes

Recognizing the waste associated with information is a starting point for building more fluid processes. To address them methodically, skills in observing, mapping, and reviewing work across functions are needed.

The Lean Office & Service course from Lean Factory School® It delves into the application of Lean Thinking to office and service activities, with moments of discussion and exercises.

Frequently Asked Questions

What are master data and why do incorrect records block the workflow in the company?

Master data are the reference data repeatedly called upon in processes, such as customer, supplier and material records, measurement units and payment terms. If an entry is incorrect, the error reappears in every order that uses it and causes delays, rework, searches and transfers between offices.

What waste (muda) in the Lean Office generates an incorrect or incomplete record?

An incorrect address generates all the main office muda. Problem: order is blocked due to a missing payment condition. Flaws: invoice is filled out for an outdated address. Unnecessary steps: searches between emails and files. Then handovers, parallel archives, duplicate item codes, and buyers busy reconciling data instead of working on suppliers.

How are Poka-Yoke and Jidoka applied to quality control of master data?

Poka-Yoke makes it difficult to make mistakes: a drop-down menu instead of free text reduces the number of writing variants, and a signal of possible duplication prevents creating the same supplier twice. Jidoka stops the work as soon as an anomaly appears, preventing it from flowing downstream. However, a formal check verifies the format, not the veracity of the content.

What data quality dimensions should be checked at the source according to the DAMA-DMBOK?

The dimensions indicated are five: completeness, uniqueness, consistency, timeliness, and validity. For each of them, we ask ourselves what could go wrong and where to stop it. Examples include different mandatory fields for different types of identity documents, the search for duplicates on the VAT number, the revision date, and the formal verification of the IBAN.

What is the difference between a data owner and a data steward in Master Data Governance?

The data owner is the business manager of a data class, for example the commercial area for customers, and decides on its meaning and rules. The data steward oversees the quality, requests, and anomalies on a daily basis. IT, on the other hand, provides applications, authorizations, and integrations that are consistent with the rules defined by the business.

Why organize the data before introducing a new ERP, APS, MES or artificial intelligence?

These systems use the demographic data to calculate needs, timelines, and priorities. With inconsistent or inconsistent data, APS produces unrealistic plans, and with an incorrect demographic data product, AI produces incorrect results with the same certainty as the correct ones. Data cleaning and maintenance rules should therefore be planned in the first phase of the project, not after the launch.

Bonfiglioli Consulting          Copyright © 2026 Bonfiglioli Consulting.  All rights reserved.  P.I. 02646871208          Privacy Policy  |  Cookie Policy  |  Adjust Preferences