It’s not about you.

One of the assumptions fostered by many generations of how-to books and writing classes, is that a piece of fiction is the product of extended and complex conscious deliberation: the application of various formulae and rules. If you look through these books, the list of rules is often quite intimidating. It’s a lot like what would happen if driver’s education began with presenting each student with an enormous pile of all the 10,000-odd individual components of a disassembled automobile. “First, assemble the engine…” Does it have to be that way?

I worked for a long time as a development executive, where a big part of my job was to concoct concepts for stories and then build the skeleton of a plot to be executed by others. This was often just as painstakingly deliberate and time-consuming an exercise as the writing courses would make it sound, with a lot of teeth-gnashing in trying to maneuver characters and situations from point A to point B.

Although that process is typical of Hollywood feature film storytelling, it’s not the way that I approach fiction. This type of plotting is fundamentally concept driven: you build a plot around an idea, and, often as not, try to fit the characterization in around it.

By contrast, every piece of fiction I’ve written at my own behest has been driven by the characters, with — and this is the critical piece — the distinct, sometimes unsettling feeling that the characters contained their stories, before I had written a word or even given it a lot of thought. Surprisingly little of their plots was dictated by me.

(My first novel, Double Yellow Line, was a mixed bag in this regard, with about an equal mixture of my ideas and the characters’, which I consider to be its primary flaw. You can see the author deliberating and struggling rather than listening to the characters, which gives it a decidedly amateurish quality in present form. I’m obviously not satisfied with it, which is why a page-one rewrite is high on my list of things to do.)

At some point in the process — for me, often before the story begins — the characters take on an independent life and they dictate their own actions and their own choices. This is extremely frustrating if you have a strong preconceived agenda regarding plot and themes because you often find that they don’t always cooperate with your plans. Conversely, you may find the characters doing things that you don’t readily understand.

At this point, plotting and writing the story is less about invention and deliberation and more about discovery and negotiation. It’s still a lot of work, but it’s a very different kind of work than laborious mechanical plotting. It’s more akin to directing a play, full of colorful, mercurial, and sometimes very evasive performers who insist on ad-libbing their lines and doing things their own way.

Above all, managing that process demands that you be willing to alter or sacrifice your own plans and ideas for the sake of the characters. This isn’t the same as indulging them, or reducing the story to wish fulfillment — it’s simply accepting that characters, like children, may not be interested in or willing to live up to your expectations for them. Ultimately, you can’t force it, at least not without resorting to contrivance or simply making the characters act in illogical ways.

I don’t mean to belittle the importance of technique and structure. Writing, whether prose, poetry, screenplays, stage drama, or comics, is formalistic: there are certain techniques and structures with which you essentially have to be familiar. You can’t really write good poetry if you have no grasp of meter, for example, and you can’t write a salable screenplay if you don’t understand three-act structure. I think it’s helpful to study such things and learn to recognize how they function in other works so that you can begin to internalize them.

However, storytelling is not simply an exercise in technique, and if you are preoccupied wrestling with the mechanics, you’re doing it wrong. If it feels laborious, the finished product will feel labored.

Among my occasional responsibilities when I worked in comics was reviewing the portfolios of artists. Most aspiring comics artists will, as they should, fill their portfolios with only what they consider to be their best work. Unfortunately, that often means pieces on which they’ve labored long and hard, striving for intricate detail and perfect rendering, to the point where the work is stiff and lifeless. I’ve seen many artists whose actual best work is in their sketchbooks. The loose doodles and candid sketches are where you can see the emergence of their true style — the way they interpret the world through their art — unencumbered by their conscious efforts to conform to someone else’s ideas of Good Art. There are rules they need to understand, of course ( if not necessarily follow), such as perspective and human anatomy, but what will ultimately make the work worthwhile is possessing a life of its own.

Much the same applies to prose, to film scripts, and to any other form of narrative art. It’s easy to lose sight of that, since both instructors and the entertainment/publishing businesses really like formulas and rules, but it’s one of the things that separates the wheat from the chaff.

# # #

2 thoughts on “It’s not about you.”

  1. I really like what you’re saying here–escpecially the part about how if it feels laborious you’re doing it wrong–but it brings up another question for me:

    How closely are the actual act of writing and the creation of the story linked, for you? Does the story grow in your head at its own pace, or does it only progress when you sit down to write?

    What you said about structure not being a primary concern and the characters basically having the last say on what’s going to happen struck a chord for me, but my issue–and perhaps this is primarily laziness–is that the story happens too fast in my head for me to get it all down on paper. There are a number of stories I’ve worked on that exist in their entirety in my head, and that I’ve written down chunks of, but I never want to go back and fill in the missing pieces because I already know what happens.

  2. <blockquote>How closely are the actual act of writing and the creation of the story linked, for you? </blockquote>

    An interesting question. With <strong>Dharma Bum and the Shield of Athena</strong>, in particular, I am convinced that 85-90% of the story existed before I started writing it. (I had a similar sense with <strong>Deidre Tanaka Does Not Speak Japanese</strong>, but it wasn't as acute.) In the former, I "created" very little in any conscious or deliberate sense. It always seemed to be going somewhere, although until quite close to the end, I wasn't sure where. (I had a number of ideas at different points, most of which proved to be wrong.) There were things that felt important, although I frequently didn't understand why until much later.

    The best analogy I can make is that each scene of <strong>Dharma Bum</strong> was like watching pieces of a movie through an open door that you can't enter, and then trying to transcribe it as best you can. It came in fits and starts, and it was only when it was done that I had enough information to perceive it as a whole. I would like to say I created all of that, but I feel I would be lying…

    <blockquote>What you said about structure not being a primary concern and the characters basically having the last say on</blockquote>

    I think it's important to note that the stories do have structure. <strong>Deidre Tanaka</strong> has a pretty straightforward three-act structure, <strong>Dharma Bum</strong> is four. (I thought the latter was going to be three, which tells you about how much conscious control I have over the structure…) I didn't design them that way, but I have a passable understanding of how story structure works, so the portion of my unconscious that composes these things has apparently internalized that. On the other hand, I am resigning myself to the fact that whatever ideas I may have about where the story is going to go or how it's going to be structured are likely to be wrong.

    <blockquote>but I never want to go back and fill in the missing pieces because I already know what happens.</blockquote>

    I do wonder sometimes if the fact that I don't consciously know where the story is going a lot of the time is a psychological strategy to make sure I keep working on it — I may be frustrated, but I want to know how the story ends! To some extent, it comes down to what your motivations are for creating the story. If you're not interested in having it read by anyone else (and there's nothing wrong with not wanting to), then finding out the ending may be the <em>only</em> motivation to create the story in the first place.

Comments are closed.

Privacy Preference Center

Accessibility Settings

If you change certain aspects of the site's appearance using the accessibility sidebar, it may set these cookies to manage and remember your settings. The wahFontColor and wahBgColor cookies, which are set if you alter the site's color scheme, normally expire after about 14 days, but you can remove them immediately by clicking the "Restore Defaults" button on the sidebar.

I may sometimes present an alternative version of the sidebar offering different options, which may set the a11y-desaturated, a11y-high-contrast, and/or a11y-larger-fontsize cookies if you change those settings. These a11y cookies normally expire after about seven days, but are removed immediately if you restore the applicable settings to their default values.

wahFontColor, wahBgColor, a11y-desaturated, a11y-high-contrast, a11y-larger-fontsize

Password-Protected Posts

Accessing certain posts or pages on this website may require you to enter a specific password. If you correctly enter the password, the site saves this cookie on your device to allow you access to the password-protected post or page. (For this cookie, "xx" will be a cryptographic hash.) There may be more than one of these cookies, particularly if you access several password-protected posts with different passwords. The cookies normally expire in about 10 days, and are not set at all if you do not access any password-protected content.

wp_postpass_xx

Commenting

When you submit a comment, you may have the option save your information for future comments, storing the info in these cookies. (For each of these cookies, "xx" will be a cryptographic hash.) The cookies are not set at all unless you select that option when submitting a comment. They normally expire in just under one year, but you can delete the cookies in your browser (or other user agent) at any time. (These cookies are not usually set for administrative users, since comments they submit while logged in are associated with their user ID number and user profile information rather than a manually entered name and email address.)

comment_author_xx, comment_author_email_xx, comment_author_url_xx

YouTube Videos

Embedded video players for content hosted on the YouTube video platform (which is owned by Google LLC) may set these third-party cookies and/or use similar technologies to store data in your browser (or other user agent) for purposes such as (without limitation) managing video settings (e.g., tailoring the playback to your connection speed), storing video preferences, providing certain functionality (e.g., allowing you to pause a video at a particular point), showing you advertisements, associating your video viewing and other activity with your Google account (if any), ensuring proper functioning of the service, preventing abuse, and/or compiling user analytics data. Such cookies and/or stored data items may be set by various domains (such as, though not necessarily limited to, youtube.com; youtube-nocookie.com; googlevideo.com; ytimg.com; google.com; accounts.google.com; www.googleadservices.com; and/or doubleclick.net, which is part of the DoubleClick advertising service, also owned by Google LLC). Not all the listed cookies and/or data items are necessarily set in all instances, and there may sometimes be others not listed above, particularly if you are logged into a Google account. Some persist for only a few minutes, or until you close your browser (or other user agent); others may remain in your browser (or other user agent) as long as your individual settings permit. To learn more about what information the YouTube platform and other Google services may collect through and/or in connection with embedded video players and how Google may use that information, see their "How Google uses information from sites or apps that use our services" page and the Google Privacy Policy. For additional information about how Google uses cookies and/or other technologies that may collect and/or process personal information, see the "Technologies" section of their Google Privacy & Terms site and the "Our advertising and measurement cookies" section of their Google Business Data Responsibility site, which includes a detailed list of cookies associated with Google advertising and measurement products. (Those pages do not currently discuss the storage of data in your browser (or other user agent) using technologies other than cookies, e.g., in web storage.) For more information about Google advertising, see the "Advertising" section of their Google Privacy & Terms site. (Google, DoubleClick, YouTube, and other related marks and logos are trademarks of Google LLC.)

VISITOR_INFO1_LIVE, VISITOR_INFO1_LIVE__k, VISITOR_INFO1_LIVE__default, YSC, YEC, _Secure-YEC, PREF, GED_PLAYLIST_ACTIVITY, CGIC, DV, CONSENT, SOCS, AEC, exchange_uid, id, pm_sess, pm_sess_NNN, aboutads_sessNNN, remote_sid, test_cookie, use_hitbox, _gac_gb_, __gads, _gcl_, _gcl_au, _gcl_aw, _gcl_dc, _gcl_gb, _gcl_gf, _gcl_ha, __gpi, __gpi_optout, __gsas, Conversion, 1P_JAR, ACLK_DATA, GPS, NID, ENID, ANID, AID, TAID, IDE, APIS, SAPISID, DSID, HSD, SID, HSID, SSID, SNID, SIDCC, FCCDCF, FCNEC, FLC, FPGCLAW, FPGCLDC, FPAU, GAPS, GLC, N_T, OTZ, PAIDCONTENT, RUL, TAID, UULE, LOGIN_INFO, Permission, yt.innertube::nextId, yt.innertube::requests, yt-html5-player-modules::subtitlesModuleData::display-settings, yt-html5-player-modules::subtitlesModuleData::module-enabled, ytidb::LAST_RESULT_ENTRY_KEY, yt-player-autonavstate, yt-player-bandaid-host, yt-player-bandwidth, yt-player-headers-readable, yt-player-lv, yt-player-quality, yt-player-volume, yt-remote-cast-available, yt-remote-cast-installed, yt-remote-connected-devices, yt-remote-device-id, yt-remote-fast-check-period, yt-remote-session-app, yt-remote-session-name, application_server_key, AuthKey, DeviceId, Endpoint, HighPriorityNotificationShowCount, HomePromptCount, HomePromptTime, IDToken, IndexedDBCheck, LogsDatabaseV2, P256dhKey, Permission, PromptTags, RegistrationTimestamp, shell_identifier_key, TimestampLowerBound, yt-serviceworker-metadata

Vimeo Videos

These third-party cookies may be set in connection with embedded video players for content hosted on the Vimeo video platform, for purposes such as (without limitation) managing video settings, storing video preferences, providing certain functionality (e.g., allowing you to pause a video at a particular point), associating your video viewing and other activity with your Vimeo account (if you have one), showing you advertising, ensuring proper functioning of the service, preventing abuse, and/or compiling user analytics data. Cookies whose names begin with "_ceg" are associated with the Crazy Egg web analytics service (which is subject to the Crazy Egg Privacy Policy and Cookie Policy). Cookies whose names begin with "optimizely" are associated with the Optimizely digital experience platform (which is subject to the Optimizely Privacy Policy; the "Privacy" section of the Optimizely Trust Center provides additional information about Optimizely privacy practices, including a link to the Data Processing Agreement that applies to personal data the Optimizely services process on customers' behalf that may be subject to certain regional privacy and/or data protection laws, while their "Cookies and localStorage in the Optimizely snippet" help page provides additional technical information about the cookies and/or similar technologies used by that platform). Many of the other listed cookies are associated with the Google Analytics service, the Google AdSense advertising service, and/or other Google advertising and measurement products, which are subject to the Google Privacy Policy; see their "How Google uses information from sites or apps that use our services" page, the "Information for Visitors of Sites and Apps Using Google Analytics" section of the Google Analytics "Safeguarding your data" help page, the "Technologies" section of their Google Privacy & Terms site, and the "Our advertising and measurement cookies" section of the Google Business Data Responsibility site (which includes a detailed list of cookies associated with Google advertising and measurement products) for more information. The Vimeo Cookie Policy does not currently disclose the normal durations of the cookies and similar technologies the Vimeo platform uses, but it appears that some may remain in your browser (or other user agent) for as long as your settings permit. To learn more about what information the Vimeo platform collects and how that information may be used, see the Vimeo Privacy Policy. The Vimeo Cookie Policy also provides information about how Vimeo users can control the use of third-party analytics and/or advertising cookies in connection with embedded Vimeo video players. (Vimeo and the Vimeo logos are trademarks of Vimeo.com, Inc., registered in the U.S. and other countries. Crazy Egg is a trademark of Crazy Egg, Inc. Optimizely is a registered trademark of Optimizely, Inc. in the United States, EU, and elsewhere. Google, AdSense, Google AdSense, Google Analytics, and other related marks and logos are trademarks of Google LLC.)

_abexps, aka_debug, clips, continuous_play_v3, embed_preferences, has_logged_in, is_logged_in, jsessionID, player, search_click_position, Searchtoken, stats_end_date, stats_start_date, sst_aid, uid, v6f, vimeo, vuid, _ceg.s, _ceg.u, optimizelyBuckets, optimizelyEndUserId, optimizelySegments, _ga, _ga_, _gac_, _gaexp, _gaexp_rc, _gat_, _opt_awcid, _opt_awgid, _opt_awkid, _opt_awmid, _opt_utmc, _opt_expid, __utma, __utmb, __utmc, __utmt, __utmv, __utmz, _dc_gtm_, AMP_TOKEN, FPID, GA_OPT_OUT, adsense, adsenseReferralSourceId, adsenseReferralSubId, adsenseReferralUrl, adsenseReferralUrlQuery, S_adsense, Conversion, _gac_gb_, __gads, _gcl_, _gcl_au, _gcl_aw, _gcl_dc, _gcl_gb, _gcl_gf, _gcl_ha, __gpi, __gpi_optout, __gsas, id, pm_sess, pm_sess_NNN, aboutads_sessNNN, test_cookie, CONSENT, SOCS, GED_PLAYLIST_ACTIVITY, 1P_JAR, ACLK_DATA, GPS, NID, ENID, ANID, AID, TAID, IDE, APIS, SAPISID, DSID, HSD, SID, HSID, SSID, SNID, SIDCC, FCCDCF, FCNEC, FLC, FPGCLAW, FPGCLDC, FPAU, GAPS, GLC, N_T, OTZ, PAIDCONTENT, RUL, TAID, UULE

PayPal® Buttons

The payment or donation buttons that may appear on portions of the administrative dashboard (which is not normally accessible except to logged-in administrative users) contain embedded content served by PayPal® services. Those buttons may set the third-party cookies PYPF (via paypalobjects.com, which is owned by PayPal, Inc.), which appears to check whether or not you are a logged-in PayPal user, possibly to facilitate the PayPal user login process, and/or 01A1 (via abmr.net, which is owned by Akamai Technologies), which stores certain technical information about your device and browser (or other user agent), possibly to facilitate the login and shopping cart functions. The PYPF cookie normally expires in approximately four weeks, the 01A1 cookie in approximately one year.

Each PayPal payment or donation button may also incorporate a tracking pixel called "pixel.gif" (which loads from paypalobjects.com). A tracking pixel, sometimes known as a web beacon, is a tiny image file that loads from a remote server; it's a type of embedded content (as is the button itself, which loads from the same domain). The image file itself contains no personally identifiable information, but the loading of that file may be used to help identify and/or track you.

If you use the buttons to make a payment or donation, the PayPal services will set additional cookies (not listed here) to manage your PayPal login and transaction data (and potentially also for various other purposes, e.g., user analytics and/or advertising). For more information about what data PayPal services collect and how that data may be used, visit the "Legal Agreements for PayPal Services" page to review the PayPal Privacy Statement and Statement on Cookies and Tracking Technologies that apply in your location (the Statement on Cookies and Tracking Technologies that applies to each region is linked from within the applicable PayPal Privacy Statement). For more information about how Akamai may collect, process, and/or use personal data, visit the Akamai "Privacy and Policies" page and Privacy Trust Center. (PayPal.com, PayPal, and all logos related to the PayPal services are either trademarks or registered trademarks of PayPal, Inc. or its licensors. In addition, all page headers, custom graphics, button icons, and scripts related to the PayPal services are service marks, trademarks, and/or trade dress of PayPal. Akamai is a registered trademark or service mark of Akamai Technologies, Inc. in the United States (Reg. U.S. Pat. & Tm. Off.).)

PYPF, 01A1