My son was only 40 days old when I boarded a plane to London.
I left my family behind in Pune because a critical project was in "dark red." The stakes were massive: if we didn't turn it around, we risked losing the project entirely.
I walked into the first stakeholder meeting ready to work. But when the onsite Project Manager introduced me as the new lead, the room went silent. The stakeholders looked at me, then back at the PM, and asked: "Are you sure? He is just a kid."
I can't blame them. I was young. I was replacing senior resources who hadn't met expectations. And to make matters worse, the outgoing lead refused to give me a handover — protesting that if someone with her experience couldn't do this job, the company was making a mistake sending me.
I could have crumbled. I could have let Imposter Syndrome win.
Instead, I went back to basics.
What I actually did
I listened. I didn't pretend to know the answers. Every meeting I attended, I said nothing until I understood what was being said. I asked questions — even the ones that felt "too basic."
I documented. If I did a task once, I wrote it down so I'd never have to relearn it. That documentation later became the training material for the offshore team.
I automated. I ignored the manual drudgery and built scripts and utilities to do the heavy lifting, freeing myself to focus on the things that actually needed human judgment.
In less than two weeks, we ticked a box on the project plan that had been stuck for months. A few months later, we were no longer in the red.
The lesson
The biggest thing I learned that year wasn't technical. It was this:
Skills matter more than labels.
You don't need grey hair to lead a transformation. You need a learning mindset, the grit to document the chaos, and the courage to automate yourself out of a job.
To anyone feeling "too junior" for the challenge in front of them — if you can solve the problem, you belong in the room.