- How I solve problems
- I start by turning ambiguity into explicit constraints, metrics, and a testable workflow. I build small, instrumented prototypes, define eval criteria (binary safety checks plus graded quality), and iterate using real usage signals. I debug by tracing data and decision paths end to end, then tightening grounding, templates, and guardrails to reduce variance while keeping latency and cost predictable.
- How I work with teams
- I collaborate by creating shared artifacts that let teams move together: crisp PRDs, decision logs, eval rubrics, rollout plans, and clear ownership. I thrive in cross-functional settings and can coordinate large dependency graphs without breaking changes. I like tight feedback loops with design and engineering, and I mentor by giving people frameworks, examples, and review checkpoints that raise quality without slowing delivery.
- How I communicate
- I communicate with structured, audit-friendly documentation: goals, constraints, success metrics, risks, and next steps. I explain complex systems by mapping inputs, tools, outputs, and human checkpoints in plain language, then adding technical detail only where needed. I favor decision-ready writing like opportunity briefs and PRDs that connect customer pain, measurable impact, and delivery sequencing.
- My product instincts
- I design for real operators, not demos. I bias toward workflows that reduce time-to-value, minimize cognitive load, and make compliance and quality visible. I integrate feedback through measurable pilots and instrumentation, then refine UX and guardrails based on where users stall or lose trust. I make deliberate tradeoffs like strict templating when reliability and adoption matter more than flexibility.
- What drives me
- I’m driven by building systems people can rely on in high-stakes environments. I like turning messy, under-documented reality into products that feel simple, safe, and usable. I’m motivated by shipping, learning fast, and seeing workflows move from manual and error-prone to measurable and repeatable.
- How I learn and grow
- I learn by building: I pick a real workflow, implement it end to end, instrument it, and pressure-test it with eval sets and governance constraints. Recently I’ve gone deep on conversational agents, evaluation at scale, cost controls, entitlements, and tool-grounded workflows across enterprise systems. I also actively learn by partnering with domain experts and codifying their rules into product constraints.
- Work style and values
- I thrive on teams that are curious, direct, and outcome-driven, where quality and governance are taken seriously. I value high ownership, clear decision-making, and fast iteration with accountability. I prefer environments where product, engineering, and stakeholders work as one system, and where we talk openly about tradeoffs, risks, and what the data is actually saying.
- Initiative and agency
- I routinely identify leverage points where automation or better workflows unlock disproportionate impact, then build the pilot plan and artifacts to make it real. I’ve led 0→1 platform builds to pilot-ready, created governance and evaluation systems for internal agents, and built pro-bono workflows to prove hands-on capability. I look for opportunities where trust, cost, and reliability are the real product.
- Core strengths
- I ship governed, measurable systems. I led a loyalty rollout reaching ~5M members in ~18 months and coordinated delivery across ~20 enterprise teams. I reduced a monthly store audit workflow from ~10 hours to ~5 minutes for ~600 leaders via Copilot automation. I built an n8n pipeline that compressed PM scoping from weeks to 2–3 days. I fine-tuned a BERT classifier on ~40k tickets to 95% human acceptance and automated routing and documentation.
- What I'm looking for
- I’m looking for a senior PM role owning conversational AI products, preferably voice, where the work is real enterprise deployment: integrations, governance, evaluation, and adoption. I want to lead teams building agent systems that are safe, instrumented, and cost-bounded, and to drive products from pilot through scale in environments where trust, compliance, and measurable outcomes matter.