SAVOYE

How Early Lessons Shaped Leadership Values

Honestly, one of the biggest learning moments for me came very early, when I entered this industry as an intern and co-op. That period shaped not only what I wanted to do professionally, but also what I was determined not to do. I saw firsthand how over-complicated many systems were, especially user interfaces. Operators often had to be trained across multiple subsystem screens just to understand a single operational flow. That experience left a lasting impression and directly influenced many of the decisions we make at SAVOYE North America today, including our focus on building a single, unified interface.

I also learned early the importance of testing and code quality. Watching fixes introduce new problems reinforced that innovation comes with risk, making simulation, validation, and testing essential. Many of the strongest lessons came from stressful moments caused by poor code and limited visibility, experiences that continue to guide how we lead, build, and set standards.

Guiding Design Principles for WES Integration

Two core principles guide our software design process when integrating with multiple warehouse technologies and WES environments, integration flexibility and visibility. On integration flexibility, we are very intentional about finding the right balance. On one extreme, you can write fully custom code for every new piece of equipment, vendor, or software system, but that approach does not scale. On the other extreme, you can attempt to build a massive, highly configurable platform that supports every protocol and messaging pattern imaginable. In practice, that often results in a heavy, monolithic application burdened by unnecessary complexity.

Our goal has been to avoid both extremes. While building equipment-agnostic software was important, we also recognize that we cannot and should not support every possible integration that exists or may emerge in the future. Instead, the WES architecture was designed to allow customization primarily at the driver level. This approach lets us adapt to specific equipment behaviors and protocols without rewriting core logic or bloating the overall platform.

The second guiding principle is visibility. As we integrate with diverse equipment and subsystems, maintaining insight at the machine and subcomponent level is critical. Our vision has been to pull real-time status, faults, health data, and historical records directly into the WES, eliminating the need for users to switch between vendor interfaces. By delivering consistent, real-time visibility in the AiRVOS™ UI, we support better operations, troubleshooting, performance optimization, and long-term system reliability.

Bridging Engineering and On-Site Operations

My approach to collaboration starts with a simple but important distinction: I want our engineers to think like engineers, not just developers. Writing code is only one part of the job. The real responsibility is understanding the problem deeply and designing a solution that works in the real world.

“Two core principles guide our software design process when it comes to integrating with multiple warehouse technologies and WES environments, integration flexibility and visibility.”

In this industry, the only way to do that is to get engineers onsite. That means standing on the warehouse floor, using the equipment, working at goods-to-person stations, scanning barcodes in high-traffic areas, and experiencing the environment the software must live in. When engineers see how operators work, what slows them down, and where frustration appears, it fundamentally changes how they approach problem-solving and leads to better decisions around design, performance, and reliability.

That onsite exposure is paired with ongoing communication with operations teams. We listen to pain points, understand where productivity is lost, and learn what “good” looks like from the people running the system every day. Internally, we rely on structured collaboration through workshops, cross-functional project kickoffs, and end-to-end flow reviews. This shared understanding across engineering, operations, and on-site teams ultimately drives reliable performance once systems go live.

Navigating Leadership Challenges in Complex Environments

One of the biggest challenges in my role comes from the complexity of the systems we deliver. Working across mechanical engineering, PLC and controls, robotics, and automation, and software, it is not always immediately clear where an issue originates. In high-pressure moments, that ambiguity can create tension across customers, integrators or internal teams.

That is where strong cross-functional leadership becomes critical.  As a leader, my responsibility is to create alignment amongst the team, drive transparent communication and keep everyone centered on resolution.  When we approach challenges as one integrated team, we not only solve problems faster but we strengthen trust at the same time.

This philosophy extends to our partners, including WMS providers. From the customer’s perspective, any failure is still a failure. We push for shared accountability and win-win outcomes that deliver integrated, reliable solutions and earn customer confidence.

Trends Defining the Next Decade

In the next decade, I believe WES will increasingly leverage advanced analytics and machine learning to anticipate bottlenecks, balance workloads, and enable predictive maintenance. Data-driven decision engines will no longer be a “nice-to-have” but a must within the software running the automation.

I can also see how, as warehouses become more sensorized and connected, edge-centric decisions at the machine or zone level will complement centralized orchestration to reduce latency and improve responsiveness. Ultimately, these shifts lean toward a smarter, more autonomous, and more adaptive execution software that still keeps human decision-makers in the loop.

Skills and Mindsets for Future Leaders

From an approach perspective, you need to be able to embrace both technical depth and practical context with WES and other execution software. Understanding how software translates into physical material flow and real operational constraints is critical.

You need to be able to adopt a customer-centric mindset. Solutions should solve REAL problems, which grounds innovations in operational value rather than trying to keep up with technological industry trends. Lastly, be comfortable with complexity and integration. Logistics environments integrate software, automation hardware, data flows and people. Aspiring professionals should be open and excited to navigate systems that are constantly changing that requires continuous learning and flexibility.