Notes & essays
AI is leverage, not authorship
How I use AI collaborators while keeping human judgment explicit.
AI can accelerate the work. It should not erase the human responsibilities that make product work trustworthy.
AI can compress the distance between thought and artifact. That is the leverage. But it does not remove authorship, judgment, or responsibility. In practice, it makes those things more important because more can be produced before anyone has checked whether it is right.
My approach is to make the human-owned parts explicit: the problem, the taste, the constraints, the review criteria, the risk boundary, the verification, and the final claim. AI helps produce drafts, code, tests, alternatives, and synthesis. The product judgment stays accountable.
The working sequence
Give AI bounded jobs.
AI is strongest when the task has context, constraints, expected output, and review criteria.
Treat output as a draft until tested.
Generated code, copy, strategy, and analysis need review against source truth and product intent.
Keep final claims human.
The human owns what is shipped, what is claimed, what risk is accepted, and what remains uncertain.
Leverage increases responsibility.
The faster I can move from idea to artifact, the more important it becomes to know which artifact matters, what quality bar applies, and what evidence is enough.
Across the projects, the strongest moments are not only the things that shipped. They are the decisions to analyze before implementing, revert a plausible but wrong migration, pause a risky commerce expansion, and turn repeated issues into shared rules.
AI makes output cheap. Product leadership decides which outputs deserve to become product reality.
AI should make product judgment more visible, not less.
The best AI-assisted workflow leaves behind briefs, acceptance criteria, review notes, validation checks, and launch decisions. Those artifacts make the work inspectable.
The public version of this is claim discipline. It is stronger to say that I led framing, prioritization, experience design, acceptance criteria, release decisions, and AI-assisted execution than to imply the model independently built or validated the product.
The operating model makes delegated work legible: Sketch defines why to build, Helm directs the agents, Iterate creates evidence, Perfect governs launch readiness, and Operate keeps learning after release.
Seen in the work
Trust-heavy nonprofit operations
Public fundraising, supporter records, organization controls, payments, certificates, content operations, and launch gates in one system.
Knowledge architecture and source-faithful systems
Searchable strategy corpus, model articles, semantic visuals, templates, protected resources, and editorial QA workflows.
Evidence-grade compensation decisions
Sensitive compensation workflows, compliance framing, source grounding, reviewer decisions, and human-in-loop AI boundaries.
Creative output as a product surface
Generative artwork, poster editors, saved libraries, export readiness, checkout paths, and output-quality judgment.