Access Official Technical PDF

Share Summary:LinkedInEmail

Engineering leadership in industrial automation draws on more than knowledge of equipment and control systems. It also requires the ability to guide technical teams, manage complex projects, connect data and business priorities, and improve how work is performed. Career profiles spanning manufacturing, product development, infrastructure, information technology, and healthcare illustrate several perspectives that can help technical decision-makers think about those responsibilities.

These experiences do not prescribe a single model for automation leadership. Instead, they show how capabilities developed in different technical and operational settings can contribute to the work of designing, delivering, and improving systems.

Engineering leadership connects technical depth with delivery

Industrial projects often bring together engineering disciplines, operations, suppliers, and business stakeholders. Leaders must therefore understand the technical work while also coordinating the people and decisions needed to move a project forward.

For example, Andrew MacDonell’s medical-device program management role involved leading a cross-functional team through a product development lifecycle, from concept to commercialization. That experience highlights a transferable leadership task: keeping multiple contributors aligned as a technical solution progresses through distinct stages. In an automation project, similar coordination may be needed among controls, electrical, mechanical, software, production, and project teams. The specific disciplines and deliverables vary, but the need to manage dependencies and communicate decisions remains.

Infrastructure experience offers another useful perspective. Maria Delgado’s work in energy and utilities included strategic planning and execution for infrastructure construction investments, alongside developing program-management practices and directing a project and portfolio management organization. This kind of portfolio view is relevant when decision-makers must assess how individual projects fit into broader operational priorities.

Product development benefits from cross-functional thinking

Automation systems are not isolated technical artifacts: they are implemented to support particular processes and users. Product-development experience can help leaders keep requirements, design choices, and delivery responsibilities connected.

Gopi Lingam leads a product design group working on a dialysis system, drawing on mechanical engineering education and earlier software engineering experience. His career illustrates how experience across technical domains can inform product work. Likewise, Avinash Madadi’s role at a manufacturer includes responsibility for electronics development for new products, following earlier research and development work and international supplier engagement.

For industrial teams, the practical lesson is to bring relevant expertise together early. Mechanical, electrical, software, and operations perspectives can help clarify how a product or system must function in its intended setting. Supplier relationships also form part of the engineering context when components must be sourced and incorporated into a design. The profiles do not specify a particular development method, but they underscore the range of responsibilities that can sit around technical product work.

Data and connectivity broaden the automation perspective

Industrial automation increasingly intersects with software, enterprise systems, and data management. Leaders who can connect these areas with operational needs are better positioned to frame technical initiatives in terms that both engineering and business teams can evaluate.

Yanhui Li’s enterprise architecture and research work involved designing and delivering customer solutions using the Internet of Things. Venky Kandaswamy’s career focused on organizing and retrieving large volumes of data across different technologies, and his later responsibilities included building a product catalog for a large retailer. These examples come from different industries, but they point to capabilities that matter in connected industrial environments: architectural thinking, data organization, and the ability to relate technology choices to a defined use.

For system integrators and plant leaders, this means treating connectivity and data as part of an operational design conversation. Teams should be clear about what information a system needs to exchange, how that information supports the intended work, and who is responsible for the relevant technical and organizational decisions. The profiles do not specify particular platforms or architectures, so these should be determined by each project’s requirements rather than assumed from general trends.

Continuous improvement depends on how work is organized

Automation initiatives are also shaped by the processes they are intended to support. Jenna Bilinski’s position as director of a Kaizen Promotion Office at a hospital involved applying Lean methodology to improve care delivery. Although healthcare is not manufacturing, the role demonstrates that continuous improvement can be organized as a dedicated leadership responsibility and applied to operational workflows.

In an industrial setting, leaders can use the same broad principle by examining the process around a proposed technology, not just the technology itself. Understanding how work is currently performed helps teams identify the problem they are trying to address and consider whether a change supports the process. Improvement also involves people: operators and other stakeholders have practical knowledge that can inform how a system is designed and introduced.

Build leadership capability across disciplines

The varied careers represented in these profiles suggest several areas for developing engineering leadership in industrial automation:

  • Coordinate across functions: Bring technical and business contributors into a shared project conversation.
  • Link design to delivery: Track how decisions affect later stages, from development through implementation and operation.
  • Connect data to purpose: Define how information and connected technologies serve a specific operational need.
  • Include process improvement: Consider workflows and users alongside equipment and software.
  • Develop team capability: Treat team leadership and resource coordination as part of technical execution.

These are not substitutes for domain-specific engineering knowledge. They complement it by helping leaders make technical work understandable, coordinated, and relevant to the organization’s goals.

Conclusion: Make technical leadership part of the system design

Industrial automation decisions are influenced by engineering design, project execution, data, suppliers, and the processes people use every day. Experience in product development, infrastructure, connected technologies, manufacturing, and continuous improvement offers different ways to approach that work. For plant managers, operations leaders, and system integrators, the practical implication is to build teams and decision processes that connect these perspectives from the outset. Strong engineering leadership helps ensure that technical choices are considered in the context of delivery, operations, and the people who will work with the resulting systems.

Access Official Technical PDF

About The Author