You describe partnership as going beyond transactions. What does that distinction mean in practice within the automotive industry?

Yasmine King

I see partnership as a system design requirement, not just a commercial model.

As vehicles become software-defined, connected, and electrified, the performance of the system is no longer determined by any single component. It is determined by how well those components interact across company boundaries.

From an engineering perspective, that changes how you build. You are no longer optimizing a product in isolation. You are designing for interoperability, for evolution, and for behavior over time within a larger system.

The most effective partnerships are the ones that create shared understanding. When that exists, decisions improve, integration accelerates, and the system can evolve without constant rework.

Shalini Palmer

For me, partnership means moving beyond the idea of a customer and supplier relationship as simply an exchange of products or services. In automotive, the challenges are now too complex, too interconnected, and moving too quickly for that model to be enough. Real partnership means staying close to the customer's priorities, understanding the pain points behind the immediate requirement, and working together over time to solve them.

What matters in practice is trust, consistency, and shared accountability. The strongest partnerships are the ones where you are not just there for one program or one commercial moment, but where you are helping shape the direction of travel, aligning teams, and staying engaged as needs evolve. That is where long-term value is created.

Yasmine King

Building on that, true partnerships shape how systems are designed and evolve over time. In increasingly complex environments, system performance is shaped as much by decisions made across company boundaries as within them. That requires shared problem solving across technical, commercial, and strategic dimensions, coupled with a long-term commitment to adapt, scale, and deliver together as requirements and architectures change.

As two women CVPs leading a unified automotive strategy, how does that shared leadership model actually work day to day?

Shalini Palmer

Day to day, shared leadership works when there is clarity of purpose and trust in each other's strengths. My focus is naturally very close to the customer, to market needs, to how we build strong relationships, and to making sure we are executing in a way that creates growth and long-term value. That gives me a direct view into what customers are prioritizing, where pressures are emerging, and where we need to respond quickly.

What makes the model effective is that this customer and market insight is not separate from strategy, it feeds directly into it. Shared leadership only works when there is openness, constant alignment, and no sense of working in silos. In an industry like automotive, the commercial reality and the technology direction have to move together.

Yasmine King

Shared leadership works when both leaders are deeply connected to the present and aligned on the future.

My role requires continuously bridging those two perspectives. I spend time directly with customers and partners to understand what is happening in real time, while also making investment decisions that position us for where the industry is going. That combination is critical because many of the decisions we make today, particularly around architecture and technology direction, will define what is possible several years from now.

Shalini Palmer

Our shared leadership model works because it is built on alignment rather than overlap. We bring different perspectives, but we are focused on the same outcome, which is creating a strong, unified automotive strategy that is grounded in both customer reality and future direction. The day-to-day reality is a lot of listening, a lot of alignment, and a lot of translating insight into action. That is what keeps the model practical and effective.

Your leadership journeys have been shaped by trust, collaboration, and relationships. How have those three things shown up differently at different stages of your careers?

Shalini Palmer

At different stages of my career, trust, collaboration, and relationships have meant different things. Early on, trust was often about proving myself, building credibility, and having the confidence to speak up. As my career progressed, collaboration became more about how to bring teams together, how to align people around a shared goal, and how to create an environment where others could succeed.

Today, relationships mean something even broader. They are not only important for delivering results, they are also central to how you support people, sponsor talent, and help create a culture where others can grow. At senior leadership level, trust is not just something you earn personally, it is something you help build across teams, customers, and the wider organization.

Yasmine King

For me, trust, collaboration, and relationships have evolved alongside how I interpret and act on complexity.

Early in my career, trust was built through technical depth and consistency. It was about understanding problems at a detailed level and delivering reliably. Collaboration at that stage was often focused on solving well-defined problems within a team.

As my roles expanded across engineering, customer-facing, and business functions, collaboration took on a different meaning. It became less about solving a single problem and more about connecting perspectives. That required a different kind of listening, being able to interpret signal versus noise across customers, technologies, and teams.

Shalini Palmer

Trust, collaboration, and relationships have always mattered, but the way they show up changes over time. Earlier in a career, they are often about building credibility and learning how to contribute. Later, they become much more about enabling others, aligning teams, and creating the conditions for bigger outcomes. What stays constant is that leadership is never only about expertise, it is also about how you work with people and how much confidence they have in building with you.

Trusted mobility is the destination you are working toward. What does that mean for the automotive industry and who is responsible for delivering it?

Yasmine King

I see trusted mobility as an architectural outcome.

As vehicles become more software-defined and electrified, the complexity of the system increases significantly. Trust can no longer be achieved through individual component performance. It has to be built into how the system is designed, observed, and evolved over time.

From an engineering perspective, that means systems that are observable, adaptable, and designed for integration. You need to understand how the vehicle is behaving in real time across sensing, compute, connectivity, and energy domains. You need to be able to update software safely and reliably over the lifecycle. And you need architectures that allow data to move across the system in a way that enables coordinated decision-making.

This is where the underlying architecture becomes critical. The network, the energy system, and the sensing infrastructure all play a role in enabling that level of coordination.

Shalini Palmer

To me, trusted mobility means creating vehicles and mobility experiences that people can rely on, not just at launch, but across their whole lifecycle. Trust has to extend across safety, reliability, performance, and the ability to adapt over time. In today's automotive world, where software, electrification, and connectivity are becoming more central, that trust depends on much more than one technology or one company.

Responsibility for delivering it is shared. OEMs, suppliers, technology partners, and the wider ecosystem all have a role to play. Trusted mobility is built when there is strong collaboration, clear accountability, and a commitment to designing solutions that are resilient as well as innovative.

Yasmine King

And because no single company owns the full system, delivering trusted mobility is inherently an ecosystem effort. It requires alignment across hardware, software, and system-level design decisions to ensure those systems function as intended at scale. Enabling this future is a shared responsibility across the industry that depends on deep collaboration, open thinking, and a commitment to build trust into the system from the start.