Product / how I work
// the role
Most PM work is the same questions, asked again next quarter, with last quarter's answers lost in someone's notes. The system below is what I built to stop the reset.
// the discipline
That means being close enough to the customer to make real tradeoffs, and disciplined enough to build systems that compound learning over time, instead of starting from scratch every quarter.
// the leverage
AI is infrastructure, not a shortcut. Used well, it dissolves the process overhead that eats a PM's week, freeing time for the work that actually requires a human: judgment.
01 the system
An AI-powered PM workflow that runs a Net Product Value loop. It's Net Present Value, applied to product instead of capital: identify → define → build → measure → iterate → actualize. The discipline: ask "is this still worth it?" at every stage.
Running in Claude Code: a persistent context library (company strategy, stakeholder profiles, PRDs, decisions, live metrics); skills exposed as slash commands that auto-route to relevant context; sub-agents that critique work in parallel from different angles such as engineering, UX, executive, customer, stakeholders; all before anything ships.
+ dozens more
runs on command
02 a day in practice
03 what i bring
This is what daily PM work looks like when you stop treating AI as a chatbot and start treating it as a system you design and orchestrate.
The system is replicable: context library, skills, sub-agents, the loop. The rest of the formula isn't.
The × matters. Zero out any multiplier and the whole thing collapses. Judgment without effort ships nothing. Effort without judgment ships the wrong thing. Both without ownership stall in committee.
Judgment to know which context to maintain and when to override the model. Effort to run the loop deliberately, every day. Ownership to see each decision through to real value. That's what I'd bring on day one.