Tonight, I’ll be teaching my annual class on demo teams. I know I haven’t posted about the martial arts recently, and that the majority of you out there reading this are writers, rather than martial artists, but this particular post holds helpful tips for both. And since this is what I’ll be discussing over the next two days with the students of Dragon Heart Tang Soo Do, I thought it would be appropriate. However, for the writers out there, I’ll provide annotated notes, indicating the literary terms that correspond with my demo team lingo. So even if you aren’t a martial artist and you have absolutely no desire to learn about demo teams, give it a read. I think you’ll be surprised to see just how much the two worlds intersect.
Story vs. Concept; A Demo Team Showdown
by Kisa Whipkey
Originally Posted on 5/10/13
Recently, I found myself on the wrong side of an angry, pitch-fork touting mob after I eloquently shoved my foot in my mouth. (Turns out, there’s a fine line between snarky and jackass. Especially when it falls on the wrong ears.) And as I was being schooled by a student who naively believed I was a demo team idiot, I was amazed at how often the terms “concept” and “story” were used interchangeably, as if they were the same thing. I’m not sure if this is a common misconception, but since I was due for a demo team post, I figured why not take a moment to clarify the definitions and try to make something good out of my embarrassing mistake. And what better way to do that than to pit story against concept in an epic battle of demo team terminology. Sounds fun, no?
So, here we go! Contestants to your places, aaaaaaand . . . fight!
Round One: Concept
(2014 Annotation: Writers, this is the same for you. Everything said below applies to the same definition we use in literature.)
Concept does not, in fact, equal story. If it was synonymous with any word, it would be theme. And what is theme? The point of your project. It’s the message or idea that you want to convey to your audience. Let’s check out some examples.
(These are some of the more common demo themes/concepts I’ve seen over the years.)
- Video Games such as Mortal Kombat, Street Fighter, Etc. (I’m guessing there’s a secret sect of Comic-Con Cosplayer geekhood within the martial arts.)
- Medieval Asian Warlords (Yes, the Asian part is particularly important. How else can you create something as awesome as a D-grade Kung Fu movie brought to life?)
- The Korean and/or Association Flag (Especially prevalent in the WTSDA. Apparently, we have a lot of association pride. And unoriginality.)
- Badass little kids taking over the world (Cute factor combined with awesomeness. Who doesn’t love that?)
- The Matrix movie franchise (Does this really need further explanation? The Matrix was just, like, the most epic movie ever!)
- Pretty much any popular movie franchise (Further proof of my statement on example one. Maybe we’re all nerds at heart?)
- Women’s self-defense (The only thing better than badass kids is watching a bunch of girls pummel a bunch of dudes, right?)
- Peace, Love and Unity, man (Otherwise known as the undefinable, “high” concepts.)
- The Elements (Because there can never be too many interpretations of wind, fire and water.)
(I hope, by now, you’re laughing with recognition.)
But despite my mockery, these are all perfectly acceptable examples of concept. I’ve used some of them myself. (There may or may not be multiple versions of Mortal Kombat costumes lurking in Dragon Heart’s demo team archives. 😉 ) The problem comes when that’s all there is to your demo (2014 Annotation: same is true for writing). The concept should be the foundational element, the first spark of creativity. Not the entire focus. Here’s why: concepts are simple. They contain absolutely no allusions to the story they might evolve into, making them a two dimensional, cardboard cut-out experience guaranteed to bore the life out of your audience. Don’t believe me? Let me show you. A concept’s inception typically looks something like this:
Student One: “Dude, let’s do a demo about the Korean flag!”
Student Two: “Like, oh my god! That would be totally awesome!”
Ok, maybe that’s a little facetious, but it’s not that far off the mark. A concept is that first burst of enthusiastic direction, not the ultimate goal. Don’t get me wrong, concept is very much an important part of any demo. Not only does it provide the inspiration, it has influence over decisions like costuming (aka genre, if you’re a writer), set/prop design (setting), characters, and overall presentation (POV/Voice/etc.) as well. But it’s focus remains purely on technique, and will rarely impart any lasting impression or emotion on the audience. For that, you need story.
Round Two: Story
(2014 Annotation: This is more commonly known as “premise” in the written world. But same basic idea.)
If concept is the idea, then story (aka premise) is the way you impart said idea to the audience. It builds on the foundation concept provides to create something with a far richer experience for everyone. However, story is often misconstrued to mean flash. As in, an overly theatrical fluff-fest that’s trying to compensate for a lack of technique. That, my friends, is sadly mistaken. And probably the reason story is given so little respect in the creativity division. (2014 Annotation: “flash” in literature can take on many forms, but most commonly it’s seen as an over-indulgence in world building, or an over-wrought, heavy-handed style that gets in the way of the story.)
All those components that instantly scream flash – costuming, props, etc – are not actually controlled by story. They reside within concept’s domain. (Cheeky bugger, fooling everyone by pointing the finger at story.) The only thing story controls is choreography (aka plot, for writers). Why? Because choreography is how you tell a narrative in a demo (See? Plot). The rest is bonus to help ensure the audience understands. But you don’t actually need anything beyond choreography.
Story is defined in the literary world as conflict. Meaning, there has to be something happening. A journey from Point A to Point B. I’ve written about this topic at length in my previous post, Storytelling for Demo Teams, so rather than repeat myself, I’ll provide an example of how story elevates concept. And how it doesn’t necessarily have to be complicated to be effective. (There’s only so much you can cram into a 5 minute span, after all.)
I’m going to use one of my own demos for this exercise – The Dream Sequence – which I have featured before.
The concept for this demo actually came from the music itself. (As do all my ideas, which many of you know by now.) I wanted to show a dreamy, ethereal world that matched the tone of the music. But since that isn’t enough for a competition-grade demo in my opinion, I needed a story that would deliver that message to the audience. So I created one about a little boy who falls asleep and finds the dolls he was playing with have come to life around him. When he wakes up, the dolls disappear. Literary genius, isn’t it? But that’s my point. No one said you had to be a master storyteller; you just have to tell something.
So, to recap:
Concept = dreamy, ethereal imagination.
Story = slightly creepy dolls coming to life inside a child’s dream.
(2014 Annotation: This same equation applies in literature, and is quite handy for figuring out things like queries. 😉 )
See how neither of these statements is really that complicated or involved? And how, when combined, you end up with an idea that’s far more powerful and interesting than the concept alone? That’s the beauty of story. (If you haven’t seen the demo I’m referencing, take a moment to go watch it. I’ll wait. 😉 )
And the Winner is . . . ?
That’s right, our epic showdown actually ends in a draw. Anti-climatic, I know. But that’s because one isn’t better than the other. They work in tandem, not competition. The ideal demo (or novel) is a balance of both, pulling from the strengths of each to create a wonderful masterpiece people remember for years. But, because the two terms are separate elements, it is possible to create award-winning demos using only one of them. You can have a traditional demo that focuses primarily on technique, with no storyline, just concept. And you can create a moving, story-driven demo featuring absolutely no costumes, props, or flash. (Technically, though, if you have a story, you have a concept, regardless of the addition of flashy elements. Concept can live without story, but story needs concept to survive.) The trick is knowing your ultimate goal and utilizing your team’s talents to their fullest. (I’ve given out a lot of helpful tips about how to do this.)
And remember, if you find yourself having to explain what your demo is about, you failed. (Harsh, but true.) Whether your aim is traditional/concept-driven, or theatrical narrative, your audience should always receive your message clearly. That is, after all, the entire point of demos (and storytelling in general), is it not?