screw tightening the rewrite

A good friend of mine, and playwright, Matthew Paul Olmos, is working towards the presentation of a new play of his, “the nature of captivity”.  It has been workshopped and developed as part of the prestigious Resident Artist Program at Mabou Mines and I have been lucky enough to watch this script transform over the last several years from being almost unbearably bad to becoming one of his most solid, informed, challenging, and well crafted pieces of writing.

What then to ascribe to ascribe this transformation?  Part of it is due to, no doubt, the fantastic actors, directors, and designers who he has had working on it and forcing it and him to grow the script, story, and writing to fulfill itself.  Part of it, though, is also due to the enormous effort that has gone on under the skin of the play; Matthew’s fundamental rebuilding of the framework, his execution of the second act, and his writing, rewriting and rewriting again has lifted the script into a new and exciting place.

In a recent interview with Adam Szymkowics, Olmos talks about the process of what it really means to rewrite.  I here quote extensively from Matt’s answer to one of the questions:

Something I’m beginning to learn the long way is to not only embrace questioning, but be willing to make changes afterwards.

It is very easy, sometimes, to come up with a pretty good first or second draft of a play; you have many moments that work, there is an overall arc to the piece. All in all you think to yourself, “this is decent.” And in many ways you are happy with it. And in your own arrogant way, you think to yourself, “It’s already better than half the shit out there.”

And hopefully, if you are doing your job, you’ll work through the script with a director, actors, etc., and listen to them when they ask you questions, challenge what you’ve written, and communicate to you what they are getting from the piece. You’ll create an environment that aims not only to give you feedback, but asks every person in the room to ask really deep questions about what it is you’re doing with this play and what it means in the world around us.

And then there’s the playwright back in their bedroom, or barstool, with all these notes. And you begin to read over your script again, and some of the changes you have been thinking over…they just seem so big. And you become afraid to mess with the parts of the script that already work. So you begin to just only tinker. Or clean up certain scenes. You begin to question how well a reading went, and theorize that is why certain parts didn’t work. Perhaps you’ve already rented a space, or scheduled a public reading, and you think to yourself that with this one talented actress or this one skilled actor, the script will fly regardless.

I find that, often, writers are too afraid to turn everything they’ve written onto its head and address the true problems inside it. We don’t want to damage the sections of the piece that already work. So we try this patch’job, or pretend the missing pieces will not be missed. Or we think that the story we are telling doesn’t need to go any further. That this one aspect of whatever topic we’re writing about is enough. We let certain blames fall onto the characters onstage, as opposed to digging deeper and presenting a play that discusses why those characters are flawed to begin with. We let our script run along the surface because we are too scared and too lazy to try to write something much more complex and difficult.

It is our job both as writers and as people to always question, but not to stop there. Rather to dig into ourselves for answers, and when we find them, to have the courage to completely disassemble something we’ve worked so hard on. To not settle for something good, but try for something that scares the shit out of you instead.

What he’s talking about is essentially the much discussed screw-tightening vs. redesign of a site that we all know from the startup world to be so deadly to ideas, innovations, and iterations of product.  Read more about it from Chris Dixon here and Charlie O’Donnell here.  We spend our efforts messing with the small stuff because it’s too scary to get in there and do the work, the real work, that needs to be done.  We settle for something good and let the things that scare the shit out of us escape.

From Josh Porters Metric Driven Design Presentation

It is an entirely human inclination, no?  It makes sense that we shy away from that nagging voice in the back of our head that there’s a better way to write the second act and instead focus on optimizing a scene in the first act that gets some good laughs.  Maybe it is because we have so much at stake.  In our art, in our companies, and in our lives and loves, hitting the next, biggest known, hardest challenge is a task of incredible difficulty but which, or so we are told, promises untold rewards and success.  I’m not sure where I come down on hitting the global maximum in the meta projects of our lives, but it certainly makes sense in the process of art and business.  Chris Dixon and Charlie O’Donnell probably don’t know the MPO, and their lives probably couldn’t be farther apart, but here they are, attacking the same issues and hopefully inspiring both themselves and others to make the scary decisions and push towards that next level.

Performances of “the nature of captivity” are March 3 through 7 and are free. All you have to do is RSVP to rap@maboumines.org.  For more info, check out Mabou Mines and Matthew Paul Olmos’ website.  I’m going on Thursday, maybe I’ll see you there.

 

 

how to give and take feedback

these are my 5 rules of giving good feedback as a playwright to a playwright:

  1. be honest
  2. be specific
  3. be complete
  4. use red pen
  5. make their play work, not their play yours.

i love giving feedback.  sit down, have a little jamesons, and dive into a play, read it a few times, then have some more jamesons, take up that good bright red pen, and dive in.  every page covered, marked, cut, edited, annotated, questioned, exclaimed; monologues written on the back pages and a script well and goodly used.

and then the best part.  sitting down with your friend, sharing some drinks, and dissecting it.  maybe it takes two hours, maybe 4, maybe more.  but in the end, you’ve both got a good buzz on, you’ve covered a lot of ground, and the script is at a completely different place than it was a few days before.

but how do you take good feedback?  that’s probably even harder than giving good feedback.  luckily, there are also five, easy to remember rules, that i always try to follow.

  1. Shut up
  2. Shut up
  3. Shut up
  4. Take Notes
  5. Say Thank You

if i’m talking when someone’s giving me feedback or critique, that means i’m not hearing the feedback or critique.  when i debate someone’s critique, i’m not hearing it.  when i tell them they don’t understand, it’s because i don’t understand what they’re telling me or why.  i try to take a moment, stay quiet, and really really hear what they’re talking about.  why did they get lost, why did they get confused, why did they think the main character was dead, when really they were just sleeping?  is that a good confusion to have or a bad one?  i take a lot of notes, because i know i’m going to forget what i’m thinking when i’m listening.  and a lot of times, someone will say something that will inspire a whole tangential new idea, i need to have it down somewhere or i know it’s going to be lost.  and lastly, its not always fun doing all the work that’s needed to give good feedback, and it’s not always fun giving it, and it doesn’t hurt to say thanks.

and what’s this have to do with websites?  a design deck is the same as a script.  a demo from a developer is the same as sitting with a director for a run through.  the give and take between VCs and founders, is the same as figuring out your marketing plan for your production.  these are all highly collaborative processes, which require being both sides being able to give and take good feedback.  successful technology for successful business happens through the interaction of many disciplines, through many people and many stages, all of which involve creativity, communication, and the invention of nothing from something.  just like a theater production.

having just made this connection, i see that there are a lot of missed opportunities i’ve had over the last few projects to give and take good feedback.  this is not an error i plan on making going forward.

(this post is part of an on-going series about the similarities theater and tech startups)

  

startup lessons from the ny theater world – an intro.

a little on the deep background.  firstly, i am not a playwright.  as much as i may like to fancy myself as one, i don’t.  because the one and only requirement for calling oneself a playwright is that one writes plays.  i don’t write them.  i have written them.  i have studied writing them.  but i don’t write them.  my friend matthew paul olmos writes them.  i don’t.  further, i am not a producer.  likewise i have produced, and have studied producing , but i don’t produce them on an ongoing basis.  my friend jerry bruckheimer produces.  (just kidding, he’s not my friend.  but jerr – if you want to be, drop me a note!)

over the last several months of working on my startup, i have been amazed, intrigued, bemused, at how similar the process of building a consumer internet application is to producing a play.  so i thought i’d sit down and write a little bit on it, try to organize some thoughts.  on the whole subject.  see what happens, how it follows, etc.

but first, some coffee time.