All work

Carhartt WIP, 2026

Replatforming search, browse and recommendations

I own Carhartt WIP's move to a new discovery platform and its scale-up: the requirements, the vendor choice, the roadmap, the UX, and the scrum team of engineers delivering it on web and app.

Role
Product lead and product owner of the scrum team
Timeline
Requirements from February 2026, MVP live in Germany in October, rolling out across markets
Team
Web and app engineers, an implementation partner, the vendor and merchandising
Scale
25 markets, 39 locales, web and app

The problem

The business needed discovery the team could steer, test and scale across markets on its own.

Steering without engineering

Merchandisers needed to see and adjust why products ranked where they did, without raising an engineering ticket.

Testing the team can run

The team wanted to set up and read tests on its own.

One source of product data

The engine needed product data straight from the source catalog rather than through a separate feed.

What I did

Defined the platform before picking a vendor

I wrote 87 requirements across search, merchandising, recommendations and the platform itself, and split them into MVP and later phases. Every demo and every vendor score used them, which kept the decision about our problems rather than the best demo.

Ran delivery as a scrum team

Two-week sprints from contract to MVP. I own the board, the priorities, the measurement strategy and the merchandising rules, and I set the go-live plan across web, app, the implementation partner and the vendor.

Fixed the data first

Attribute names now match the source catalog, and new-arrival dates now stay stable, so the new engine starts clean.

Designed the browse experience

Curated filters per category, six to nine per page. Merchandising rules sit on top of the ranking model, so campaigns survive model updates, and sold-out products stay visible but rank low.

Category page
Color
Size
Shoe size
Material
Length
Width
Price
Boost: new arrivalsBury: sold out

Rebuilt recommendations around business goals

I audited every existing placement and set one principle for all of them: each placement gets one goal, a primary strategy, a fallback and guardrails. Search keeps sold-out items ranked low, while recommendations leave them out.

Planned the scale-up beyond the MVP

The MVP is live in Germany. I own the plan after it: rolling out market by market, adding recommendations, and testing the team can run on its own.

How we'll know it worked

  • Separate platform dashboards

    Quick to read, but apart from the rest of our reporting.

  • What we did

    Our own analytics, against a baseline set before launch

    One source the business already trusts, comparable across every phase.

Where it stands

The MVP is live in Germany, with the remaining markets to follow.

39locales in 7 languages
87requirements across four pillars
25markets in scope
Livein Germany since October

What's working

  • One set of requirements kept the vendor choice about our problems, not the best demo.
  • Fixing catalog data before the switch, so the new engine doesn't inherit old errors.

What's next

  • Rolling out market by market, so each launch is checked before the next.
  • Moving search merchandising into the team's weekly routine after launch.

What I'd do differently

I'd set the pre-launch baseline even earlier, during requirements, so every phase is measured from the same starting point.

Working on search, discovery or product data? Let's talk.