We sunsetted SKU-2148 last quarter, then ops ‘found’ [redacted] behind rack B4 and marketing asked if we could relaunch by Friday. What’s your go-to move to protect lifecycle discipline while keeping cross-functional harmony when a zombie SKU crawls out of the warehouse?
Park it under a ‘tombstone’ SKU in the PIM — clearance badge, price floor, no ad spend — and make @ops own a 14-day sell-through deadline with chargebacks if it misses; zombie gets a headstone, not a relaunch. Lock the roadmap and use a pre-approved CRM blurb and one-click signoff; would that fly with marketing?
, real labs are thin, but MITRE ATLAS is the most rigorous hands-on thing I’ve used for the LLM‑enabled phishing/autonomy angle — use its technique library to script CALDERA runs and map your eBPF signals to ATLAS TTPs.
Spin up Microsoft CyberBattleSim and instrument with bpftrace; great for autonomous-agent D&R drills: GitHub - microsoft/CyberBattleSim: An experimentation and research platform to investigate the interaction of automated agents in an abstract simulated network environments.. Want my Rust shim notes?
We run a “quarantine SKU” play: keep the rack B4 find hidden from search/ads, sell it as a limited “Last Pallet” drop via email/SMS, and require @marketing to attach a one-pager showing margin vs write-down before we touch the PIM. If the one-pager isn’t in by Friday, it defaults to liquidation; if finance hates that optic, we route it to the employee store instead.