Human-Centered Supply Chain: A Conversation with Tatyana Ventura, Director of Customer Success at RFgen

Reframing Modernization: What a Human-Centered Supply Chain Actually Means

What is a human-centered supply chain, and why are we hearing so much about it now?

Tatyana: We’re now operating in what many call Supply Chain 5.0, and at its core there is a stronger focus on people. A human-centered supply chain is built around the reality that operations run because of people. That includes operators, supervisors, planners, drivers, customers, and suppliers. It means designing around people rather than around processes or automation alone and leveraging technology to support human judgment rather than replacing it.

For years, supply chain leaders focused heavily on automation and digitalization. Supply chain was viewed primarily as a cost center, and labor was often seen as the largest cost to reduce. The assumption was that greater efficiency meant reducing human involvement wherever possible.

Leaders are now recognizing that supply chains depend on people. Whether or not robots or other types of automation are introduced, there will always be exceptions, variability, and judgment calls. That shift changes the lens. Automation becomes a way to augment people, not eliminate them.

What changed to accelerate the shift toward human-centric operations?

Tatyana: The early 2020s really accelerated that shift. COVID exposed just how fragile many global supply chains were and forced resilience to move from a buzzword to a priority. Organizations had to rethink supplier relationships, distribution models, and demand volatility.

At the same time, sustainability moved from a reporting exercise to an operational constraint. It began influencing sourcing decisions, production planning, and transportation choices in very concrete ways.

Labor volatility was another big factor. We’ve seen high turnover, retirements, and difficulty onboarding new workers forced leaders to rethink how systems support people on the floor. Efficiency alone was no longer enough. Reliability, adaptability, and workforce support became equally important.

When you put all of that together, it naturally shifts the focus.

Why is technology finally able to support this shift?

Tatyana: We’re at a point where the technology is mature enough to support how operations really run. Enabling technologies like AI, machine learning, robotics, analytics, and connected digital ecosystems are now capable of supporting a lot more than just improving efficiency.

Organizations can realistically pursue faster disruption detection, smarter scenario planning, worker-assist systems, and network-wide traceability. A few years ago, a lot of that felt aspiration. Now, it’s very achievable.

When you combine that progress in technology with the pressure for resilience, labor challenges, and sustainability requirements, it naturally leads to what we call Supply Chain 5.0. It is not a rejection of automation. It’s about using automation in a way that helps people perform better, make smarter decisions, and adapt when things don’t go as planned.

Where Supply Chain Execution Breaks Down & What it Costs

How does the lack of human focus in supply chain execution show up today?

Tatyana: Human centricity really starts with recognizing and admitting human reality. Leaders expect systems to represent reality, but many execution systems actually represent intentions.

The gaps show up in three predictable places:

First is usability. User experience is often treated as cosmetic, but on a shop floor, it directly impacts productivity. Seconds matter. If a transaction takes more than three to five seconds to complete, workers walk away.

We’re implementing a customer right now who spent millions on a brand-new ERP. But the UI of the ERP-native RF solution was so difficult to use that adoption stalled at about 17 percent. They ultimately scrapped it.

Second is connectivity. Leaders assume they have strong Wi-Fi because a site survey was done. Then go-live happens, and operations stall because of dead zones. Work doesn’t pause when the network drops, so teams find ways to keep moving.

Third is shadow work. Leaders often underestimate how much it exists. People compensate for system gaps with spreadsheets, paper logs, and double-checking. That shadow work may be invisible in planning meetings but painfully visible during audits, inventory counts, and end-of-month close.

What behavioral or operational breaking points signal that it’s time to modernize processes or systems?

Tatyana: They’re fairly common.
The first is when inventory accuracy pain starts to feel like real operational risk. You can survive on “pretty good” for a while, but when you’re competing against organizations with true inventory accuracy, that gap eventually shows up in your bottom line.

Labor volatility is another major signal. We’re seeing high turnover and a lot of people retiring across the industry. The breaking point comes when you can’t onboard new employees quickly, or when training takes too long because the systems aren’t intuitive. When knowledge walks out the door and workflows aren’t easy to follow, it becomes clear that something has to change.

Compliance and traceability have also become much more real. We have a customer that imports paper cups into the EU, and new requirements mean they have to show, down to a specific plot in the forest, where the tree originated for each pallet shipped. At that point, traceability isn’t just reporting. It’s operational.

What are the red flags that frontline teams are struggling with the systems they’re expected to use?

Tatyana: It usually shows up in small but telling behaviors. People start writing things down “just in case.” They rekey transactions later. You see duplicate work and avoidable errors. Sessions time out and have to be restarted. Sometimes teams avoid the system altogether because it feels slower than the workaround.

And then there’s the moment when people stop trusting what the system is telling them. They begin verifying everything manually because they assume the data might be wrong. That’s when trust starts to erode, and once that happens, usage drops and the system stops functioning as the source of truth.

What happens when organizations try to solve productivity or performance issues without addressing usability or workflow design?

Tatyana: There are three definite costs.

First is the people cost. Burnout increases and frustration builds. Experienced workers decide to retire early. Younger workers hesitate to stay when the technology they’re given feels like it came from the 1990s. Hiring becomes an even bigger challenge.

Then there are operational costs. When you don’t have an optimized process or mobile data collection, rework becomes routine. We’re working with a customer right now who pays four employees overtime for four hours each week just to perform recounts. That’s roughly $24,000 a year because the process wasn’t designed correctly in the first place.

And there’s the data cost. As we talk more about AI and advanced analytics, the reliance on clean, trustworthy data becomes critical. You can’t rely on shadow systems anymore, and any AI initiative will stall if the execution data isn’t reliable.

Those costs add up quickly when systems aren’t designed with the user in mind.

Designing Warehouse Execution Around Real Work

What does “doing it right” look like when modernizing supply chain execution on the floor?

Tatyana: Doing it right means building modernization around the information value chain, not around an org chart. It’s really about how information moves from the floor into the system and then into decisions.

It also means designing for exceptions and for human reality. People are wearing gloves. They’re moving in and out of freezers. Sometimes operators are working inside a ship hull where there’s no Wi-Fi. Leadership often imagines perfect connectivity and clean process flow, but the floor is full of interruptions, partial pallets, relabeling, staging overflow, and dead zones.

Modernization works when systems are built to accommodate that reality, not ignore it.

What’s the earliest sign that frontline adoption is improving after a warehouse technology rollout?

Tatyana: Faster training is usually the first sign. New employees become productive more quickly because the workflow makes sense.

We also see less rework, and that shows up in the error logs. When transactions are validated at the point of capture, mistakes tend to drop.

Another early indicator is reduced cognitive load. Fewer wasted steps. Safer work. Less frustration. When the system supports the task instead of slowing it down, adoption improves naturally.

How do leaders modernize warehouse execution and data capture without replacing the ERP?

Tatyana: The most reliable path is not rip and replace. It’s augment and extend, especially at the execution layer.

Keep the ERP stable. Keep the core intact. Then modernize where the work actually happens.

Execution is where data is captured, validated, and confirmed, and that can look different depending on the site, the warehouse, or the workflow. Focusing on point-of-work capture lets you improve accuracy and usability without introducing unnecessary risk to the system of record.

From a risk perspective, version-independent approaches reduce upgrade exposure. Prebuilt workflows with some local tailoring usually get you to value faster and avoid the long-term IT burden that comes from heavily customized builds that are hard to maintain later.

Continuity comes first. Design for offline or hybrid environments and then optimize from there.

How do supply chain leaders decide whether a new technology will help their teams instead of overwhelming them?

Tatyana: The first test is pretty simple: does it remove steps or add steps? If it adds friction, people are going to work around it or reject it entirely. The floor just doesn’t have time for extra complexity.

Leaders also need to avoid evaluating technology as a device purchase or a buzzword initiative. We hear things like “just buy scanners” or “barcoding is just barcodes,” but what really drives outcomes is the workflow and the validation behind it, not the hardware alone.

The difference shows up in whether captured data becomes system truth or something people feel they have to double-check.

The teams that get it right don’t pursue random acts of tech. They look at where the bottlenecks and broken handoffs are first and then build improvements that actually fit how work gets done. That’s how you avoid expensive rollouts where a system technically goes live, but adoption remains low because it was never designed around the task.

Who needs a stronger voice in supply chain technology decisions today?

Tatyana: Frontline operators and team leads. They’re the ones living with the workflow every day. If technology is designed without their input, it will miss the realities of how work actually gets done.

IT and OT owners also need to be involved earlier, especially those responsible for devices, networks, and integration points. A lot of transformation efforts run into trouble because environmental and operational constraints are considered too late, often at go-live.

When the people closest to the work and the infrastructure are part of the conversation from the start, things tend to go much more smoothly.

Trends and Practical Steps to Keep Modernization on Track

What supply chain innovation trends are quietly reshaping execution right now?

Tatyana: Offline-first design is becoming the expectation, not the exception. Mobility solutions that fail when Wi-Fi drops aren’t viable in real-world warehouse environments. Execution systems need to support continuous work, even in dead zones or unstable connectivity.

Another trend is the shift toward task-driven micro experiences instead of large, monolithic screens. A shop floor workflow is not a laptop workflow. If a screen isn’t designed around a specific task, inefficiency compounds quickly.

Both trends really come back to the same idea: execution systems have to match the physical environment and the pace of work, not the assumptions of a desktop interface.

What is a practical, low-risk starting point for warehouse modernization and better data accuracy?

Tatyana: Start where work happens on the floor and where that work becomes system data.

Identify one or two transactions that drive the most rework. It’s usually receiving, inventory moves, or cycle counts. Modernize those first with mobile data capture and validation that posts directly to the ERP.

Then build from there. Fix the highest-error workflows first, build trust in the data, and scale from there.

It’s low risk because you’re not overhauling the core ERP. Instead, you’re improving the execution layer, which delivers measurable gains in speed and accuracy and creates a stronger foundation for planning, analytics, and future AI initiatives.

Another small but powerful improvement is transaction-triggered labeling. Print the label from ERP-validated data at the moment of receipt, pick, or pack. That alone can eliminate an entire category of downstream errors.

Why do supply chain transformation projects stall, and how can leaders prevent it?

Tatyana: There are usually a few common reasons.

One is the lack of a clear North Star metric. If outcomes and KPIs aren’t defined upfront, teams can lose focus and it becomes hard to measure progress.

Another is underestimating connectivity and environmental constraints. Systems get designed for ideal conditions instead of real work, and the issues don’t show up until go-live.

And then there’s the big bang rollout. Trying to launch across too many sites or workflows at once creates unnecessary risk.

A more practical approach is to start smaller. Modernize one site or a few high-impact transactions, refine the model, and then expand. Execution should evolve over time, not be treated as a one-time event.

Final Thoughts

Modernization looks straightforward on paper. The real test is what happens at the point of work. If the system adds steps, slows people down, or breaks when connectivity drops, teams will work around it. If it supports the task and reflects what’s actually happening on the floor, adoption tends to follow.

A human-centered supply chain lives in everyday interactions between people and systems. When execution is designed around real-world conditions, people start to trust the system again. The data gets cleaner. The operation runs more consistently, and performance becomes sustainable.

Quantifying the Impact of Modernizing Execution

Improvements in execution rarely show up as a single dramatic change. They appear in faster onboarding, fewer errors, reduced rework, and more reliable system data. Over time, those incremental gains compound into measurable operational impact.

If you want to estimate what modernization could deliver in your environment, our ROI calculator provides a practical starting point based on a few inputs about your operation. You can also connect with an RFgen expert to review the assumptions and translate the results into next steps aligned to your workflows and ERP systems.