JohnI’ve been lucky enough to have been interviewed and accepted for a technical program manager (TPM) role at Ford Motor Company for the past six months. I figured it was a good time in my career to progress from software/data engineering to somewhere that I can have more impact. With the TPM role essentially being brand new to me, it was just like starting my first job. Having said that, here’s a few lessons learned about being a TPM.
Be Comfortable with Change
Photo by le vy: https://www.pexels.com/photo/red-and-green-tree-leaves-on-a-sunny-day-668553/
While you don’t necessarily need to be comfortable with change, you at least need to come to grips with the fact that it is omnipresent. Change is going to be encountered in all areas of your work: the software you use, the team you have, the requirements of the project, even your current responsibility and roles.
If you spend your hours complaining about every change that happens in a day, you’ll probably never have any time to do the actual work. Though easier said than done, something that may help is to view through an opportunity lens for each curveball that comes your way. Instead of complaining about what problems change is causing, see it as a chance to make the work or outcome better. This idea might even be mentally healthier for you as well.
Communication Skills
Photo by SevenStorm JUHASZIMRUS: https://www.pexels.com/photo/123-let-s-go-imaginary-text-704767/
Another important thing I learned was that you need to be well-versed in communication. This means utilizing soft skills, being able to provide clarity in ambiguity, and communicating clearly in various channels such as email or instant messaging tools.
Looking back in my career, I’ve worked with individuals that have hardcore opinions in the IT world, but it’s still scoped relatively to IT topics. As a TPM though, I’m working with a litany of different areas such as management, legal, and people from all over the world. These are people from completely different cultures, backgrounds, and may have personal issues I’m not aware of. You can imagine the differences of lingo, energy, and formalities in meetings. Boil it down, being good at talking or writing with anyone is vital to keep conversations efficient and productive.
It’s All About Systems
Photo by Aleksejs Bergmanis: https://www.pexels.com/photo/aerial-photo-of-buildings-and-roads-681335/
And to help manage the constant state of change and ensure everyone stays aligned, I believe it comes down to systems. I found if you don’t develop systems, it can be exhausting to work in a reactive state. One key thing about successful systems though is that they need to be updated as projects mature. They can be great one day, but if you don’t adapt, you’ll find gaps start to form in the work.
Conclusion
After writing this, I thought about another topic I should touch on, and that is to ask for help. I know damn well I’m just starting out in this role, and I have no idea what I’m doing. I’m learning on the job as they say and it’s imperative for me to learn as much and as fast as I can. With that being said, I’m looking forward to all the experiences and learning lessons coming my way.
Thanks for reading!