AI PMs Should Start With the Workflow, Not the Model
A practical case for defining the user workflow, decision, and operating constraint before choosing a model, agent, or automation pattern.
Insights
These pieces show how I frame AI product problems in public: start with the workflow, understand the consequence of a wrong action, and treat production behavior as part of product design. Each featured item links directly to the original source.
Featured
A practical case for defining the user workflow, decision, and operating constraint before choosing a model, agent, or automation pattern.
Moves the failure analysis beyond model quality and into the surrounding system: validation, execution, traceability, and the action that follows an output.
Selected writing
The common thread is practical rather than ideological: what should the product do next, and how should that behavior be measured?
June 4, 2026
Connects model behavior to product mechanics such as review, escalation, runtime controls, auditability, and operating metrics.
May 28, 2026
Argues for risk-based review at specific control points instead of putting a person in every loop or automating everything by default.
May 21, 2026
Explains why a plausible model response still needs action-specific validation once the output can change production state or business workflow.
Case study
ReplayGuard combines an issued patent, public implementation, browser-local evaluation, technical limitations, and commercialization material in one place. It is the strongest current example of the product argument and the underlying implementation living together.
Open ReplayGuard →