Years in Product
CPO & VP Experience
Banks assume variable means unpredictable. It doesn't. These workers know exactly what a Friday night shift earns.
Mapped 14 user journey scenarios before writing a line of AI code: happy paths, edge cases, adversarial inputs. Built an 800-line prompt architecture with hard constraints and context injection. The AI does things (logs earnings, creates paydays), not just talks. 7-tool agentic system with LLM-as-judge evals.
Two years of spinning. Nothing shipped. Team had lost confidence and the product had no clear path to market.
Cut the contractor team by half and brought in laser-focused senior engineers. Realigned the org around one pursuit: PMF. Migrated from Jira to Linear for a fresh start and killed six months of stale backlog. Skipped PRDs entirely. Prototyped in Replit to align stakeholders, define data structures with engineers, and build the first design system. Designer only touched UX gaps the prototype couldn't solve.
No product function. Stalled releases. Burn too high. Product and engineering disconnected from business strategy.
Replaced contractors who'd over-engineered for scale they didn't have. Brought in senior engineers to fix a stalled data migration. Trained a services-culture org on iterative product development. Shipping went from stalled to weekly.
EMR platform was failing with providers, feature velocity was slow, and the product team lacked clear direction.
Embedded in the OR to study clinician workflow. Discovered EMRs were built for billing, not diagnosis. Built clickable iPad prototypes and ran usability tests with each clinician before writing code. Redesigned around real-time clinical signals that drive treatment decisions.
I build tools that solve problems I hit repeatedly. These are public because other PMs who code run into the same friction.
Claude Code plugin. Strategic sparring partner that challenges assumptions and pushes toward prototypes over documentation. Integrates Linear and GitHub via MCP.
View on GitHub
Quality standards for PMs who code with AI. Ship responsibly. Match team patterns. Don't leave messes for engineers to clean up.
View on GitHub
3 Super Bowl Campaigns · Shipped Production Code · JD, Colorado Bar
My career happened in thirds.
First, marketing. DTC brands like Oakley, North Face, and Beats by Dre. Three Super Bowl campaigns with Audi. These weren't just advertising. We had engineering teams building software for these brands.
Then I learned to code. Took a detour to Turing School because I wanted to understand how things actually get built. Founded the Denver chapter of Girl Develop It and taught women to code on weekends.
Marketing foundation plus shipping production code led to product. I've been doing product since before it became the discipline it is today.
I'm the one you call when turnarounds need to happen and shit needs to get done. Startups, Fortune 500s, stalled products, scaling teams. I've done it across verticals.
Engineers want to work with me. I speak their language, understand their constraints, make tough calls, and protect their focus. I build products WITH my team, not just for them.
I don't rely on assumptions. I study what people actually do. User empathy isn't a phase of the project. It's how I think.
My undergrad was art studio. I painted and drew my way through college. Then law school. Passed the Colorado bar. That breadth made me dangerous: creative thinking, critical thinking, logical reasoning.
I don't write memos nobody reads. I build. I ship. I iterate.
"For years, the design-eng-product dynamic got predictable. AI made it weird again. I'm here for it."
Agentic prototypes (RAG, tool calling), evaluation frameworks
LLM evaluation pipelines, LLM-as-judge, CI/CD integration