Misadventures in Master Data Land

Kicking off the (Mis)adventure

Sarah (Brand Manager): We need 5 SKUs for the winter promotion. Let me start filling in the Excel template.

Doug (Material Master Data Specialist): Let me add that to the Master SKU tracker

Michelle (Master Data IT Manager): Make sure you use the right tabs. Finished and semi-finished have different classifications.

 

Confusion reigns

Sarah(silently saying to herself): Oh, boy! This Excel has 200 fields. What is a FERT! Let me just set up a Teams session

 

The waiting game

Sarah (on the phone with Dave): Hi Dave, I just sent you the ticket for SKU creation. Hope we can get this done in a couple of days.

Dave(Master Data Steward): Not happening, Sarah. We have a major backlog. Besides, SKUs take a lot of effort.

 

Houston, we have a problem

3 weeks later, in a meeting room

John (Warehouse Manager): We cannot receive the SKUs in DC because there is no quality inspection plan

Jeremy (Logistics Analyst): The classifications for SKUs 3 and 4 are wrong. The quality inspection data for DCs is missing

Sarah: The classifications for SKUs 3 and 4 are wrong. The quality inspection data for DCs is missing

 

 

The cost of chaos multiply

Week 4 of the misadventure

Sarah (to John on the phone): Customers are asking about SKUs and if we are ready to ship

John (Warehouse Manager): No. The missing quality inspection for Fremont DC is holding up shipments from the plant

 

Expensive lesson learned – Do it right the first time

Martha (CIO): What’s going on with our master data quality? Our VP of Supply Chain called and told me that master data errors are creating chaos in the our warehouses.

Samantha (ERP Systems Director): We need to move fast and fix bad master data in ERP fast

Rick (Master Data Governance IT Systems Manager): I think we should invest another half a million in a master data quality solution

Martha: No! Figure out a way to create master data right the first time.