Bronze, Silver, Gold Means Nothing (When Layer Names Don't Help)
The Problem
Your data lake has three layers: Bronze (raw data), Silver (cleaned data), Gold (business-ready data). Sounds sophisticated. Then new analyst joins: "Where's customer data?" Answer: "Check Gold layer." They search. Find 14 tables with "customer" in the name. Which one is right? No idea. They ask 3 people, get 3 different answers. Turns out the "right" customer table is actually in Silver because Gold was never finished. Bronze/Silver/Gold tells you nothing about what's inside. It's like Home Depot organizing by "Bronze aisle," "Silver aisle," "Gold aisle" instead of "Paint," "Tools," "Lumber." Users need to understand what data IS, not what processing tier it's in. Metal names are architecture porn—they make engineers feel organized but leave users lost.
The Principle
Name layers by what they contain, not processing stage. Use names that self-document: Raw (exactly as source systems sent it), Curated_SystemName (cleaned, usable, still system-specific), Integrated_T...
Action Steps
Want the full solution?
Get access to all 48 cards + complete fable