Discussion about this post

User's avatar
Dan Gronsbell's avatar

This post is hitting on something that I see too few Product-focused people discussing. Instead of looking at this like a 'factory,' they only see one station. Said differently, instead of looking at each step of the journey, and determining how to improve speed, cost, and quality, they pick out one area, one tool. In many cases, they get frustrated as some of these are in their infancy. An example is video creation. Tools like Runway, and one of my favorites, Google's VEO, have made leaps forward, but still cause the user to have frustration to odd hallucinations even with skilled prompting. This doesn't mean give up on them; they will continue to improve. Additionally, one can use them to get farther down the automation field even if it doesn't get you there fully today. One of the best books I read in college is The Goal. In it, the main character is faced with figuring out how to improve his manufacturing facility. He fixes one thing and something else becomes the bottleneck. Leveraging AI helps to alleviate bottlenecks in order to increase throughput -- more features that customers care about and truly enabling Product-Led Growth.

This is a GREAT topic and there is so much that can be said. I will make two other points that have shown much value in my work:

1) Using training agents, strung together agentically, to look over what is produced and move things through workflow stages. In regards to my 'factory' point above, these agents would be your quality control team as widgets are being made in the factory. Production is important, but one of the comments I see a lot is about gaining speed with tools, such as IDEs, but then having to have a lot of clean up done by humans. AI is getting better at the clean up too, but agents also serve as a great solution in areas outside of one's codebase. For example, with innovation management, agents can be very, very helpful in reviewing AI-generated research (e.g., custom research GPTs) to look for certain things (i.e., quality control), and can push requests back to the GPT to do further work/refinement. Then one it passes human review, move on to using agents to populate lightweight frameworks (templates) such as a competitor and lean model canvas, to save the human some time. There are numerous other steps in a good innovation process as the journey from Product-Solution and Product-Market-Fit take shape, and agents can be helpful in saving time and cost.

2) Alleviating capacity constraints. Typically, Product can become frustrated if they are faced with capacity shortages with shared services such as Engineering and Marketing. They become the bottlenecks. AI tools can help in two ways. First, they can help other functions, whether shared or not, increase production (e.g., produce more quality marketing content, faster). Second, Product can pull in more of the workload 'in house.' For example, using a tool like Magic Patterns for UX prototyping and then import the code into a front end tool like v0. The front end code, which can be React or numerous others, can be imported into Jira and ingested directly into an IDE. So instead of Dev having to do the front end, Product can do it. Depending on the company's security/IT policies, POCs can be launched from Product without going through Dev to at least ship a product early and get feedback. Iterations can be handled by Product, and once it is ready for a true production release, it can go to Dev. The main point being that there are only so many cycles in a year and Product always wants more -- AI tools are making it possible to produce more, in less time, at a lower delivery cost.

Expand full comment

No posts

Ready for more?