About | Ben Wyndham

How I Got Here

My foundation is operations. I spent my first two years at Backcountry working inside a retail program that was still being built in real time, surrounded by systems that were still taking shape. That proximity to early-stage operational problems turned out to be formative. I found myself troubleshooting retail systems, defining requirements, and shaping how processes should work before I had a title that reflected any of that.

That's when I realized I was doing product work and wanted to keep doing it.

The move into product in 2023 was a natural extension of work I was already doing. I focused on the fundamentals first: inventory and transaction accuracy in our ERP and OMS systems, the kind of unglamorous data integrity work that everything else depends on. I also led payments modernization, introducing Apple Pay and buy-now-pay-later options across the checkout experience.

The promotion to Senior PM in early 2025 brought a new domain in PIM and merchandising systems and a shift toward portfolio-level thinking. I took on larger bets: building Backcountry's dropship program from zero to a $20M+ revenue channel, expanding into marketplace channels with a repeatable integration framework designed to onboard new channels without starting from scratch each time, and most recently developing an internal automation platform and acquisition integration framework that define how we scale tooling and onboard new brands across the portfolio. Designing something once that works ten times is the job I want to be doing.

How I Work

Systems first.

I try to understand the whole system before proposing changes to any part of it. Enterprise software is deeply interdependent, and the second-order effects of product decisions often matter more than the first.

Abstractions over instances.

I look for the pattern underneath the problem. A good solution to one integration failure is a fix; a good abstraction is a framework that handles the next ten. That instinct shapes how I scope work and where I invest engineering effort.

Engineering is a design partner.

I bring engineers into problem definition, not just solution delivery. The best technical decisions I've made came from that conversation happening earlier than felt comfortable, before requirements were locked and direction was set.

Ruthless about scope.

I cut aggressively. Most products fail from too much, not too little: too many edge cases accommodated, too many stakeholders appeased, too many "while we're at it" additions. Scope discipline is how good work ships.

Shortest path to value.

I start with the outcome, not the solution. What are we actually trying to achieve, and what's the fastest route there? If part of the solution delivers value before the whole does, we ship the part. Sequencing is a product decision, not a project management one.

Beyond Product

Outside of work you'll find me on a rock wall, at a pool table, or deep into a board game. I like problems with rules, whether the board is physical or technical. On the building side, I maintain a portfolio of personal projects spanning enterprise automation, AI and LLM tooling, Excel add-ins, and demand and supply planning, the same problem space I work in professionally, but with more room to experiment. Most of what ends up in my day job started as something I was tinkering with on my own time. You can find the full portfolio on my projects page.

About Me