Clean Slate Required for PIM Success:
Migrating broken data into a new PIM system perpetuates errors; successful implementations require data cleansing before system cutover.
Podcast Episode 2 with Anthony Testa
Secrets to Building a High-Performance Product Content Team with Anthony Testa
February 18, 2025 · 1:03:58
Watch on YouTube
About This Episode
Anthony Testa from The Trada Group discusses a topic rarely covered on B2B commerce podcasts: how to structure the actual teams that manage product content and supplier relationships. Drawing from his experience at MSC (a major industrial distributor), Anthony reveals the hard lessons learned from implementing PIM systems, managing supplier data, and building organizational structures that scale.
The episode opens with a critical insight: most organizations fail at content management because they try to migrate their existing, broken data into new systems instead of starting with a clean slate. "Garbage in, garbage out" isn't a warning—it's a prediction of what will happen if you're not ruthless about data cleansing before migration.
Anthony outlines a two-team model: **Data Operations** (supplier-facing, responsible for collecting and initially processing data) and **Data Governance** (the "data police" who enforce schema, taxonomy, and compliance rules). The conversation explores how these teams interact, what happens when data doesn't fit existing categories (the "jump ball" scenarios), and how to scale supplier relationships when you're managing data from hundreds of manufacturers.
The episode covers practical details often overlooked: abbreviation standardization, formatting consistency (dashes, uppercase/lowercase), and the need for a compliance staging area where data sits before being published.
Key Themes
Two-Team Model for Scaling:
Separating supplier-facing operations from data governance creates accountability; Data Operations handles the relationship and initial processing, while Data Governance enforces compliance.
Data Governance Is People + Rules + Process:
Technology enablement helps, but you need humans defining the schema, humans enforcing rules, and humans resolving the "jump balls" when data could fit multiple categories.
Consistency Down to the Detail:
Whether it's whether "BL" means Blue or Black, or whether dashes stay in product descriptions, consistency rules matter more than you'd think—they cascade downstream to warehouses, logistics, and customer experiences.
Notable Quotes
“You literally need a clean slate because garbage in, garbage out. When you try to map your existing content over to the new system, it typically will not work. You have to go through a cleansing phase." — [[Anthony Testa]]”
“Data is never ending. It's always going to be an evolution on what your teams will continue to work on." — [[Anthony Testa]]”
“You need to make sure that you create your schema and taxonomy. Once you have that locked down, you have the data police that team now owns making sure that that data stays pristine." — [[Anthony Testa]]”
“When you think about data, you're thinking about aisles in a store. But now some products belong in multiple aisles. That's where the data governance team comes in." — [[Anthony Testa]]”
Guest
Anthony Testa — The Trada Group
Topics
Product Data Data Governance Team Structure Supplier Relations Pim Content Management Organizational Design
The B2B eCommerce Show
Real conversations with operators and leaders building digital commerce for B2B.