3 months of publishing, done in 1 week
- BRP
- Global Digital Transformation Specialist
- 3 months, redesign to first cycle
- 2026
Staff role, not a client engagement
Product and model data had to travel from PIM to published pages across BRP's commercial footprint: more than 110 countries in North America, APAC, EMEA and LATAM. One model took about three months. After the operating model was rebuilt, it took a week.
At a glance
1 week
from PIM to published, down from about 3 months
The situation
Every model BRP launched needed its specifications, imagery and pricing to reach live pages across the company's commercial footprint: more than 110 countries in North America, APAC, EMEA and LATAM. The data started in PIM and reached the web through a chain of handoffs that nobody owned end to end. A single model took roughly three months to get through it, and the teams downstream spent that time waiting and re-entering the same values.
What I did
The chain nobody owned end to end
I mapped the PIM-to-web chain as it actually ran, which turned out to be different in almost every market, and rebuilt it as one operating model: shared data structures, a single workflow standard, and a named owner for each stage of the content lifecycle.
QA moved in front of publishing
Then I automated the parts that were being done by hand. QA moved in front of publishing rather than after it, and workflow analytics made it visible where a model was sitting and for how long, so a stalled launch stopped being something you found out about late.
Results
- The PIM-to-web process went from about 3 months to 1 week
- QA runs on every publish instead of on request
Skills used
- Product Strategy
- UX & Product Design
- Web Development
- Data Pipelines & Automation
- Generative AI
- SEO
- Operational Analytics
- Governance & Standards
- Cloud Infrastructure
Systems: Google Apps Script, Google Sheets
