2025.12 - To prepare for a future with fewer TPMs, we need better ways to measure how close that future is so we can start to figure out what is left for us to do, and hone those aspects.
I think our role will evolve. Not sure if always towards executive leadership, as Casey mentioned in the other comment. I believe that we will be able to run more programs in parallel, and maybe even take on some other functions. (Vibe coding, vibe QAing
..). I can see us as orchestrators across some stages of the program/project development process that now we barely touch. But things are moving so fast that next week I may have a totally different opinion :)
Great forward thinking article. My hope is we don't become obsolete, but get more time to focus on the development of the program (maybe that will just be the executive leadership role though????). I am looking forward to the next article.
I think our role will evolve. Not sure if always towards executive leadership, as Casey mentioned in the other comment. I believe that we will be able to run more programs in parallel, and maybe even take on some other functions. (Vibe coding, vibe QAing
..). I can see us as orchestrators across some stages of the program/project development process that now we barely touch. But things are moving so fast that next week I may have a totally different opinion :)
That is spot on. Even if I wanted to figure out what my role looks like the tech is changing so fast that I need rethink everything.
What I am struggling with is what shape this "orchestration" role will look like.
Great forward thinking article. My hope is we don't become obsolete, but get more time to focus on the development of the program (maybe that will just be the executive leadership role though????). I am looking forward to the next article.
I appreciate the kind words, Casey. Hoping we can figure this out together.