Exploring the technical toolset

There’s a reason why the T comes before the PM. The technical nature of the position is what differentiates a TPM from a generalist program manager. The area of focus is so deep within technology teams and technology products that specialized knowledge is needed to properly manage projects and programs. To be clear, not all companies actually use the term TPM and continue to use the generalized PM moniker instead. Make no mistake, though—positions that work with technical teams definitely require a technical background. This allows TPMs to dive deeper than just tracking milestones and deliverables, and also ensures that the right solution is being built for both the project and the organization.

As a TPM, you need to have some foundational knowledge in the technology space. We’ll go over the particulars across the industry throughout Part 3 of this book, but in general, that background should afford you some intermediary knowledge...