I started my journey as an automobile enthusiast — engines, torque, the smell of grease, and a dream of landing a job at one of Germany's legendary car companies. That was the plan. Clean. Linear. Mechanical.
Life, of course, had other ideas.
After more research, I found myself heading to Canada instead — broader opportunities, less of a language barrier, and frankly, a little safer than some alternatives. I enrolled in a master's in industrial engineering, drawn to its versatility: lean thinking, eliminate non value added activities, continuous improvement — principles that could live in any industry.
Then, one fine spring day — sunny, a perfect breeze — I walked across campus and noticed her for the first time. Project Management. It wasn't love at first sight. But something caught my attention. I enrolled almost on instinct. The more I got to know her, the more I was captivated — every conversation about timelines, scope, quality, stakeholder alignment, and value delivery felt like discovering a new dimension of the craft. I was completely hooked.
I decided to take things to the next level and pursue a career in PM.
The Rough Patch
Taking our relationship to another level, moving in together — my first PM role — was not all roses. There were thorns. Plenty of them.
Responsibility without authority.
Imagine being told the food must be delicious — but you're not the one cooking. You can't control the heat, the seasoning, the timing. You're just responsible for the outcome. That's a PM. Accountable for value delivery, but the actual work is done by people who don't report to you. For a while, that gap felt impossible to bridge.
No respect from veteran engineers.
Walking into a room of seasoned engineers with no lines of code to your name is humbling. Why should they listen to you? What do you actually know? A fair question — and one I didn't have a good answer to yet.
Stakeholder conflicts.
Everyone has an opinion. Everyone has a priority. In a room full of smart, opinionated people, debates get heated fast. I spent more time than I'd like to admit just keeping people pointed in the same direction.
Shifting priorities.
I was fortunate to work in environments where priorities changed dynamically — fast-moving, high-stakes, never boring. But let's be honest, “dynamic” is a polite word for chaos. One week you have a clear roadmap, the next it's been flipped upside down because of a new executive decision, a market shift, or a client changing their mind — again. And every time, all eyes turn to you. No one asks if you're ready. You just have to be.
What Actually Worked
On influence.
I stopped trying to control the work and started creating conditions for great work to happen. Think of it like this — you can't cook the meal, but you can make sure the best ingredients are sourced, the right utensils are there, the heat is right, and the kitchen isn't on fire. That's the PM's job. Build the environment. Remove the friction. Let the team cook.
On earning respect.
I got my hands dirty. I learned to code. Did testing, deployments, wrote user stories, gathered requirements, ran demos. I touched every piece of the end-to-end value chain — not to become a developer, but to understand the craft deeply enough to be a credible partner. Master of project management, jack of everything else. Honestly? Game changer. I still code as a hobby, for the kicks — especially now with AI making it easier than ever to pick up new technologies.
On shifting priorities.
I stopped treating changing priorities as disruptions and started treating them as data. Every pivot told me something — about stakeholder confidence, market reality, or gaps in our planning. I built flexible frameworks instead of rigid plans, kept buffers visible, and made sure the team always understood the “why” behind every change. When people understand the reason, they adapt faster and resist less. The chaos didn't disappear — I just stopped being surprised by it.
On conflict.
Everything shifted when I learned to distinguish between cognitive conflict and affective conflict. Cognitive conflict — debating ideas — is healthy. Affective conflict — personal tension, ego, frustration — is what kills teams. My job became encouraging the former and quietly defusing the latter. I started reading between the lines. Watching tones. Noticing when someone was hesitating or getting frustrated unusually fast. When I spotted those signs, I didn't wait — I'd pull them into a 1:1 immediately to dig into what was really going on.
Good vibes are contagious. So is low morale. I made it my mission to catch low morale before it spread — and kill it right there.
On communication.
Most problems — conflicts, missed deadlines, shifting priorities — are really just communication failures in disguise. Right message, right people, right time. That became my mantra. I don't believe in over-communication. More is more, as far as I'm concerned.
We don't fight anymore, project management and I. We've figured each other out. Like any relationship worth keeping, the work isn't done — but now we're doing it together, in harmony.
If you're somewhere in the middle of your own rough patch with PM — trust the process. The harmony is worth it.
P.S. — The kid in me never left the garage. My favourite hobby is time on track, and my favourite music? The sound of a V12 at full throttle. Some things don't change.