I am not an engineer, I can't look at code and determine if it is good, performant, or elegant. However, I can look at designs and make a judgement. I'm curious to see how Claude Design changes how I think about AI and its capabilities.
I don’t think this is a spicy take at all. A PM’s job is to prioritise, and the most important/high priority projects will naturally be handled by Engineers enabled with AI-coding workflows. The high priority/impact work should be allocated to the folks with the highest level of skill.
I feel like PMs coding unlocks a whole new category of work, mainly addressing the long tail of cool ideas/small optimisations that ordinarily would not be addressed. Time will tell how valuable these items are in the long term.
I have been working on a web app called Beval - Simple evaluations for your AI product.
In my day to day as a Product Manager working in a team that ships AI products, I often found myself wanting to do 'quick and dirty' LLM based evaluation on conversation transcripts and traces. I found myself blocked by 'Gemini in Google Sheets', it was too slow and cumbersome, and it didn't handle eval changes well. And because I was exploring, it wasn't helpful to try and set up something more robust with the team.
To fix the problem I eventually learned to call the OpenAI API in python, but I really felt that I wanted a 'product' to help me and potentially help others.
Personally I find this kind of approach infantilizing. I don't think it's fair to have an expectation of yourself or of your colleagues to spell out in Google Calendar what you/they are spending their time doing throughout the day. People should look at gaps in people's diaries not as opportunities for new meetings, but as time someone is probably spending doing something important or interesting.
Honestly, I'd suggest a prioritsation matrix here.
Classify all the tasks with an impact / ease score from 0-5. Multiply the numbers together to understand the relative priority of each item.
It won't be perfect but it will a good place to start.
You also do this at a product level instead, and invest all your time onto one product to begin with. This might reduce your switching costs working between projects/products.
Very true.