Capacity Planning Meets Marketing's Ambitions
Description
A text-based meme on a dark background that lays out a sequence of events. First, 'IT Director to Everyone: We only have 20k user slots left so we'll need to get more asap'. Second, 'Campaign Team: (sends invitation to 100k+ users)'. Third, '*Site goes down*'. Finally, 'Everyone:'. Below this text is a large ASCII art representation of the 'Surprised Pikachu' meme, showing the character with an open mouth in a look of shock, rendered using braille-like dot patterns. The meme humorously depicts a common scenario in tech companies where a non-technical team, like marketing, disregards explicit warnings from the IT or engineering team about system capacity limits. The predictable result is a production outage. The punchline is the feigned surprise of 'Everyone' involved, captured by the Surprised Pikachu, which is ironic because the failure was entirely foreseeable. This resonates with senior developers who have experienced the consequences of such departmental miscommunication and lack of planning
Comments
8Comment deleted
Marketing calls it a 'viral campaign.' SRE calls it an 'unplanned load test.' The server calls it 'segmentation fault (core dumped).'
Marketing calls it “demand gen,” SRE calls it “an unscheduled 100k-user chaos test on a cluster provisioned for 20k,” and the RCA doc is already throwing OutOfMemory
The only thing that scales faster than our infrastructure costs is marketing's ability to ignore the word "capacity" in "capacity planning."
Marketing calls it a wildly successful campaign; the load balancer calls it a DDoS with a budget line
When your IT director gives you a clear capacity warning with actual numbers and timelines, but marketing treats it like a suggestion rather than a hard limit - congratulations, you've just discovered the difference between 'eventual consistency' and 'eventual catastrophe.' The real tragedy isn't the 5x oversubscription; it's that everyone acts surprised when basic arithmetic catches up with them in production
Nothing exposes the absence of backpressure, rate limits, and a queue faster than Marketing turning '20k seats' into a 100k‑user production load test
Engineering provisions 20k slots; marketing blasts 100k invites. Classic proof that user acquisition outpaces throughput in every distributed system postmortem
Our chaos experiment was “email 100k users with a 20k‑seat license” - instant thundering herd, a saturated 20‑conn DB pool, and a reminder that rate limiting is cheaper than optimism