When RFID fails for organisational reasons, not technical ones

Many RFID projects are decommissioned not because the technology does not work, but because the organisation was not ready to adopt it. Technical problems can be resolved at a later stage. Those linked to people and processes, if neglected in the early phases, become difficult to remedy.

The difference between a successful implementation and one that is abandoned after a few months is rarely found in the hardware. It is found in how the organisation managed the change.

In our experience we have identified five recurring organisational mistakes that compromise RFID projects regardless of the quality of the technical solution adopted.

Mistake 1: failure to involve operators

When operational staff perceive RFID as something imposed from above, or as a threat to their role, resistance to change emerges in concrete ways: tags not applied correctly, procedures not followed, protocols ignored. The system captures incomplete or inaccurate data, and the cause is not technological.

Operator involvement is not a peripheral aspect of the project. It is a necessary condition for the system to function. Operators know the specifics of the production process better than anyone else: the exceptions not anticipated during design, the variability in workflow, the peak moments when standard procedures become difficult to follow. Ignoring this knowledge during implementation produces a system that works in theory but not in practice.

Raffaele Cinaglia, CEO of Csolutions, observes: "In the implementations we oversee, operator involvement begins before the hardware is installed, not after. We explain what will change in their daily work, gather their observations on process critical points, and incorporate this information into the system configuration. An operator who has contributed to the design of the system adopts it with a completely different attitude from one who finds it already installed without having been consulted."

Mistake 2: workflows overlaid, not redesigned

RFID is simply added to existing processes designed for barcode. Instead of eliminating manual activities, the system duplicates them: the operator continues following previous procedures and additionally has to manage the new technology. The result is a greater workload, not a lesser one.

An effective RFID implementation requires workflow redefinition, not overlay. Each phase of the process must be redesigned taking into account what the system captures automatically and what remains with the operator. Redundant activities must be eliminated. Exceptions must be managed with new procedures, not those designed for a different system.

Mistake 3: exception handling not defined

When a tag is not read, what happens? Who intervenes? Within what timeframe? With what decision-making authority?

If these questions have no defined answer before go-live, every exception becomes an open problem the system does not know how to handle. Operators improvise, often reverting to previous manual procedures. Over time, the RFID system is used only when it works without issues, while critical situations are handled outside the system. The data collected becomes partial and unreliable.

Exception handling procedures must be documented before operational launch, tested during the pilot project, and communicated to all personnel involved.

Mistake 4: ambiguous data ownership

Who is responsible for the quality of RFID data? If the answer is not precisely defined, no one takes ownership. Data quality degrades progressively: tags not updated, readings not reconciled with management systems, anomalies not reported. Over time data becomes unreliable and the system stops being consulted in operational decisions.

Data governance is not an IT topic. It is an organisational topic concerning who bears responsibility for ensuring that the information collected by the RFID system is accurate, complete, and up to date. This responsibility must be assigned to a specific person or function, with the resources and authority needed to exercise it.

Paola Barletta, Business Developer at Csolutions, adds: "Data quality is the foundation on which any advanced use of RFID technology is built. A company that wants to offer certified traceability to its customers, or to meet Digital Product Passport obligations, needs accurate and verifiable data. If data governance is not defined from the outset, this prospect remains out of reach regardless of the quality of the installed hardware."

Mistake 5: training treated as a formality

Two hours of training for a system that transforms daily work is not sufficient. Initial training can cover the basic functions of the system, but it does not prepare staff to manage the real situations that emerge in the first operational weeks: unexpected volume peaks, new product variants, cases not anticipated during testing.

Support in the first weeks after go-live is just as critical as the technical validation of the system. This is not additional training but day-to-day operational support while the team learns to manage the system under real conditions. Companies that invest in this accompaniment reach full operability in significantly less time than those that treat go-live as the project's end point.

Structured change management as a prerequisite

The five mistakes described share a common root: organisational change is treated as an automatic consequence of technology installation, rather than as a parallel and equally structured project.

A successful RFID implementation requires two distinct workstreams proceeding in parallel. The technical workstream covers hardware, software, and integration. The organisational workstream covers role redefinition, process redesign, training, data governance, and change management. Neglecting the second, even when the first is excellent, produces technically sound systems that the organisation cannot adopt.

Raffaele Cinaglia concludes: "RFID technology requires a solid organisational infrastructure as a prerequisite. Without role redefinition, data governance, and structured change management, even a technically perfect system risks being progressively abandoned in favour of the previous manual procedures, which operators know better and feel more comfortable using."

Frequently asked questions (FAQ)

How is organisational maturity measured before starting an RFID project?

The signals to evaluate include: has the company already adopted other digital systems successfully? Is management involved in data-driven decisions? Is there clear governance for the data of existing management systems? The answers to these questions indicate the degree of organisational readiness and allow the necessary interventions to be planned before go-live.

How long does change management take in an RFID project?

The change management process starts before installation and continues in the weeks following go-live. For a medium-complexity implementation in a production plant with 30 to 50 operators involved, the critical accompaniment period is typically eight to twelve weeks after go-live.

Is it possible to recover an RFID project that has failed for organisational reasons?

Yes, but it requires an honest analysis of the causes of failure and a structured intervention on the neglected organisational dimensions. Often the technical system is still functioning and does not require significant work. The effort needed concerns data governance, process redefinition, and rebuilding operational staff confidence in the system.

Contact us to assess your organisation's readiness and structure the change management path for RFID adoption.