Lean Writing

From Insider Outlook
Revision as of 03:07, 23 April 2020 by Admin (talk | contribs) (1 revision imported)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Back to Writing

What is it?

Simply put, a Lean methodology is doing just enough to have a workable product, and then testing it on live customers as you observe their behavior and provide their feedback. But, that is a gravely simplified explanation.

Recently, a "Lean" movement has been transforming a number of fields. Lean Marketing, Lean Development, Lean Management, etc. While simplifying product releases is not rocket science, there is a certain amount of understanding that needs to be in place to leverage the advantages of the technique. More importantly, there is a traditional workplace cultural shift required to actually embrace the seemingly disorganized workload that emerges. In a large company, this is not a trivial task. Those who have been successful for years using the standard management techniques will find it the most disheartening. Senior managers that like plans, schedules, budgets and procedures will be completely lost until they can understand the value of a shorter cycle. The good news is that an individual writer can change their personal rituals fairly easily. But more on that shortly. Let's see how a traditional product or service would be built, and then relate that to a work of fiction or fantasy.

Traditionally, a widget or service is developed with the widest appeal in mind. It will need to be usable by the biggest target audience possible, in many different disciplines, and possibly for lots of different purposes. It should also be immediately useful anywhere, with a minimum of instruction and setup. In this world, a specific function was idealized, not so much a particular user. The function would be analyzed, broken down, modeled, and optimized for a variety of general users. Such a product had to be developed, tested, mass produced, marketed and distributed before the company could make their first dime of revenue. This is not very conducive to innovation and it certainly presents a high bar for market entry. Yet, dozens of companies flourished in this environment, and actually became experts at dealing with the many problems of this method. This is a traditional description of the Product Development cycle.

Once a different approach surfaced, this method got tagged with a new name, the Waterfall model. This simply acknowledges that the entire river of development money had to run over a cliff before any returns could be realized from the pool at the bottom of the falls. This was the old industrial model, and it work well on a long cycle. Then, the Internet happened. Long cycles were no longer tolerable.

Websites were fancy electronic brochures in the beginning. Organizing content and navigating among it was the biggest challenge originally. Soon, dynamic pages surfaced that could do math and look stuff up in databases. Before long, the old brochure websites were being used to provide valuable services, and eventually delivered a valuable product in themselves. Once the developers had the bare bones of the website up and working, there was nothing stopping them from posting it and letting it run. Once launched, developers realized that they could make small, incremental changes to the live website on a practically continuous basis and test it on live users immediately. By passively observing the use of the new features, they could know quickly if their idea was a good one. Small, but frequent changes also ended up keeping the website bug-free. Then, they would turn their attention to the next wave of small, but helpful changes while observing how the clients were using the new features. They were getting fast feedback that was not subjective or solicited outside of the regular user environment. This was powerful information. Interesting observations surfaced regarding customer behavior, and i still think we debate the value of font style, color choices, and what size to make buttons even though there is evidence to support nearly any design choice. The key thing is that all of that was testeable, and you could get real comparison numbers immediately.

This developed into a toolkit of methods, practices and techniques that formed the basis of Agile methodologies. Basically, they started with something simple, saw what frustrated users, added only useful features, and then pursued the next frustration. Principles that eliminated waste effort emerged quickly, allowing them to build only the necessary components, and putting decision making power in the hands of the ones doing the work. This was basically the emergence of a Lean philosophy which is currently being applied to a wide range of industries.

Lean Writing

The fundamental idea of a Lean strategy is to get something that mostly works introduced to the market as soon as possible, and then leveraging fast feedback and customer involvement from the very earliest stages. In turn, this feedback will drive further development and new features in the next version. A better product or service can be created over time from these early releases, and a mature product will evolve over a longer timespan based on just what the market needs or wants, and nothing more. By working in short cycles, the final product creates a better fit with the actual needs and desires of the intended audience, not just the expectations of upper management or an ivory tower product owner. Think about how many useless features, gadgets, and functions the typical word processing software has. They all sound good in focus groups, but the reality of how frequently they may be used is completely unknowable. Lots of time and resources are wasted on trivially important features, not to mention the bugs they create along the way.

Similarly, Lean writing is doing just enough writing to get the story across in a satisfying way to the reader, without writing anything more than what is needed to do just that. The idea is to write the basics, and elaborate as necessary to create a stronger, more complete story. Have a group of friends or other writers read it, and then respond to their feedback to fill in more blanks that you may not have thought about. You should always be adding or elaborating on things they pick out as interesting. The gap between what is interesting to authors and what is interesting readers can be bigger than you might imagine as an author. This is the story you want to tell. However, this is not very attuned to your readers. You need to be writing what they want to read, and that is not always the exact story you want to write. But, by listening to their feedback and comments, you can get back on their wavelength and develop the basic story into something that thrills their imagination, and will make them want more. This is the idea of lean writing applied to fiction and fantasy.

Lean Worldbuilding

In worldbuilding, this can be a very important skill to recognize and manage. It is critical to have a solid handle on the immediate world around the characters, and it is certainly helpful to know a good amount of what they think and believe about it. Details about the world can be rich and full of local color and culture, and that helps to bring the environment to life. However, it is easy to get buried in excessive detail, and you may end up spending your valuable time fleshing out marginally important features. Here is where Lean writing can save you hours of development time. An example may be helpful.

You are writing a story, and your protagonist discovers a note written in a language they do not understand. Do you need to create this new written language? If it will play a key role in the plot, then it is probably useful to flesh that out to some degree. Otherwise, just understand that such detail is not really a key deliverable in getting the story written. Maybe it will help the author embody the characters more effectively, and that can have some merit, but unless the look and feel of the language is going to be directly meaningful to the reader, it may be a good idea to set that aside until it is actually needed. Instead of spending days creating a make-believe language, paint it in broader strokes that might actually be helpful to the reader. It may be enough to simply compose a list of adjectives to describe the writing style. Describing it as flowing and elegant depicts a certain sophisticated characterization of the hand that wrote it, while calling it scratchy and scrawled reveals something more barbaric about the ones who may use it.

As another example, instead of enumerating all of the individual plants the protagonist might encounter on a walk through a garden on an alien world, describe in more general terms the shapes and colors of the plants and flowers, the scents, and the sound of the wind. By using broadly suggestive and familiar terms, you can more accurately convey a mood or feeling conjured up by those plants and overall environment. That is probably what you were meaning to do anyway through the detail of the plants themselves. You have just saved yourself hours of writing an herbology guide that would not be useful anywhere else, and would just waste words downloading all that detailed jargon to the reader. Less is more, and that is what Lean writing is all about. Your readers have excellent imaginations, so let them apply theirs to the fullest extent.

The beauty of Lean Worldbuilding is that you can always come back and add a little more as you need it. Instead of writing up a full synopsis of six religions, let their development evolve as characters reveal aspects and morality through their actions. Build up a religion as it is expressed through the people that follow it, and especially their struggles to live out those ideals. This makes the tenets and doctrine much more relevant and personal, and less academic. A manufactured single dimensional philosophy is easy to spot, and your readers deserve something more complicated and conflicted. Using a lean method in your writing, you only write the important stuff as it is needed, evolving from broad strokes and ideas to finer details as they are needed by the reader.