Pantser or Planner, it should be easy to start a book and write it either way. The methods should not be mutually exclusive and the results should be comparable once the work is complete. There is no reason to force someone into one or the other mode. But, with Parametric Writing, the expectation is you will perform all of the legwork some time, or, an editor or helper will.
Writing in the Pants mode, ‘bottom up,’ is comparable to designing a car by starting with individual components- maybe the wheels, maybe the transmission, the seats. Here the author is throwing drafts out and trying to organize them; in PW we tie outlines (Briefs) and Rules to the draft as we go. This leads to a clear and built-in summary of the Text tied directly to the draft.
Imagine dragging around plot events- in the outline- and having the appropriate paragraphs shift in the Text.
Rules, too, can be put in with clear ‘to-make’ choices. Create mutually contradictory Rules (e.g. “Bob is nice”, “Bob is too nice” and “Bob is average”) and link them as you draft Text; after, at a glance, you can review the places where these Rules actually got used in the draft, and weigh out which approach makes the most sense for the Story.
Planning
In the Planner mode, where an outline is written before the Story Text, Parametric Writing provides the tree view to the left to establish the gridwork and skeletal frame of the work. This can be done in machine design- roughing in entire automation cells as empty black boxes, leaving the specific choices of ‘what’ to the end while reserving space and interfacing for them.
Parametric Writing’s ability to insert placeholder text makes this possible. The placeholder text establishes the order of the outline, and allows you as an author to create a book-length draft that doesn’t have actual words and Text. The pages are filled with placeholder Text that matches up to the draft outline, the Briefs list. This text makes it clear how many pages are devoted to each chapter, segment and plotline; even without the real words in place, it is possible to gauge out the book, decide where the midpoint is and how the flow of the Story will go.
As the ghost Text is replaced with real words, Parametric Writing makes it clear how much Text was reserved for each Brief. This can help when filling in the Text so that we don’t accidentally write too much in a sideplot, or too little in an important event; of course, authors can always change their minds, but that decision should be conscious- not accidental.
Either Way
Parametric Writing is the same tool in either writing philosophy. The planning and the drafting- the bottom up and top down- methods still use the same tools, and it is perfectly reasonable to combine them. I tend to enjoy writing the critical middle events in full, but chunking out- leaving in reserve and assigning a placeholder to- those build-up and preparation sections, and the closing and shut-down parts of a book. Everything is important, but for me, setting aside 5 pages to explain the neighborhood and the Johnsons is easier than trying to put a note in.
Having the pages assigned having the Text held in position and waiting for finalization, helps me eyeball how the work will end up.
Computer Programming
In computer programming, and specifically in writing a large program of your own, both approaches are often used interchangeably. For me, writing a difficult algorithm and skipping for later details such as I/O, user interaction, error handling, and web boilerplate like JSON with HTTP requests, makes sense. I get a basic thing working, then start taking all of the functionality and splitting it into better functions (pieces). But I avoid certain tasks and put placeholder empty functions there, outlining the work without completing it.
The mechanical outline tools for Computer Programming include creating separate Files, and creating Functions and Properties that might be only ‘for future’. This mechanical form of outline is comparable to creating Briefs and using placeholder text. With programming, it is rare to put in a placeholder like ’50 lines of code’ as comments in a function, but more common to write overall comments and pseudo-code where the final code would go. These tools are analogous to the Briefs and Placeholder Text within PW.