Theater For The Future

Patrick over at BackstageJobs has a very enlightening new feature (oof. accidental pun.): an interview with longtime Chicago electrician and more recently hot shot Lighting Designer Keith Parham.

I’m curious: How interested are you in hearing about folks behind the scenes? Designers, directors, dramaturgs and anyone engaged in navigating an artistic process day by day are endlessly fascinating to me, but I consider myself biased.

First of all, thanks to Jacob Coakley at Stage Directions magazine for the editor’s note that mentioned my Chicken of the VNC post - and more importantly the idea that sharing our skills and acquired knowledge is a worthwhile endeavor for us all. For any of you just joining me now from Stage Directions, check out more of my sound design goodie bag, and feel free to ask questions.

So Context. As in: the context that we operate from when we create artistic work or artistic commentary. And the context of others, and the context of others and the context of others. Thank you, THANK you, gentlemen, for sharing your context.

It is so helpful and enlightening to understand the background of an artist. Half the show for me is leafing through the program and remembering the last show or conversation I had with an artist and understanding the work that I see in the terms of what they’re working on and exploring now. Because of this habit, I’m a true fan in the Long Tail sense of the word of many actors and designers in Chicago, and I’ve caught some moments that I’ve carried as utterly magical that I think most audience members don’t normally appreciate - because they’re moments of improvised learning. By understanding the background of an artist, you can catch the moments when the artist suddenly “gets it,” and pushes past their previous limits. I don’t really enjoy divorcing the work from the artist. That feels like amputation to me.

I had a great first face-to-face conversation with Paul Rekk at the Jeffs last night, which I hope was helpful for both of us. His post a few days ago helped clarify for me the reasons for our divergence of perspective - we come from radically different backgrounds.

I grew up in Amherst, Massachusetts. The status quo there - the one I felt compelled to rebel against as a teenager - was one of alternating impotent liberal wishful thinking and cutting 90’s progressive cynicism. Amherst, in case you’ve never heard of it, is famous for its five colleges in close proximity that you may have sensed recently in the shadows of Scooby Doo reruns, its horribly authentic yet utterly disconnected Belle, and the unfortunate human rights record of its namesake, the Honorable Lord Jeffrey. Most alarming to my adolescent brain was that most of the folks in this extremely politically active town ignored the basic precept of fellow Masshole Tip O’Neill: “All politics is local.”

In Amherst, all politics is International. The town is overrun by politically astute 18 - 24 year olds all running away from the demands of their families for the first time in their lives - and the professors and administrators that make a comfortable living off them. The local community might as well not exist as far as the colleges are concerned. I grew up a townie in a school filled with the sons and daughters of professors - which means I was on the empty pockets side of intellectual gentrification. I wrote my early plays about the old men in greasy spoon diners, trading the real wisdom of the world as the world sped up around them. The encroaching property taxes that made retirees leave their hometown after decades even went to prop up that old museum piece of New England democracy - our “functioning” public town meeting that ‘led’ our town through a process that resembled permanent filibuster, while the real power was held by a permanently appointed Town Manager. Imagine a City Mayor appointed for life! Oh wait… And most folks my age were too busy making a show of rejecting the idea of establishment and re-rejecting the disestablishment. So they’re all far too busy to engage with the actual establishment - they wanted nothing to do with local reform or local community. They would rather buy the Che Guevara t-shirts if you know what I mean.

And so of course I ran from my community in the end. I moved to Dallas and saw the most well-SUV’d part of Texas mobilize for the War on Terror by purchasing ever larger and more reckless tanks of gasoline while embracing a skin-deep caricature of patriotism. I watched my family with my electric binoculars fight to stay united, grow up, and not lose their homes to the social will of my hometown. And I found another family, an urban family, and a place where I felt useful. And that’s when I stopped my adolescent self-pity in the face of my own terror and self-recognition, and saw the poison I drank in each lost connection.

This is my context: I sense a deep hypocrisy in the cynicsm of willful disconnection and disassociation with those connections that exist between us. I deeply value progress, but the advocates of progress became in the nineties an incredulous kind of lazy and entitled. And then we saw the consequences of that half-assed progressivism - as part of the country claimed we never had any values at all and took over, running our values into the mud.

I think that’s turning around now, but we’re kidding ourselves if we think our generation isn’t going to face an onslaught of responsibility now that we’re taking over the wheel, institution by institution. I feel a call to service these days - to not repeat the mistakes of the village that raised me and taught me - how they forgot their roots and their neighbors in their push for progress - while also upholding the values of that village in the face of eroding American values and eroding American justice that we all feel. When I first moved to Chicago, I think I wanted to escape from the erosion of the places of my past - but even here, I don’t feel safe from eroding values and eroding justice. I don’t feel safe from complicity in the many injustices of this country and this world simply because I’m in a place where people share my values.

We’ve all felt that kind of powerlessness in our lives - the question of “why do this at all? I’m not arguing a legal case that will affect a life. I’m not fighting hunger or disease or poverty. I’m not relieving disaster victims.” Well, to disengage from that responsibility simply because we are powerless to fix large social problems as individuals is not a valid solution to me. In my context, the way to make an impact on the world is to practice connection. It is to practice and value detail in craft, to create quality in all our lives. This practice fights that sensation of powerlessness in a human-sized way, to create a real, vital community through our collective creative work and our ability to listen to each other. Communities are built individual by individual, and piece by piece - and it’s communities that have the ability to create change.

Death, decay, and destruction take care of themselves. Growth requires food, water, and a big bright light shining on it. In my context, if you’re not re-building, you’re damaging.

In my context, you can choose to create and support the craft of your peers and neighbors on a sustainable scale, or you can tear down and destroy - models, ideas, and work - and leave an empty shell of a wasteland. That’s not a clean slate as far as I’m concerned… It’s a world where positive energy was stopped and paved over by negative energy into a place where it couldn’t grow anymore.

And is the crux of some of our online arguments, no? In other contexts, harsh criticism is valued as pure truth. It’s valued that way because the folks who have that perspective have been witness to comfortable lies for too long. They see how cooperative initiatives can be co-opted by self-promotion, the PR game, and profit. In their context, the ultimate sin is self-censorship and watered-down art in the name of decorum.

I know that this hope for community and mutual support - not dishonesty, support - comes off as wishful thinking in our context-less world of the internet. Here in Chicago, where my Yankee roots don’t share a lot of the same background as the midwesterners who have had to tear down some actual injustice and external ignorant destructive forces to get to play in this White City, my all-for-one-and-one-for-all message comes up against some legitimately divergent viewpoints. Which is fair, and I’m eager to learn to be at better peace with it.

My context informs my work: The theater I have chosen to call my home has a very clear mission that speaks to these beliefs: we “create intimate, animate theatrical experiences which renew both artist and audience.” I also consider teaching and opening doors for younger artists or artists without my experience to be a cornerstone of my life’s work. Teaching for me isn’t about giving the right answer, it’s about asking the right question. It is about testing ideas, but also understanding them, supporting them and letting them thrive on their own terms.

So deliberation in the theatrosphere is not about finding the penultimate truth for me, because I don’t believe in those lofty ideas on a hill. I believe in perspective. I believe in seeing each other’s work, and seeing each other work. I believe in growing within and embracing our own context.

All politics is local.

Laura at Trailing Spouse Blues tuned me into this article which is just a wonderful working example of the theory at the core of this blog: that an open sharing of information leads to a “bigger pie” - more influx of thought, funding, and participation in theater, which leads to a reinvigorated and strengthened theater community.

When you share your knowledge you strengthen your industry and gain unexpected rewards.

I’m certainly not suggesting Coke publish the secret formula on their web site. But for a creative person sharing knowledge, especially business knowledge, will help the community has a whole.

The more knowledge amateurs, students or beginners have the greater their ability to make quality decisions. People can’t be forced to follow best practices or charge a professional rate for their work. But, more often it’s a lack of knowledge and experience that leads to such poor decision-making.

It’s hard to let go of the knowledge that we think is at the heart of our success. The note-taking system I detailed in the last post is an example of something that I do to help keep me as organized a sound designer as possible. I think it makes me better able to cope with the demands of a sound designer - where you must overlap many shows at a time in order to pay bills. At those times, it’s important to remember that our knowledge - which is the sum total of our history of choices, experience and conclusions of that experience - is both valuable to a newcomer, but it is also build and really only works for our brain. People can take your open-source knowledge and they necessarily will reshape it to their purposes. Virally, new thoughts and solutions will be created that you wouldn’t have dreamed possible. At the same time, those new thoughts wouldn’t have been possible without the seed of your own knowledge.

Sharing your best practices extends the collaborative ethos of theater into your business, not the other way around. It doesn’t guarantee the success (or domination) of a particular individual or a particular company, because it doesn’t guarantee ‘credit’ - it strengthens the entire industry first.

When I first started designing, I took handwritten notes. Scribbles, really. Each note said something like “dloor up 7 after…” I have horrible handwriting under pressure in the dark. Also, I didn’t write very quickly, so I’d leave a lot of trailing sentences as the play progressed and new cue mishaps grabbed my attention.

Frankly, I didn’t yet have a process, and I was designing in a panic. I used notes as shorthand to trigger my memory of what happened particular run, and then doing the notes meant reconciling that memory with the director’s divergent memory and then taking an appropriate measure to correct that cue for the next run.

The problem with me and this method became clear the first time I designed my annual summer juggernaut - the ten repertory shows of Cherubs. Each show ran an hour, and teched in an hour and forty five minutes. After tech, I would have one dress run to make any last adjustments, and then performance. Each night you tech two shows, and then the next night you tech two more. At the end of my first week of Cherubs tech I had a pile of incomprehensile scribbles like “Fade out the drone when she does that thing upstage” with little memory of the play itself. I needed a better way.

And I didn’t just need it for Cherubs. I looked at the designers whose careers I wanted to emulate - Andre Pluess, Lindsay Jones, Ray Nardelli, Josh Horvath. These individuals are unbelievably prolific, if you haven’t noticed. I think Lindsay pulled off something like 30 shows in 10 states last year. They worked everywhere, all the time - in Chicago and regionally. In watching their processes, I noticed patterns in how they organized their notes, cues, and files into standard formats and structures no matter how different the show was.

I experimented with excel spreadsheets and text files. The disorganization and lack of clarity continued - though I did notice that I had a speed increase and a greater percentage of complete sentences because I’m a faster typer. So I was capturing more of the same bad information I worked on self-discipline in the moment and looked into some preliminary shorthand lessons. It didn’t click with me. New problems started emerging as I experimented with new methods - I would bring a level up one day only to bring it down again after sitting in a new seat only to bring it up again after sitting in the first seat again. I was pushing and pulling my hair out.

The breakthrough came for me when I thought about the nature of the information I was trying to retain. Levels. Cues. Moments. Memories of the events of a run. Records of previous runs and notes. Whether I had taken care of a note or not. Notes from a director. Notes for a stage manager. Notes for myself.

I decided to create (ta da!) a relational database and see how that worked for me. I broke the information of my work into core models - cues, subcues (like fades and layered sounds in a cue), notes. Five years later, it looks like this:

Not the greatest interface, but it’s been built incrementally with only my brain, so it works great for me. Notes are in yellow there. As a show progresses, I scroll through my cue list. If I have a note, I just type in one of the yellow boxes and I have a quick pull down menu of basic types of notes to give me some quick context - “Director” means it’s something I need to ask the director. Its direct, and in practice, simple. I should note while the data structure is complex enough for me to use this system in every show, it’s also flexible enough that I can ignore great sections of it when time demands that of me. I really only use the subcue table, for instance, when I run using CD playback shows where overlapping sound files still need to be managed. Computerized playback often makes that paperwork more or less moot, so it just sits there.

By capturing the data I also noticed an immediate benefit - separating the data from the display of that data by taking it off a piece of paper or a spreadsheet freed myself to use the data in new and different visualizations. I could create a new layout that automatically created a cue list easy for a stage manager to read:

Or a quick pull list of notes to do in a hurry:

With six or seven shows and some troubleshooting, it became a system that I trust more than my handwritten notes and my swiss cheese memory. It became a way to freeze those pure, immediate reactions that I have in the space and in the moment and use those to inform my notes. And since I began analyzing the way that I captured information and the structure of the information that needed to be captured, my handwritten notes have become decidedly more disciplined and focused.

But that’s what works for me. What’s important is the way that you structure your own capture. You need a way to capture all the relevant data that you can fit into your bucket, and a way to intuitively and simply filter that information later. We are flawed creatures, and it’s not only possible but likely that at some point you’ll try to fool yourself into thinking you took one action when you took another.

There was another important capture that took place in recent months - the company members of the side project sat down and captured through a brainstorm all the roles and responsibilities of the company so that we could better enlist and provide support to Artistic Director and theater operations superhero Adam Webster. By capturing and filtering the things we did as individuals over the course of a season, we began compiling a bible of simple manuals for tasks and procedures that were involved with running a theater - everything from filing taxes to taking out the trash to repatching the lightboard. We took this information out of our cluttered minds and put it in a repository where anyone can come in and take over, and in doing so the problem of “running a theater” became smaller and more manageable. When you look at the life cycle of company membership, that kind of capturing and filtering process creates institutional knowledge that is the difference between the life of a theater company and its demise.

This is one of the reasons that I think creating a database of Chicago Theater is a worthwhile project and not simply navel-gazing. It is made up of collected and searchable and therefore endlessly useful data. If it is successful, it creates a model for other public resources of data in the theater community that by necessity would be more accessible than say, TCG’s data that Scott Walters used to such great effect. It captures hard facts that can be organized to suit your purpose that day. It allows us to check things that we believe are true (”You know what Chicago needs? A production of Our Town in April 2009!” They’ll never know what hit them!) against the captured data of collected memory that inarguably is true.

On a side note: Speaking of manuals, I’ve been exploring the utterly hilarious Poignant Guide to Ruby in my learning process of the Ruby on Rails programming environment for the CTDB. I think the devilvet in particular will appreciate the use of off-the-cuff cartoon foxes and elves to spice up the process of (yawn) learning a programming language.

When you’re reading and writing a manual, I cannot stress enough the importance of retaining your sense of humor. This is the thing that I often forget.

Some brief updates from the forge:

• Tech is going well. That’s the sound playback software LCS you’re seeing there. It’s pretty sweet - it’s the secret behind the complex sonic routing of things like Disney World, cruise ships, Cirque, and, well, the Goodman.
• You have like three days left to see Vivian Girls. Run, don’t walk, to Theater on the Lake at 7pm. I’m probably going to refrain from actually reviewing work on this blog, because 9 times out of 10 I have some sort of relationship or investment in the shows that I would review, but this show stands out. Dog & Pony’s opus isn’t simply a show - it’s an entire emerging genre of performance, and whether you like the show or not (you will) you’ll leave with your head abuzz with possibility. And no, you won’t be weirded out by the masks. You’ll dig it. Scout’s honor.



• The push is on for the Chicago Theater Database. Dan Granata and I have met with a number of interested parties, and it looks like the database will be beneficial to a large number of projects - and the Chicago community at large - without stepping on too many toes. As a result, I’ve taken the plunge to learn a new web development language, Ruby on Rails to simplify the development of the database. My head is swimming right now in: rake db:migrate Lions, script/generate model Tigers, and script/destroy controller Bears, Oh:My! If you’re interested in the project and less in the building of it, send a note. Why should you care? Because data is important: it helps us learn and know things for sure. Update: No, seriously, our data is important.
• The 10 scripts are in for “Cherubs,” a theater training program at Northwestern I’ve taught at for the past five years - a program that has been formative for me as a designer and a teacher. I’ll be designing these 10 shows in July with the assistance of 160 brilliant high schoolers from across the country (and sound designer/composer extraordinaire Steve Ptacek). Preproduction for 10 fully produced repertory shows built and run by teenagers is obviously an undertaking, of course. So those scripts and concepts have started swimming around in the kiddy pool of my brain with the Ruby and the LCS.
• So, as this season prepares to comes to a close, I’m finding myself knee-deep in delicious theater smoothie. Set to frappe. I’m glad I’ve got momentum as I ride around in the blender - and a full plate of projects that I think will do a lot of good for me, us, and the kids respectively. But of course it all means that posting here will continue to be spotty through June, and then blip out entirely in July as I pull daily allnighters - kind of like that period of radio silence as you round the dark side of the moon. But never fear - the summer always has this gravitational pull that flings me back out the other side with a new kind of velocity.