Harry Potter and the Two-Hour Prologue

Last week the Official Sweetie of Muddled Ramblings & Half-Baked Ideas and I decided to watch the first Harry Potter movie. It was my first exposure to the franchise. Considering all the hype, and the penetration of the film into pop culture, the movie was surprisingly mediocre. Of course, it’s possible to make a crappy movie no matter how brilliant the source material is, but in this case the biggest problem with the movie was simply in its storytelling. I suspect it is a faithful reflection of flaws in the novel itself.

The biggest storytelling flaw in this flick is that it takes forever for the story to actually begin. I have been accused of “walking to the story” often enough to recognize it when I see it.

We start with a prologue that reveals nothing which isn’t amply explained in short order. Then we have many scenes that do nothing but establish setting. Crappy home life (perhaps more interesting if we didn’t know what we already do), shopping for school supplies, and so forth. As far as the actual story goes, we finally hear a whisper of the name that will shape his young life. But only a whisper, and we proceed with a series of events that aren’t moving anywhere. There are, James Bond-style, offhand mentions of things that conveniently turn out to be important later, but that’s about it.

Once he’s at school, we get closer to a plot, but not very quickly. We get to meet important friends and rivals, but mostly it’s still establishing setting, building a whimsical and magical world. Don’t get me wrong, the movie does a fine job of this, but it’s all done through a series of unrelated events.

One of those disconnected events is that Harry’s natural broom-riding ability leads him to be the “seeker” for his house team in the sport of Quidditch. The game is like this: A bunch of people fly around under very complicated rules, scoring points here and there, then the seeker from one of the teams catches a tiny flying robot-magic-thingie and the game is over, all the rest of the activity having been rendered moot. It makes for some good action scenes, but they are not in service of the story.

The story, what there is of it, is that there’s an important thing that bad guys want to steal. The most interesting part of that story is Snape, a teacher and the head of the “asshole” house at the school. So many things suggest he’s a bad guy, but… when shit gets real his actions are noticeably absent of evil.

When one makes a movie based on a novel, the hardest decisions the screenplay writers face is what to cut. A movie simply can’t contain an entire novel. I wonder, looking at what they decided to keep, looking at scene after scene that did not serve the story, what they decided to chop. More of the same? Or were they worried that rabid Harry Potter fans would riot if the movie didn’t include the gratuitous prologue that was in the novel, and instead cut more interesting things to remain “faithful”?

The next night OSoMR&HBI and I watched the next movie in the series, and now we have consumed two more. So clearly HP-1 was not so awful we walked away from the franchise. This was partly because friends assured us the following movies got better.

Today I realized why. The first movie is ALL prologue. It is the reading you are supposed to do before coming to class. Being a story is a secondary goal, behind introducing us to the world.

Aspiring writers take note: WORLD BUILDING IS NOT STORYTELLING. I recently had the privilege of reading a friend’s draft of a novel, and I realize now I forgot to compliment her on the way she built a really strange world through the telling of her story. She hit the ground running and we got to see the world as the action unfolded, in a natural way. So, just do that.

3