Product notes, takes, and field observations from shipping real things. Written for PMs who build, not those who plan.
AI isn't replacing PMs. It's splitting the role into two very different jobs.
There used to be a comfortable middle in product management. You could build a whole career there. Write clean PRDs. Run a tight sprint process. Be the connective tissue. That middle is compressing.
Most PMs talk about AI workflows. I built one that runs my business.
Five agents, each with a clear role, communicating through files and operating on a shared SQLite database. Running daily cycles while I sleep.
AI didn't make me a developer. It closed the gap between thinking and making.
I used to have ideas I couldn't build. Not because they were bad. Because I didn't have the skills to make them real. That's changed.
If you're managing the product but you're not in the product, you're flying blind with a nice dashboard.
It's like being a raid leader who hasn't logged in since the last expansion. You can read the patch notes. You can study the DPS charts. But when the team wipes on a boss mechanic, you're not going to know why because you haven't felt the fight.
Data doesn't create conviction. Conviction creates the conditions where data becomes useful.
There's a version of product work that looks productive but never goes anywhere. Engine running, no rudder. Lots of noise. No direction.
If you need a complex dashboard to know whether something is working, it probably isn't.
The products that actually matter don't need a twelve-tab analytics setup to prove it. They surface signal on their own. Through behavior. Through pull that nobody had to manufacture.