QA Graphic

Lessons from the Blackout at Super Bowl 47

A QA Perspective

Super Bowl weekend is always filled with excitement, but for those of us in Quality Assurance, it's also a great time to reflect on the unexpected failures that happen on the biggest stage. One of the most infamous moments in Super Bowl history? The blackout at Super Bowl 47 - the night the lights went out in New Orleans.

In Episode 21 of the 'QA in a Box' podcast, I took a deep dive into this bizarre event and what it teaches us about production failures. Let's break it down.


The Setup: A Game for the Ages

It was February 3rd, 2013. The Baltimore Ravens and San Francisco 49ers were battling it out at the Superdome in New Orleans. Ray Lewis was playing his final game, and the Ravens were dominating early, taking a 28-6 lead after a record-breaking 108-yard kickoff return for a touchdown.

And then - BOOM.


The Blackout That Stunned the World

At 13:22 in the third quarter, half the stadium went dark. The scoreboard, the lights, the broadcast feed - everything except the commercials (because of course, Super Bowl ads are sacred). For 34 minutes, the game was in limbo. Players stretched on the field, fans were confused, and broadcasters scrambled for filler content.

From a QA perspective, this was a full-scale production outage. The kicker? The stadium had a redundant power system, but the flaw in their setup went unnoticed - until the worst possible moment.

Sound familiar?


QA Takeaways: Always Be Ready

This incident highlights a crucial lesson for QA professionals. When you're in production, anything can happen. The real question is:

  • Do you have a plan for when things go wrong?
  • Do you know who to contact when an issue arises?
  • Do you have a process to verify the issue won't happen again?

The Superdome did have a contingency plan, but it wasn't fully tested. And that's a classic QA pitfall - assuming that redundancy alone is enough.

In QA, we know that Production will always find the bug you missed.


What Happened Next?

When the lights finally came back on, the momentum of the game shifted. The 49ers used the delay to regroup, cutting the lead to 31-29. If not for a goal-line stand by the Ravens, this could have been remembered as the greatest comeback in Super Bowl history - instead, it became the Blackout Bowl.

The Ravens won 34-31, but what do most people remember? The failure.


Final QA Lessons

The Super Bowl 47 blackout was more than just a stadium issue - it was a lesson in preparedness. Here's what QA teams can learn:

  • Production failures are inevitable - be prepared for them.
  • Know your escalation process. Whether it's IT, DevOps, or even the power company, you need the right people ready to respond.
  • Always conduct a post-mortem. Stadium officials did a full investigation after the game. Do the same after any QA failure - learn, improve, and ensure it doesn't happen again.

Just like in the Super Bowl, QA isn't about stopping the game - it's about making sure it runs as smoothly as possible.

 

About

Podcast Show Notes and Links

Schedule

Thursday 13 PlayWright
Friday 14 Macintosh
Saturday 15 Internet Tools
Sunday 16 Misc
Monday 17 Media
Tuesday 18 QA
Wednesday 19 Pytest