Lead Product Manager · Digital Commerce

I ship experiences that move conversion, not just features.

Lead PM owning the digital roadmap for two national retail brands across web and native app, from search & discovery to checkout to personalization. I run a test-and-learn practice where every experience I ship is measured, and the lift is the point.

+6.3%
CVR · shipped filter test
+59%
CVR · AI agent exposure
5M+
users reached / experience
2
national brands · web + app
01

Selected experiences

Quick Filters on product listing pages
Search & Discovery · Shipped

The problem: Shoppers on product listing pages struggled to narrow large catalogs and dropped before they ever reached a product. The most-used filters were buried behind an extra tap that pulled people out of the browsing journey, so they went unused.

+9.1%
CVR of sessions users filtered
+8.1%
Rev / session
500K+
sessions in split test
5M+
sessions engaged, shipped to date
Approach

Started as a one-tap quick-filter surface placed directly in the listing flow and proved out through a controlled split test on the highest-traffic categories, so the read would be fast and decisive. The validated concept then graduated into a permanent, self-tuning capability, scaled across hundreds of PLPs.

Result

Clear conversion and revenue-per-session lift in test, exposed to 500K+ sessions, then shipped and engaged with by 5M+ sessions to date. What began as a single experiment is now a durable surface that keeps the most-used filters What began as a single experiment is now a durable surface that keeps the most-used filters in the browsing journey instead of buried a tap away.

Technical How

To make the surface self-tuning rather than hand-curated, I worked cross-functionally with IT to build a data flow that takes standard site-filter engagement data, pipes it into a Google Cloud project, and feeds it back into Algolia as a dedicated index. That index dynamically populates each PLP's most-engaged standard filters as quick filters, so the surface adapts over time to what shoppers actually use, at scale, without manual upkeep.

AI Shopping Agent — Conversational Commerce, Powered by Google
AI Discovery · Shipped & Scaling

A storefront that talks back. I owned the rollout and monitoring of a high-scale conversational shopping agent, built on Google's largest LLMs, that handles product discovery, side-by-side comparison, customer care, and add-to-cart inside one contextually aware surface. The mandate: prove customers want it, then find where to put it.

+59%
CVR · users who opened vs. control
+15%
add-to-bag rate · AI-prompted vs. control
2M+
sessions exposed to contextual PDP prompts
Approach

Owned and monitored a controlled rollout of the agent at scale, synthesizing the experience data for both internal leadership and Google as the external partner. I went deep on the conversational sessions themselves, reading real exchanges to understand what customers came to the agent to do, and where it delivered.

Result

The signal was clear: customers who engaged converted and added to bag at materially higher rates, confirming strong receptivity to the experience. Initial entry-point visibility landed at the industry benchmark for a net-new surface: enough to validate demand, and enough to tell us the next unlock was discoverability, which set up Phase 2: contextually aware prompts placed where intent already lives.

Technical How

Phase 2 moved the agent from a single entry point to contextually aware PDP prompts, surfacing the assistant at the moments a shopper is already weighing a product, comparing options, or looking for an answer. Given the conversion and add-to-bag lift among users who open it, the program is now scaling into new global elements and surfaces, expanding where the agent meets the customer rather than waiting for the customer to find it.

Exposed search in mobile navigation
Navigation · Shipped (one brand)

The problem: Search was hidden behind a tap in the mobile nav. I tested surfacing it directly, and the right call was to read the two brands separately and split the decision rather than ship or kill across the board.

+4.2%
Unique CVR · shipped brand
Hold
2nd brand · diagnosing
Kill
variant 2 · no lift
Approach

A/B tested an always-visible search field in the mobile nav across both brands, with two variants. I read results per-brand and per-variant rather than in aggregate, because aggregate would have masked a real divergence.

Result

One brand showed a statistically significant unique-conversion lift, a clear ship. The second brand showed an add-to-bag decline at high significance, which I would not ignore for the sake of a clean launch. Variant 2 showed no lift on either brand.

What's next

Shipped the winner, killed variant 2, and held the second brand pending a session-replay investigation into why the add-to-bag metric moved. Holding to diagnose is a decision, not indecision.

Experimentation architecture redesign
Platform · Strategy

The problem: Our personalization tool was rendering directly on transaction-critical surfaces, including checkout, putting marketer velocity and revenue-path stability in tension. I redesigned the model to resolve that tension instead of trading one for the other.

PRD + diagram
delivered
0
tooling on checkout-critical render
MVP-first
test-and-learn model
Approach

Designed a model where engineering owns the actual rendering on critical surfaces and the personalization platform operates only as a server-side allocation and measurement relay, passing results to analytics. Documented it as a PRD with a bow-tie process diagram so engineering, marketing, and analytics shared one source of truth.

Result

Removes the third-party tool from the transaction-critical render path while preserving the ability to allocate and measure tests. Marketers keep their experimentation surface, engineering keeps control of checkout stability.

What's next

Rolling the model out MVP-first, proving it on a contained surface before generalizing. The principle: experimentation infrastructure should never be a single point of failure on the path to revenue.

02

How I work

I run product like an experimentation program, but what I ship are experiences. Every initiative starts with a hypothesis tied to a behavioral signal, gets sized against revenue impact and build effort, and ships as the smallest version that can prove or kill the idea.

I read results per-segment and per-brand, not in aggregate, because that's where the real decision lives. A win on one brand and a regression on another isn't a wash; it's two different ships. I'm comfortable killing my own ideas when the data says so, and equally comfortable holding a launch to diagnose why a metric moved before reacting.

I work close to the stack. I write the PRD, scope the Jira ticket, design the measurement framework, and sit with engineering on the architecture, so the test that ships is the test we can actually trust.

The loop

Hypothesis Size & prioritize Smallest viable test Measure per-segment Ship / hold / kill Scale to platform
03

Stack fluency

Search, personalization & experimentation

AlgoliaDynamic YieldLaunchDarklyFirebase A/BFullStory

Commerce & content

commercetoolsAmplienceStylitics

Data & analytics

GA4BigQueryLooker

Lifecycle

BrazeAttentive
04

Experience

JD Finish Line logo
JD Finish Line, North America Boulder, CO · Sept 2024 – Present
Lead Product Manager, Digital Ops
Aug 2025 – Present
  • Own digital product strategy and quarterly roadmap prioritization as Product Owner for the Digital Operations team, managing a backlog of commerce-driving initiatives — cross-banner BOPIS, checkout optimization, dynamic search reranking, redirect experiences, and third-party payment provider offerings — and coordinating feature delivery across a $100M+ eCommerce platform to lift conversion and deepen customer retention.
  • Orchestrate cross-functional delivery as the primary liaison between IT product managers, business stakeholders, the VP of Digital, and vendor partners, translating business objectives into technical requirements, holding timelines and stakeholder alignment, and surfacing status and risk to senior leadership before it becomes a problem.
  • Run the experimentation and personalization program end to end, overseeing A/B testing through Dynamic Yield and synthesizing insight across leadership, partnership, and IT teams to graduate high-performing experiences into production code and de-risk feature-development decisions.
Senior Consultant, Web Analytics
Sept 2024 – July 2025
  • Supported a large-scale enterprise site migration as analytics lead, implementing dataLayer and API-based tracking frameworks and overseeing marketing-platform integrations while ensuring accurate data interplay between search, content, and order-management systems across every endpoint.
  • Partnered closely with IT, business stakeholders, and enterprise data services to coordinate event tracking, data pipelines, and downstream reporting — keeping KPI measurement and activation intact and dependable throughout the migration.
Adswerve logo
Adswerve Denver, CO · Nov 2021 – Aug 2024
Analytics Consultant, Enterprise
Nov 2021 – Aug 2024
  • Led full-lifecycle enterprise analytics engagements for major eCommerce clients — site audits, data-model architecture, dataLayer design, implementation, and pre-launch QA — to deliver accurate, scalable events data.
  • Identified and executed growth opportunities inside existing accounts, pitching advanced measurement capabilities and driving more than $500K in incremental services revenue through strategic analytics expansions.
  • Directed a cross-functional team of 12 developers to deliver GA4 dataLayer implementation across three multi-regional eCommerce sites, establishing robust event frameworks and advancing enterprise reporting maturity.
Fusion92 logo
Fusion92 Chicago, IL · Mar 2021 – Nov 2021
Analyst, Digital Investment
Mar 2021 – Nov 2021
  • Forecasted and recommended monthly media spend for client portfolios ($50–75K budgets) across programmatic, CTV, and third-party digital channels, using Excel and Datorama to inform strategic investment decisions.
Refinitiv logo
London Stock Exchange Group, Refinitiv Chicago, IL · Jun 2020 – Jan 2021
Product Specialist, Quantitative Analytics
Jun 2020 – Jan 2021
  • Built and troubleshot T-SQL database queries powering clients' quantitative trading models, integrating 50+ financial and alternative datasets, and led product demos that opened upsell opportunities.

Let's talk product.

Email me LinkedIn