anti-pattern // sfmcPRODUCTION

Redesign Before Discovery

Do not “clean up” an undocumented production org before understanding what is actually active.

Context Pack →Open Workspace →
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources0Other sources0Last verifiedNot recorded

Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.

Problem

Names and folders can be misleading; hidden dependencies often live in SQL, imports, exports, sends and business processes.

Approach

Inventory and classify first, trace dependencies second, redesign third.

Tradeoffs

Discovery feels slower initially

Prevents expensive accidental breakage