Lakshmi Kalyani Kolli

Three things, in order of impact: deliberate exposure to high-accountability situations early in my career, leaders who placed me there intentionally, and a consistent decision to stay close to where execution actually happens rather than where it gets reported. The mentors who shaped me most didn't offer guidance from a distance — they positioned me in roles where the consequences of poor judgment were real and visible. That accelerated my development in ways that structured learning programs rarely do.

One experience in particular has stayed with me. I was working on an EV battery program that presented as on-track across all standard reporting. When I cross-referenced the actual cell supply commitments against pack integration timelines, we were three to four weeks from a program-critical stoppage that had not yet been surfaced. The data existed — it simply hadn't been synthesized into a single, honest picture.

Raising that assessment meant informing senior leadership that a schedule already communicated externally was at risk, before I had a complete solution in hand. It created friction. But the program responded — sourcing was escalated, integration sequencing was restructured — and we avoided what would otherwise have been a six-week slip at the worst point in the launch cycle.

That experience reinforced something I've applied consistently since: the organizational cost of surfacing a risk early is almost always lower than the cost of surfacing it late. Leadership, in my view, is not about reporting status — it is about ensuring that the people who need to act on reality have access to it while they still can.

That principle has been the foundation of whatever success I've built.

The most consequential advice I received came from a program director I worked under early in my career — someone with two decades of large-scale manufacturing experience who had little patience for what she called "smooth conversations that go nowhere." After a cross-functional alignment meeting where I had spent ninety minutes carefully managing the tension in the room — and left without a single decision made — she said: "You're optimizing for agreement. Optimize for clarity instead."

It took time to fully internalize. In cross-functional programs, alignment feels like progress. But I came to understand that early consensus is often deferred conflict. The real constraints — cost, timing, technical feasibility — haven't been stress-tested yet. You've created the appearance of alignment without confirming whether it will hold.

The situation that proved it involved a sourcing decision for compute and camera hardware on a robotics-adjacent platform. Engineering required performance headroom. Supply chain needed lead-time predictability. Finance had a cost ceiling that made the preferred vendor nonviable at volume. Three teams, three legitimate positions, weeks of circular discussion.

Rather than continuing to manage toward consensus, I put the tradeoffs on the table directly — the specific gains and losses associated with each option, and the risks each path carried at scale. The conversation slowed for roughly twenty minutes. Three weeks of stalled progress resolved.

The shift from agreement-seeking to clarity-seeking is the single most transferable change I've made in how I operate. It is more demanding in the short term. It is also the only approach that produces decisions durable enough to survive contact with real program conditions.

The most important thing to understand early is that these industries are fundamentally operational. Whether you are working in EV systems, advanced manufacturing, or robotics-adjacent platforms, the work is constraint management under real conditions — supplier risk, schedule pressure, technical tradeoffs, and cross-functional misalignment. The people who become indispensable are those who can walk into a difficult room with clean data, a clear articulation of the tradeoff, and a credible path forward.

Technical fluency earns you entry. Operational credibility determines your influence.

On the experience of being a woman in these environments specifically: the representation gap remains real, particularly in hardware-intensive sectors. What I have found most effective is not adjusting style to fit what the room expects, but building a consistent track record of being right about things that matter. That kind of credibility transfers across organizations and levels in a way that personality adaptation does not.

The other thing I would emphasize is the value of proactive ownership. Early in my career, I identified a supplier risk that sat in the gap between two functions — neither team claimed it, and it was progressing toward a program impact with no one actively managing it. I began tracking it independently, synthesized the exposure, and brought a structured assessment to the program lead without being asked. What had been an unmanaged vulnerability became a controlled risk. That decision changed how I was perceived on that program for the remainder of the engagement. No one assigned that work to me. But identifying what is falling through the gaps and taking ownership of it — before it is asked for — is one of the most effective ways to build standing in environments where accountability is the currency that matters most.

The professionals who advance fastest in these industries are rarely the most senior in the room. They are the most willing to be accountable for the problems no one else has claimed.

The defining shift in EV, Automotive and Manufacturing-adjacent hardware is the transition from static physical systems to software-dependent platforms. Sensors, compute architecture, and battery management systems increasingly rely on software updates, data pipelines, and predictive intelligence to deliver performance and maintain safety over a product's operational life. That changes the nature of program leadership significantly.

The opportunity is meaningful: you can improve deployed systems without hardware intervention, detect degradation before it becomes failure, and make supply chain decisions with substantially more signal than previous generations of program managers had access to.

The structural tension, however, is considerable. Hardware programs operate on twelve-to-eighteen-month development cycles. Software teams work in two-week sprints. Supply chains require six-to-nine months of committed forecast to maintain capacity. When a component upgrade becomes desirable mid-program — because performance requirements have shifted or a superior option has emerged — those three timelines do not align naturally.

I encountered this directly when an engineering team sought to qualify a new supplier offering improved resolution at equivalent cost. The decision was defensible from a purely technical standpoint. But the supply chain implications of dual-sourcing at that program stage, combined with the software validation effort required to recertify against the new hardware stack, produced a total cost of transition three to four times what the component delta alone suggested. Each function had assessed the decision correctly within its own scope. No single role was accountable for the integrated cost picture across hardware, software, and supply simultaneously.

That structural gap — the absence of program leadership designed to hold cross-domain tradeoffs at the system level — is the core challenge of this moment. Organizations that build that capability will execute through the current transition. Those that don't will continue making locally rational decisions with globally expensive consequences.

Three principles are non-negotiable for me, professionally and personally: integrity, contribution, and growth. They were not arrived at through reflection — they were shaped in high stakes scenarios and cross-functional negotiations, and in the moments where I got each one wrong before I understood what holding it actually required.

Integrity means owning the outcome without adjusting the picture to make it more comfortable. Professionally, that means delivering honest assessments when the news is unwelcome. Personally, it means being the same person in a difficult colleague conversation as in a room full of senior stakeholders. I learned this when I reported program status accurately but incompletely — a program leader made a consequential decision on that incomplete view, I recognized it in the moment, and I did not intervene. The program absorbed the cost. Since then, anyone making a decision that intersects with my work receives my honest read, not a version calibrated for comfort.

Contribution is what gives work meaning beyond delivery. Capability not shared is capability the organization cannot scale. The measure I return to most is a supply chain analyst I worked alongside on an EV program — strong instincts, no room to exercise them. I brought her into supplier escalations and let her lead the analysis. By the end of that program she was presenting risk assessments directly to engineering leadership. That outcome matters more to me than any milestone I personally delivered. The strongest legacies are built through people, not despite them.

Growth, for me, is self-directed and continuous. Working at the boundary of hardware systems and software-defined infrastructure forced me to understand how software teams think about iteration and risk — and that fundamentally changed how I approach program timelines. That shift did not come from a course. It came from staying genuinely curious and treating people in adjacent functions as sources of insight rather than coordination dependencies.

These are not values I hold selectively. They are the thread running through every program I have led, every team I have built, and every relationship that has mattered.