A template for everything
When I first became a product manager during the dot-com boom, the field was still fairly new. Everyone joked that every barista was becoming a PM, but I felt well qualified and excited for the opportunity. I had business and technology degrees, plus internships and school projects in entrepreneurship that prepared me to work between engineering, design, finance, support, sales, legal, and customer teams.
As I learned on the job, I threw myself into mastering the craft. I read every product management book I could find. I took certificate programs in UX design and web application development. And I built a big collection of templates and starter guides that could handle nearly any request: Product Requirements Documents, technical specifications, database schemas, user research studies, press releases, Agile epics and stories, Jobs-to-be-Done analyses. I thought I was ready for anything.
As my career went on, I saw that the best documentation wasn't solving our biggest problem. Things were changing every few years and demanding completely new approaches to products, services, technologies, form factors, and user interactions. Regulations were reshaping whole industries. New inventions were making entirely new business models possible.
I didn't want my job to be documenting a steady stream of feature requests that only ever came from one direction. If I really wanted to help the business adapt, I needed different capabilities.
So I started studying innovation management, creativity management, and change management. I worked on organizational awareness, so that I could pitch entirely new business models, different ways of running operations, and fresh ways to plan strategy and tactics, and not just suggest good features.
PMs can help companies change course. Most never get the chance, because leaders don't know what they don't know. They don't realize they can ask a PM to do scenario analysis, empowerment consulting, or strategic facilitation.
That's when I understood where the career opportunity was. Getting better at traditional PM tasks would only take me so far. What I needed was to earn the authority to anticipate the big changes coming at a company, plan for them, and maybe even save it from one.
What AI can't pick up from my old templates
AI can already write requirements documents, analyze user data, and generate project plans. My template collection was an early version of what AI now does better and faster. If I'd stayed on that path, my whole professional toolkit would be automatable today.
The scenario planning and change management work is what protected my career. When I learned to draft several possible futures for a product and build strategies that held up across different outcomes, I was building a skill that tools can't copy. It takes judgment about situations nobody has seen before, and pattern-matching on historical data doesn't get you there.
The organizational skills worked the same way. Learning to pitch entirely new business models meant learning to read a room, build coalitions, and help other people make better decisions. I stopped being the PM who produced the best documents and became the PM teams called for the hard pivots. Moving from documenting decisions to helping people make them is what separates a career that can be automated from one that can't.
Looking back, the capabilities that matter most fit a pattern. Strategic foresight lets you see around corners, the way I eventually learned to see the shifts coming in my own career. Empowerment means helping teams make better decisions so you aren't making all of them yourself. Community building is the cross-functional alliances and stakeholder alignment that no solo practitioner can replace. Facilitation turns conflicting perspectives into good decisions through structured conversation.
None of those show up in a template library, and none of them can be automated. They get more valuable as tools take over the tactical work.
Advice for the younger me
If I could go back and talk to the version of me who was proudly building that template collection, I'd tell him to spend less time on the tools of the day and more on the judgment to know when everything needs to change, plus the organizational skills to help make the change happen.
The PMs I'd bet on over the next five years aren't the ones with the best prompts or the most polished specs. I'd bet on the ones leaders already call when a big shift arrives and nobody knows what to do next.