Story Engineering

Whether you've been writing stories ever since you can remember or you've just begun, like so many of us, you will need a map (blueprint plan) to get to where you want to go. Hopefully, that means seeing your stories published and in the hands of wonderful readers.Larry lays done the right foundation to the essential elements of story architecture, in his book Story Engineering: Mastering The 6 Core Competences of Successful Writing, released by Writer's Digest Books. If you're hungry to see your novel or screenplay published one day, and you realize that things are just not flowing for you right now or perhaps you're discouraged with the many re-writes or rejections you've received... I believe you will find the answers in this amazing book of treasures (Larry's professional experiences) that work.I love the book (especially the music comparisons) and I see "Story Engineering" as a great tool box for writer's. The tips will help you fix your story. A wealth of valuable information is being shared and you will feel as if you're sitting under a waterfall. Once you come up for air, you will begin to write your story, your dream with passion and with understanding more successfully.

This was an all-around great book on writing. The main drive behind this book is that that are six core competencies to writing. To succeed at writing you have to nail each competency. Fail in any one and your story will suffer, if not die. He goes about showing you how to ensure you get these competencies right. He draws a line between "pantsers" (fly by the seat of your pants) and planners. He makes a strong case for planning.None of the concepts introduced are earth-shattering; you've seen all of them before. But Brook's delivery of the material truly clicked for me. As I completed chapters, I was immediately able to see these concepts at work in film and writing. Some of the complaints that I've read about this book is repetitiveness. I believe that was intentional, to hammer home the points being made. Another issue raised was Brook's penchant for analogy. Fortunately for me, I share the same penchant. If you don't, get ready for a rough ride.I consider this probably one of the best books on writing I've ever read. The true test will come with time, if I can put what I learned into practice. I highly recommend this for anyone looking to improve their story telling skills.

A useful how-to book, to be used with others.I tried comparing the beat sheet with a number of novels I was reading..Strange Fruit, The Titan, Murdoch's Red and Green and they matched..sooewhat. It was hard to identify the Pinch Points

The maxim "less is more" seems to have been forgotten here. So much so I found myself skimming more than reading. I liked what the author had to say, just not with so much padding.

So here's the thing I have learned as a teacher. Part of your job is to explain things repeatedly, in as many different ways as possible, until your audience understands whatever concept you're trying to teach them. This is something I often struggle with, as I tend to understand things intuitively in a "Yeah, you know, it's like...and stuff..." kind of way. My math teachers in grade school used to think I was cheating because I didn't show my work. I did it all in my head. On a professional level, I understand my subject and it seems simple and easy to me, so when my students don't get it the first or second time, I often have a really hard time coming up with some other means of explaining.

Not so with Larry Brooks. There are so many analogies in this book that you could make a drinking game out of it. Take a shot for every new metaphor, and you'll be hammered by the end of chapter 3. This is the mark of a great teacher. If you don't "get it" by the time you finish this book, you're brain damaged.

It is a MUST BUY, MUST READ, MUST HAVE for every writer, no matter whether you are a pantser or plotter. It will change your writing life, alter the way you see story (in books, movies, TV, or plays) forever. You can never got back to NOT understanding it because in these 278 pages Brooks lays out the core foundation of good story, without which you don't have a prayer of getting published (unless your Tarantino and sold your soul to the devil).

The book covers (as the title implies) the 6 core competencies. They are:

Concept
Character
Theme
Structure
Scene Execution
Writing Voice

Now I think we all intuitively understand at least SOME of these things on a gut level. Some better than others. We all have different natural strengths. But what this book will do for you is illuminate the dark corners and show you, not only where the weak spots ARE, but how to fix them.

I cannot say enough positive things about this book. Brooks' conception of story structure (which I initially read in a series of posts on Storyfix, then later in a more detailed ebook) literally changed my writing life. I used to have stellar beginnings and kick ass endings and schlumpy middles. I used to refer to it as The Dreaded Valley of the Shadow of the Middle because I was lost. My friends, now I am found. These concepts lit the way so thoroughly that the section of the book I once dreaded now I LOOK FORWARD TO.

Every section of Story Engineering has wisdom to impart. It isn't the kind of inspirational craft book you pick up and breeze through in a day or two. It is, or should be, a slow read, one where you take your time reading through and really think over the content, applying it to your work. Then you'll want to read it again. You'll want your sticky tabs, highlighter, and post it notes handy when you read it. Mine copy is starting to look like a porcupine. But hey, I can attest, the binding is good!

I'll stop waxing poetic here and just end with this: BUY THIS BOOK TODAY.

Presents itself as offering a kind of formula for writing stories which might put you off, but it is actually about the underlying principles of story telling. Very, very useful.

Excellent information and analysis, which I saw in action immediately in the new James Bond movie, Skyfall. Clearly written. Suffers from author's arrogant often derisive tone, an overly long introduction, repetitiveness, and so many extended analogies to food, sports, and airplanes, that it begins to feel like he just didn't have enough material for a book-length monograph. Nevertheless, some of the best information on successful story structure that I have encountered, and I've read a shitload of these books.

This book is helpful in such a practical way, I went through it like a workbook. Every few pages, I'd stop and return to my story to work on it, using what I learned and the notes I'd taken. The book is broken up into sections for each of the story competencies. The Concept section is especially helpful, in a practical way. Although I understood that concept was more than a story idea, I now have criteria for assessing story concepts for their viability. The idea of writing "what if?" questions for each of the Plot Points is genius. I applied it to my work in progress and it showed me how the story concept had followed through in the story outline. The Character section is phenomenal. It improved my characters in my WIP as I read. I found where my hero's arc was lacking. Even more so for my villain. The idea that people are driven by resentment struck me. It laid a clear path for character development for my antagonist. Also helped my structure -- not too much backstory in Part 1! The Structure section could have been old hat, as I've read his ebook and been a regular reader of his blog for over a year. But it had so much more. Details on foreshadowing, on stakes, on all of it. It wasn't a rerun. For many, this will be the newest part, and he takes time to explain all of it. I couldn't wait to get to the section on Scene, because I'm in revision right now, and I felt I really needed that section. I gained clarity on the idea of mission and pacing for a scene. Characterization can be a secondary mission for a scene, but not the primary. I'm now able to identify scenes that have no purpose but "characterization" and get them some purpose or send them packing! (Although I still wonder if foreshadowing counts as moving the story forward enough to be considered a mission in itself.) The revelation of the cut-and-thrust technique is phenomenal. I now aim to end as many scenes as possible this way, and I'm using the scene checklist for every scene! The section on Writing Voice was comforting and perhaps the least new. It's more of a message of 'don't sweat it,' similar to the message from his blog. 'Less is more' got the message across well and is easy way to remember it. The Beat Sheet section was a helpful review of that wonderful tool, less new since I learned it first at his blog. I have a beat sheet for my WIP, but I was glad to be reminded that I can compare it to a similar published example to help me figure out what is missing. Overall, this book reads like a workbook, with such practical advice and tools, it will be reread by many readers, I'm sure.

This book outlines the basics of writing in a well written, easy-to-follow way. If you are just getting started with writing, this book will provide lots of advice on how to write successfully. If you have read multiple "how to write" books, then this book is probably not the one for you. Overall, I thought it was fairly interesting and concise.

Wow. This book blew the doors off my concepts of storytelling by taking me to the practical step-by-step approach to planning a story. Satisfying reader expectations and surprise can both be achieved through careful design of the story.

Mr. Brooks appeared to spin his wheels in the initial chapters of This how to book. If you are reading his book, then I think you have the buy-in your story needs to be engineered. I feel he repeated himself several times, but once he got going, his advice was very helpful. He made his case as he described how to use the six competencies to create a novel. Even if you know that you will never outline a book and plot it out, you are a tried and true pantser (see how I went round and round), this book is still worth the read.
He lays out the case well that you need a strong structure for any story. In that he was through. He described well the 4 part structure of story- the opening, the first plot turn, the climax, etc.
Like a lawyer trying a case, he explains why the story must go that way and why the six competencies are vital. He doesn’t convict non plotters, though. He just warns them to check and make sure you have all the things checked off (and yes he has a checklist). He also warns them that they are dooming themselves to multiple drafts.
He gives his argument that you should outline before writing. That you will need little revision if you do so. It is a strong one.
There are many amateur writers. Why are they not professional? I suspect that Mr. Brooks is right. Agents and publishers are looking for those components he teaches us in that book. And that the famous writers have them.

This book starts out as such a hot mess I was initially baffled why this title is rated so highly and recommended so often. The writer repeated his mantra of "6 core competencies" with such regularity he came off as a snake oil salesmen on the TV shopping channel trying to sell me on the Ponds Institute's Seven Signs of Ageing. And what's with all the elongated metaphors that back up on each other? Not to forget the cryptic rhetoric on ideas versus concept versus something else or other. Honestly, it used a lot of words and said very little. Ironic considering the notion of a Hook is such a key point in story structure.

So this book is not without it's flaws, but I still rate it a solid 5. Huh?
Like a plane out of clouds, when the initial burst of waffle dissipates and Brooks get's down to explaining, in detail, his concepts, this book is very very good. It works for me, cos I like to have plans and structures before I can put my mind to something.
I've already made my own checklists and cheat cards based on the information Brooks has in this book. The chapters on story structure alone are worth the price. I got so wrapped up in those I'll have to go back and review the character traits.

Which brings me to thee other flaw that made this a far more difficult read than it should be. The concepts in the first half of the book constantly refer to and link to concepts in the later structure part of the book. It would have made more sense IMHO to put the structure first, so the concepts of character could have been slotted in far easier. Well, I thougth so anywayy :->

Because of the difficult writing style early on, I'm not sure I'd recommend it to people who are made keen on jumping in straight away and starting their grand work. Perhaps read something like K.M. Weiland's Outlining Your Novel first, get yourself off and running first, then double back to this one. I fond that grounding benefited me.

Anyway, I took a lot out of this book, and if I ever am able to write my own novel one day, I think it is this book to which I will owe the most to.

As someone with a technical bent, I found the story "engineering" approach to writing very appealing and informative. I will hold off on a full review until I try writing my first novel using Larry Brooks' advice :-)