AI Won't Replace TPMs, But It Will Redefine the Role

I joined Leena Agarwal on the Agentic AI Execution podcast for an episode titled “AI Won't Replace TPMs, But It Will Redefine the Role.”

We spent most of the time on the parts of the job that do not show up in a job description. Owning outcomes you cannot command. Deciding what not to track. Knowing when a status update is a signal and when it is theatre. And the specific way AI infrastructure work breaks the usual planning assumptions: capacity that has to be forecast quarters ahead, models that iterate faster than the platform under them, and reliability targets that only mean something if you can say what you gave up to hit them.

On the title question: the parts of the role that automate well are the parts that were never the job. Status collection, dependency chasing, meeting notes, first-draft plans – all of that is going. What is left is judgement under ambiguity, and the willingness to be the person who says the date has moved. AI makes that residue a larger share of the role, not a smaller one.

If you are moving into a TPM role from engineering or from project management, the middle section on influence without authority is the part worth your time.