How to Give NotesComplications Ensue
Complications Ensue:
The Crafty Screenwriting, TV and Game Writing Blog




Archives

April 2004

May 2004

June 2004

July 2004

August 2004

September 2004

October 2004

November 2004

December 2004

January 2005

February 2005

March 2005

April 2005

May 2005

June 2005

July 2005

August 2005

September 2005

October 2005

November 2005

December 2005

January 2006

February 2006

March 2006

April 2006

May 2006

June 2006

July 2006

August 2006

September 2006

October 2006

November 2006

December 2006

January 2007

February 2007

March 2007

April 2007

May 2007

June 2007

July 2007

August 2007

September 2007

October 2007

November 2007

December 2007

January 2008

February 2008

March 2008

April 2008

May 2008

June 2008

July 2008

August 2008

September 2008

October 2008

November 2008

December 2008

January 2009

February 2009

March 2009

April 2009

May 2009

June 2009

July 2009

August 2009

September 2009

October 2009

November 2009

December 2009

January 2010

February 2010

March 2010

April 2010

May 2010

June 2010

July 2010

August 2010

September 2010

October 2010

November 2010

December 2010

January 2011

February 2011

March 2011

April 2011

May 2011

June 2011

July 2011

August 2011

September 2011

October 2011

November 2011

December 2011

January 2012

February 2012

March 2012

April 2012

May 2012

June 2012

July 2012

August 2012

September 2012

October 2012

November 2012

December 2012

January 2013

February 2013

March 2013

April 2013

May 2013

June 2013

July 2013

August 2013

September 2013

October 2013

November 2013

December 2013

January 2014

February 2014

March 2014

April 2014

May 2014

June 2014

July 2014

August 2014

September 2014

October 2014

November 2014

December 2014

January 2015

February 2015

March 2015

April 2015

May 2015

June 2015

August 2015

September 2015

October 2015

November 2015

December 2015

January 2016

February 2016

March 2016

April 2016

May 2016

June 2016

July 2016

August 2016

September 2016

October 2016

November 2016

December 2016

January 2017

February 2017

March 2017

May 2017

June 2017

July 2017

August 2017

September 2017

October 2017

November 2017

December 2017

January 2018

March 2018

April 2018

June 2018

July 2018

October 2018

November 2018

December 2018

January 2019

February 2019

November 2019

February 2020

March 2020

April 2020

May 2020

August 2020

September 2020

October 2020

December 2020

January 2021

February 2021

March 2021

May 2021

June 2021

November 2021

December 2021

January 2022

February 2022

August 2022

September 2022

November 2022

February 2023

March 2023

April 2023

May 2023

July 2023

September 2023

November 2023

January 2024

February 2024

 

Wednesday, June 11, 2008

McGrath reposts his fine essay on how to give notes. The key: rather than telling the writer what to do, challenge his or her assumptions. Why did they do it that way? What were they trying to achieve? Is that what you, the buyer, wanted to achieve?

The best division of labor is for the buyer to decide what he wants the result to look like, and to ask the writer to figure out how to get there.

In the US Army, the commanding officer decides what he wants: take that hill, relieve that battalion, stop that enemy assault. He leaves it to the guy or gal leading the troops to decide how to take the hill, how to relieve the battalion, how to stop the enemy. They are going to have to do it, after all. They will spend ten times as long pondering the how as the CO has available. They are closer to the material: the soldiers, the terrain, the equipment.

Micromanaging from the top can lead to spectacular failures. The Spanish Armada failed because King Philip of Spain, a landlubber, insisted that his admiral follow his orders precisely -- orders written several months before the battle. The Iraq invasion of 2003 turned into a debacle because the Secretary of Defense, who had never been in combat, was micromanaging troop deployments.

The best notes say: "we want a wham-bang opening," for example; not, "when Nick gets to the bridge there should be snipers and they should be shooting tracer bullets at him." The best notes come from being a great audience member who understands his own reactions: "I want to be pulled into the story viscerally before I even understand what's going on."

The most challenging notes are those which don't make clear what exactly the note-giver is looking for. The more prescriptive the note is, the harder it is to parse. Why does he want snipers? Is the opening not scary enough? Does he want the opening to take longer? Did the note-giver see a movie with cool snipers and he wants something like that? Are we appealilng to the Halo crowd?

It takes a lot of restraint to avoid giving writers unnecessarily specific notes. Everyone in this industry wants to be creative. The writers are having all the fun. Execs want to share that fun. But execs: you will look like a genius if you simply make clear what results you want, and let the writer get there by his own path. The results will be much fresher, and more coherent, too.

Writers: you need to address notes, but you don't always have to take them. Don't be afraid to ask, "what are you looking for, here, exactly, because I may have another way to do this."

Obviously when you're writing for a director or an animator or a real creative producer -- a Zanuck, a Spielberg, someone who is truly taking part in the creation of the project -- then the situation changes. If Spielberg wants snipers, give him snipers. On BON COP BAD COP, the director had entire action sequences he had mapped out in his head; my job was to happily write them down and marvel at how fun they were. But even in this case, don't be afraid to ask what your creative collaborator really wants when he asks for certain details. You may be able to come up with something better, and most creative people are open to a better solution most of the time.

Labels: ,

0 Comments:

Post a Comment

Back to Complications Ensue main blog page.



This page is powered by Blogger.