Plotting a course
This past weekend, I had to write a plot summary for a book, and suddenly, I found myself back in my undergraduate computer science classes. Huh? I realized that I was a whisker away from making one of those flow charts they always (back then, anyway) taught you to make when you were designing a program. This kind of flow chart is a series of statements, questions, and answers, organized into a diagram designed to show you the entire structure of a program, including—you hope—all the different situations that could come up, and what should happen if they do. If you do it correctly, the program most likely will do what you want it to. Leave a step out, or neglect to include all the possible answers to the questions, and the program will fail, and you have to figure out why.
I’ve written in earlier essays that I generally start a book with a setting; once I know that, I know who will be there and why and what’s at stake, et cetera. I don’t generally outline right away; when I do, it’s near the middle of the writing process, a list of things I have to have happen before the ending (which I often know). With this book, I started with the characters and a “what-if,” began noodling around, and realized that the complexity of the story required that I come up with an outline sooner rather than later.
When I started making individual timelines for the characters, to see who finds out what when, I knew I had to start making decisions. Who’s in league with whom, how the big revelation occurs, what leads to the next thing. And that’s when I remembered the flow charts.
(Mind you, this is a memory from more than twenty years ago, back when monitors were monochrome and you had to pick the pterodactyl poop out of the keyboard. Now, run, go get Grandma another Cosmo, and crank up The Cure while you’re at it.)
All plotting comes down to asking questions and making decisions. I know this. I emphasize this when I teach classes on writing. It’s the basis of panels I’ve done at Mayhem in the Midlands and the New England Crime Bake, where the panelists make up a story based on questions asked by the moderator—who’s the main character, what does he look like, how does he get embroiled in the murder mystery, who is the villain, why, etc. It’s the scene I love so well from Shakespeare in Love, when Kit’s helping Will figure out Romeo by making decisions, starting with the known (his name is Romeo) and working toward the unknown (who is he in love with?). Every writer knows this—so what was the big revelation?
Apparently the visual metaphor I use to plot a story makes a difference to me. Who knew something that subtle could make that big a difference? An outline—something that looks like the table of contents of a book—only took me so far. The flow chart struck me as a more fluid, structured model. It has the logic, timing, and order of operations built right into it. It’s still tough to figure out all that logic, but at the end, I had a more organized vision of what, how, and when things had to happen.
It’s what every writer will tell you: you have to figure out what works for you. I’m still learning. Stay tuned.
I’ve written in earlier essays that I generally start a book with a setting; once I know that, I know who will be there and why and what’s at stake, et cetera. I don’t generally outline right away; when I do, it’s near the middle of the writing process, a list of things I have to have happen before the ending (which I often know). With this book, I started with the characters and a “what-if,” began noodling around, and realized that the complexity of the story required that I come up with an outline sooner rather than later.
When I started making individual timelines for the characters, to see who finds out what when, I knew I had to start making decisions. Who’s in league with whom, how the big revelation occurs, what leads to the next thing. And that’s when I remembered the flow charts.
(Mind you, this is a memory from more than twenty years ago, back when monitors were monochrome and you had to pick the pterodactyl poop out of the keyboard. Now, run, go get Grandma another Cosmo, and crank up The Cure while you’re at it.)
All plotting comes down to asking questions and making decisions. I know this. I emphasize this when I teach classes on writing. It’s the basis of panels I’ve done at Mayhem in the Midlands and the New England Crime Bake, where the panelists make up a story based on questions asked by the moderator—who’s the main character, what does he look like, how does he get embroiled in the murder mystery, who is the villain, why, etc. It’s the scene I love so well from Shakespeare in Love, when Kit’s helping Will figure out Romeo by making decisions, starting with the known (his name is Romeo) and working toward the unknown (who is he in love with?). Every writer knows this—so what was the big revelation?
Apparently the visual metaphor I use to plot a story makes a difference to me. Who knew something that subtle could make that big a difference? An outline—something that looks like the table of contents of a book—only took me so far. The flow chart struck me as a more fluid, structured model. It has the logic, timing, and order of operations built right into it. It’s still tough to figure out all that logic, but at the end, I had a more organized vision of what, how, and when things had to happen.
It’s what every writer will tell you: you have to figure out what works for you. I’m still learning. Stay tuned.



