Bottleneck! Dead Ahead!

The writing is mostly back on track now that we’re home from our epic arctic adventure (puffins!), with our word count standing at a fiendishly satisfactory 66,600. We still have a bunch of stubs laid out and waiting, so we can keep steaming along for a while. Jen just completed a scene in a particular POV, so while that voice is warmed up she’ll jump ahead a few scenes to that character’s next appearance. Kent is in exactly the same situation with another character. One of the (many) great things about writing with a partner is the parallel processing.

But, let’s not be hasty.

All this skipping around with the chronology is fine, as long as we’re paying attention. We have another plot thread, which involves a different subset of the cast and therefore will take a bit of a mental shift to pick up right now. That’s why we were thinking of skipping past it. But, the events in that thread’s next few scenes are tightly coupled, which means it doesn’t make sense to divvy them up. So, if we follow the plan where we each stick with the POV that’s warmed up, we’ll create a bottleneck when the third plot thread becomes the only option to work on.

And that’s why we’re not going to proceed that way. Jen will stick to the plan, but Kent will essay the mental shift and pivot to the other thread. Once its first scene is in the can, it won’t be able to create a bottleneck. At that point, Kent can stick with that thread or swing back to the other one (which has more sex in it).

This idea of bottlenecks doesn’t really pertain if you work solo. At most, it can dictate what order you write the scenes in, but you’re going to be the one writing all of them regardless. With a partner comes the need to coordinate. If Jen can’t write scene B until Kent finishes scene A, then we lose the parallel processing advantage.

A writing partner is someone who helps you figure out the most efficient way to tackle working with a writing partner.

Post a comment

You may use the following HTML:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>