The only PM blog written by someone who still ships code every week. Failed experiments included. Agent recipes you can fork.
A decision log template for PMs: schema, worked examples, the weekly 10-minute ritual, and the quarterly calibration review. Markdown and Excel.

I replaced weekly staff meeting status updates with a live agent-built dashboard. What it killed, what it surfaced, and the one mistake I would not repeat.
Month three for a new CPO: build the kill list with the inertia test, kill two things publicly, size 2-3 first bets, and write the SCQA day-90 readout.

Founder mode got read as permission to micromanage. The real lesson: stay close to the few decisions only you can make, automate the rest.
PM days 31 to 60 in a new job: skip the quick win, ship one compounding artifact. Four options, selection criteria, a worked example, and the failure modes.
A 7-slide board product section in 10 minutes: scoreboard, what changed, bets table, kill list, the one risk, and asks. No feature parade. Templates inside.
The AI product operating model diagnosis is right. The evidence is every company that lived. Survivorship bias makes a true claim look far more proven.
I crossed ~$1.5M ARR solo in under two months. It only works because I built agentic engineering, not vibe coding. The substrate does the carrying.

Speed is free now. The binding constraint for CPOs is reversibility: ship cheap-to-undo decisions instantly, slow down deliberately on the ones you cannot undo.
Speed to demo is a vanity metric. The 'I built it in a weekend' flex measures the cheapest, least durable thing. Ask if it was still running the weekend after.
Most decision frameworks quietly price building as scarce. When AI makes building cheap, four of them invert and start giving the wrong answer.
Google's vibe coding whitepaper drew the cost curve I've bet Falkster on. Vibe coding isn't wrong, it's a loan, and the interest comes due at the crossover.
A six-page SCQA strategy memo template after Minto: answer first, three grouped arguments with evidence slots, anti-bets, premortem risks, and the ask.

Most executive product reviews are status theater. Five questions convert them into decision-forcing sessions that surface judgment, cost, and risk.
Month two for a new CPO: stand up three instruments, build the coalition map, ship one visible decision, and renegotiate the scoreboard with your CEO.
Four templates for a PM's first 90 days: a one-page manager contract, signal map, decision archaeology worksheet, and the day-90 note. Fill in 10 minutes.
First 30 days as a PM in a new job: run decision archaeology, build a signal map of where truth enters the building, and write the manager contract.
Paweł Huryn's PM Skills 2.0 review: which of the 68 Claude skills to install (red-team-prd, ship-check) and which half embalms a dying PM role.