Coding Horror

programming and human factors

In Defense of the "Smackdown" Learning Model

I've occasionally been told that I have a confrontational style of communication. But that's not necessarily a bad thing-- as Kathy Sierra points out, the smackdown learning model can be surprisingly effective:

What happens to your brain when you're forced to choose between two different--and potentially conficting--points of view? Learning. That's what makes the smackdown model such an effective approach to teaching, training, and most other forms of communication.

Wrestlemania III -- Hulk Hogan vs. Andre the Giant

Whether you're writing user instructions, teaching a class, writing a non-fiction book, or giving a conference presentation, consider including at least some aspect of the smackdown model. It's one of the most engaging ways to cause people's brains to both feel and think -- the two elements you need for attention, understanding, retention, and recall.

By presenting different perspectives or views of the topic, the learner's brain is forced into making a decision about which one they most agree with. And as long as the learner is paying attention, you won't even have to ask. In other words, it doesn't have to be a formal exercise where the learner must physically make a choice between multiple things; simply by giving their brain the conflicting message, their brain has no choice. Brains cannot simply leave the conflicts out there without at least trying to make an evaluation.

I think this is also why presentations with two presenters are unusually effective. They're more engaging because you get two viewpoints. There's more back and forth; not one person droning on, but a sort of conversation on the stage.

Although I can recommend the smackdown communication style, it's extremely important that everyone retain their sense of humor. Like "real" wrestling, always remember that you're only fighting for the entertainment value.

Written by Jeff Atwood

Indoor enthusiast. Co-founder of Stack Exchange and Discourse. Disclaimer: I have no idea what I'm talking about. Find me here: http://twitter.com/codinghorror