Throughout the Project MAD series, I’ve already touched on a number of things that suggest how my new City Symphony might approach programming. So to a great degree, I’ve really been talking about programming all along this journey.
Working my way backward – in my last post about the musicians, I talked about giving musicians more authority over programming. I mentioned building a musician-based chamber music series, and giving musicians, particularly the principals, ample solo opportunities. I also talked about integrating composers substantially into the fabric of the orchestra’s life. I mentioned engaging guest soloists on a more frequent or extended basis, allowing audiences to develop stronger relationships with them long-term.
In the post on artistic design, I talked about non-musical elements of production and presentation that would bring traditional symphonic programming more into the 21st century.
In my post on building demand for classical music, I talked about the establishment of a comprehensive City Symphony Music School. All of the possible ensembles within the music school (youth and civic orchestras, choruses, chamber groups, etc.) would contribute participatory programming to the community.
I also talked about the organization presenting other genres of music in order to own the marketshare for live musical entertainment in the community, one of the MAD Foundation’s strategic goals. Presenting other genres of music also extends into dramatic collaborations in dance, musical theatre, and opera. I don’t envision that the modern City Symphony necessarily produce and present opera or dance itself – but it should extend its hand to these art forms through collaboration.
Though I’ve touched on programming factors in many areas, programming is more than what is played and who plays it. Programming encompasses how concert series are put together, when the orchestra plays its programs, and where it plays or distributes its music. In this post, I’m going to explore some of these other areas a step further and introduce a few more of my ideas.
The Repertory Model. After a lot of analysis and thought, I propose the idea that a repertory program model might serve the City Symphony better than the traditional sequential concert set model. However, I wish to note that I do not think that this model would work for the small regional orchestra that plays a small number of programs in single concerts over a season. The repertory model is really intended for an orchestra that plays several programs at least two to three times, as well as presents different concert series (masterworks, pops, chamber, presented acts) in various rotations. The repertory model is also ideally intended for an orchestra that controls its own performance space. I’m a firm believer that in the arts, the company that controls the stage ‘rules the world.’
As to what I mean about a repertory model, I’m going to focus on the traditional “masterworks” concert type first. In most American orchestras, you find a traditional series of concert sets, featuring fully-rehearsed standard orchestral repertoire performed in a set of concerts over one week or weekend. The program changes with each concert set, and then that program is finished and goes away. In the major orchestras, this change of program happens weekly. In larger regional orchestras, the change of program occurs every few weeks or each month.
For my orchestra model, instead of Program A in Week 1, Program B in Week 2, and Program C in Week 3 – each played three times Friday to Sunday, the orchestra might offer Program A on Friday, Program B on Saturday, and Program C on Sunday afternoon. Program A might be a Masterworks program featuring Shostakovich Symphony #5. Program B is a Masterworks program featuring Tchaikovsky’s Piano Concerto #1 with a dynamite pianist. Program C might be the City Symphony String Quartet in the chamber series playing the world premiere of a new quartet and other works. So in one weekend at my City Symphony Hall, one audience member could conceivably hear three different programs “in repertory.” The following weekend, Programs A and B could be repeated, on Friday night and Sunday afternoon respectively, and perhaps with a new Program D Masterworks opening on prime Saturday night.
The Metropolitan Opera, with its protean orchestra, is the best example of a repertory model. They might program a Verdi opera on Friday, Puccini on Saturday afternoon, and Britten on Saturday night, all within the same weekend. All rehearsals for these programs take place during the days behind the scenes. Their musicians seem to have no problem playing different music in repertory at an extremely high level of excellence, too. Once an opera is fully rehearsed and prepared, it opens, and then it runs in repertory for a few months, some even throughout an entire season beyond its initial opening. Certainly, there are touch-up rehearsals behind the scenes for new cast members, new conductors, etc. I can’t imagine that it isn’t delightfully challenging and interesting for the musicians to play different repertoire from day to day. I’ve taken this idea and scaled it down to the typical professional American orchestra that plays similar programs in sets. I believe its not only possible, but it might energize orchestral musicians in ways we haven’t noted in years.
In the traditional US orchestra programming model, production (rehearsal) cost is an expensive and very temporary investment. It’s very expensive for an orchestra to rehearse a program four times in a week only to play it two or three times over a weekend, and then start a new program when the next set of dates come along. I’m not saying that orchestras need to rehearse less: the time it takes to prepare a piece of music is what it is. What I am saying is that I think that this programming practice was built to serve the traditional subscription model of the 20th century, and the model was simply replicated everywhere because it worked. Audiences were conditioned to buy full seasons of concerts in advance, therefore, new programs were produced in succession to serve what was essentially the same subscription audience week after week. A lot has changed in that traditional model, at least in audience behavior. There are fewer full-series subscribers and more “dabblers” who buy choose-your-own concert sets and the really cherry-picky single ticket buyers (like myself) who choose specific concerts and dates according to their preference and life schedule.
It’s well known that the subscription audience has been eroding in America. Don’t get me wrong, I don’t think that the subscription is completely dead, but I’ve been exploring a new way of thinking about those consumers… which will be discussed in my final post on marketing and development. The repertory model would add an element of extra flexibility that would still allow for full subscriptions to be marketed, but it would broaden the opportunity for the single ticket cherry picker to get more programs they want, too.
I also believe that this repertory model is a better choice of programming strategy because of the issue of music critics and their potential positive impact on programming. With theatre companies, single productions are often run over multiple weekends in a run, giving the local critic the opportunity to review the production when it first opens, and publish that review while future performances still exist on the horizon. For great programs, a rave review can potentially stimulate increased ticket sales, if not sell out the run of a show. Spreading performances of one program over multiple weeks also allows more time for a review and that coveted “buzz” word of mouth to stimulate more sales and attendance.
The repertory model could also help maximize or stretch rehearsal investments for programs by getting more mileage out of fully rehearsed pieces of music. Orchestras already do this commonly through what is known as the “run-out,” where a fully rehearsed program is performed one or more extra times in venues outside the orchestra’s home venue, often within an hour or two of the home city, but sometimes a week or two from the original concert run.
I think it is possible that new programs could be assembled using previously played works from previous programs during the season, too, maybe with one new piece added, requiring overall less rehearsal days for the new program. These concerts could be targeted specifically at first time ticket buyers rather than the core patron audience. Most of the music on these programs would be pre-rehearsed, therefore the production cost of that program reduced. I would create concerts featuring “best of the season” or “signature” works from the season, and call it something like the Reprise Series. Again, my goal would be to have the musicians playing more frequently before paying audiences, and stretching the return on investment for fully prepared repertoire.
Let’s look a little further at my earlier Program B – that Tchaikovsky Piano Concerto feature. I return to my earlier point where I mentioned developing deeper relationships between soloists and City Symphony audiences. The repertory program model fits this idea very well. The guest piano soloist could be engaged for a three week residency instead of three or four days, and in that time, the soloist would not only play the famous concerto three times with the orchestra over three weeks, he or she might also present a solo recital in the presented series, engage in educational activities in the City Symphony Music School, and visit a local university to give master classes. This kind of extended artistic residency is something that grants would support: what I believe would be a proper use of philanthropic venture capital.
Also, if the City Symphony gives more solo opportunities to its own musicians, as I suggested it should, then more concertos could be performed in repertory programs that wouldn’t involve engaging a guest artist at all, reducing the cost for guest artist fees and travel.
There’s also the interesting option of engaging different guest soloists to play the same concerto on different nights within the same program across a three-week run, sparking the opportunity for the music critic to return to the orchestra and review the same concert with the new soloist and make interesting comparisons between performances. More press? A good thing. My thought was that if more than one soprano can sing Mimi in the same run of La Boheme in repertory at the Met, I think more than one pianist could play the Tchaik 1 in an orchestral run of that program. In fact, that particular concerto is so popular, that having different pianists play it each time might make core patrons come to all the performances to hear their favorite concerto interpreted three different ways.
The Programming Surprise. I’m also an advocate of programming “surprises.” I realize some purists may not be so amused, but I’m going with it anyway. Audiences love encores, which is one kind of programming surprise. Symphonies could learn a lot from the pop world, where bands come back for three and four encores before sending the fans away with the memory and message of “they did four encores, man, it was ma-jor!” Encores have the benefit of sending audiences away with the feeling they received more for their money in value, they got something special that they did not anticipate happening. That’s the kind of stuff that makes people come back. Some of the encores could be movements or overtures from a new program about to open the following week –possibly inspiring people to buy tickets to that new program, if they haven’t already.
Other program surprises could be a preview of new works that are being premiered officially soon – movements from these new signature works might build anticipation and ease the fear of new music among audiences. I think a lot of the problem with new music and orchestras today is scaring the audience with the very idea of ‘new music’ before they even hear it. If you tell someone there’s something sorta “new” sorta “iffy” before the purchase, they are going to hesitate and think carefully about that risk before parting with their money. My proposal: just surprise them with something “exciting and new” in the concert. As long as patrons get what they pay for and more, it works. We hear new music on the radio all the time without any preparatory announcement.
Also, what orchestra does not print “programs subject to change at any time without prior notice” in their box office materials? Always a wise thing to disclose, I still believe that surprise programming is a potentially effective tool to enhance the audience experience.
Programming Distribution. Finally, I want to talk about the where of programming: touring, recording, and digital media. First, I think too many US orchestras have been confined to their city limits for far too long. One of the reasons for this, in my opinion, is because most of them are cookie cutters of each other – they’re playing the same music in the same way as every other peer orchestra; and relying on their community for their revenue – so there’s sort of an unspoken idea of “turf” among regional orchestras in particular. We have our own symphony, we don’t need to hear yours, thank you very much. The top US orchestras do still tour nationally and internationally due to their stature, but it’s rare that orchestras below the top tier move around very much at all. That’s sad, considering that so many of our regional orchestras perform at extremely high levels on par with the top orchestras, and a lot of them commission new works that may not be heard beyond that orchestra’s premiere program and city limits.
Having an orchestra with signature repertoire of its own, however, creates a touring opportunity that is more attractive and unique, and therefore might open up more opportunities. The City Symphony might bring its new work to new audiences in other cities, thereby not really competing with the Beethoven and Brahms played by the home orchestra in that city. The City Symphony might also extend invitations to other orchestras to visit its hall to perform that orchestra’s special repertoire.
The signature repertoire also creates unique recording opportunities, a real reason to make a record. I would have the City Symphony and its chamber ensembles record and release mostly new works, perhaps paired with some standard rep on the same CD. I would definitely have the City Symphony establish its own signature recording label. Orchestras really no longer need a recording contract with major labels.
Also, the City Symphony should embrace new digital technology to make live performances available to audiences beyond the concert hall. The Berlin Philharmonic Orchestra’s Digital Concert Hall has set this bar of digital distribution very high worldwide, and the Met Opera and Los Angeles Philharmonic’s Live in HD series are on the same track. Other orchestras have made selected concerts available online through their web sites, as their union agreements allow it. I’m not saying that digital distribution should ever be for free, but it should be offered even at a limited extent as downloadable videos for sale on the orchestra’s web site. People should be able to pay a few dollars and watch a live concert after it closes for a period of time. I previously mentioned in my Project MAD series the possibility of streaming concerts live to a nearby local movie theatre, where people could attend and watch the concert at a lower ticket price in a more casual style – ideal for family audiences.
So – while I probably have not covered everything I could talk about in programming design, I believe I’ve focused on particular areas throughout this series where I would invent and combine best practices to develop a new orchestra model that is vibrant, exciting, and most of all, relevant to modern audiences.
Coming up, I will put the cherry on top of the Project MAD cake with my final post in the area of marketing and development, which I’m calling simply: The Membership Model. Stay tuned.
