John Cutler reflects on his early product career, when a single product manager bundled research, analysis, design sketching, requirements writing, release coordination, support, and even coding into one role. He notes that some of this bundling was empowering while some was amateurish, but that it all sat under the loose label of product management. The piece frames the bundling and unbundling of capabilities as a recurring pattern in how product work is organized. The excerpt provided is only the opening paragraph, so the full argument about how AI affects this unbundling is not visible here.
01Key takeaways
- Product management has historically bundled many distinct capabilities under one loose label.
- Breadth of responsibility can empower practitioners but may also lead to shallow execution in specialized areas.
- Recognizing which capabilities are bundled helps teams decide what to keep, split out, or hand to specialists.
- Capability bundling should be evaluated deliberately rather than inherited by default.
02Key sections
- The generalist product role
- Cutler describes how early on he took on research, data work, design, requirements, releases, support, and some coding. He frames this as a single loosely defined job.
- Empowering versus amateur
- He admits that the breadth was sometimes empowering and sometimes produced weak work. The mix of strength and immaturity is central to the reflection.
03From the post
“Early in my product career, I wore many hats. I conducted research, analyzed data, sketched interfaces and wireframes, wrote requirements, coordinated releases, answered support questions, and even, shudder, wrote some code. Some of that was empowering. Some of it was amateur hour. But it was all bundled into the loose idea of “product management.””
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.