Leadership is a lifelong practice. You can start from anywhere. The only requirement is that you start.

I came to Lakshmi at a point where I was managing a team of forty but felt like I was running on instinct with no real system underneath. We spent time building what he called a leadership operating system — how I was making decisions, how I was distributing context, how I was handling the things I kept deferring. It was uncomfortable because it made the invisible visible.

I now run a team of ninety with less friction than I had with forty. The work we did together did not give me more hours — it gave me a different relationship with the ones I had. I think about my role differently, my team differently, and my own limits differently.

I was a network engineer wanting to move into cybersecurity leadership but had no idea how to make the case for myself. Lakshmi helped me map my existing experience onto the new domain — not by rewriting my story but by helping me see the story that was already there. We also worked on how I was communicating with senior stakeholders, which was the real gap.

I landed a security architecture role within four months of our conversations ending. More than the role, I came away with a framework for how to think about career moves — not as leaps but as systems. That thinking has guided every decision since.

I was a senior engineer who had been passed over for a team lead role twice. Lakshmi helped me understand why — not as a skills gap, but as a systems gap. We worked through how I was showing up in meetings, how I was handling conflict, and how I was thinking about my team's output versus my own. He did not tell me what to do. He asked questions until I could see it myself.

Within six months I was leading a team of eight. What changed was not my technical ability — that was never the problem. What changed was how I thought about my role. I stopped being the best engineer in the room and started being responsible for the room. That shift came directly from the conversations we had.

I was preparing for senior architect interviews and kept failing at the system design rounds — not because I did not know the answers but because I was answering the wrong question. Lakshmi helped me understand what interviewers are actually looking for at that level. We ran through several mock sessions and he would stop me mid-answer and ask why I made a particular choice. That discipline changed everything.

I cleared the next three interviews I appeared for. But the more lasting thing was that the habit of asking why before how stayed with me. It made me a better architect and a better explainer of my own thinking.

Fresh out of college and struggling with the gap between academic knowledge and production engineering. Lakshmi ran a workshop I attended and then spent individual time with three of us who asked follow-up questions. He pointed me to the right resources, pushed me to write about what I was learning, and told me very plainly where my thinking was shallow.

That early push shaped the way I approach mastery. Twelve years later I still write about what I learn. I still go back to first principles when something does not make sense. I still think about the systems underneath the tools. That came from those early conversations.