Some Lessons I Learnt
After going through this production as in-charge, I have learnt some, if not more, valuable lessons. If you are going to lead a STOMP production, you’d be interested in this post.
Avoid 2 big ESS back to back. Peanut Butter Banana, a.k.a PBB, was the May ESS. Freedom Disorder, a.k.a FD, is June ESS. To have 2 ESS back to back have certain impacts. For one, when I planned the rehearsals, I can’t start using Nexus Auditorium, because the PBB performers and technical crews were using the Auditorium, especially in the last 2 weeks of PBB. FD performers could only start using auditorium for rehearsals after May. Clash of resources, i.e. technical crews and usage of Nexus. Try and book the available rehearsal rooms ASAP. I suggest at least 3 months ahead.
Why must I insist on using Nexus? STOMP is a musical production. We need to hear the actual sound to know what we are doing. Drama alone can be rehearsed anywhere else with space and imaginary props. STOMP can’t do without props. Given the large amount of props (props also refers to our “instruments”) we have, it is a challenge to transport out of Nexus or to store it out of Nexus unless we have resources for transportation van, driver, and storeroom… not to mention an external rehearsal venue.
Should ever anyone among us attempts to have a such STOMP production, I have some advice of my own.
Seek advice from predecessors, and various experts. Gain support and seek support from your leaders and production team. That includes performers, pastoral leaders, predecessors, and technical crews.
Start performers recruitment/selection as early as possible. If you can do publicity for the recruitment, it’d be even better. In this production, PSPT selected the performers on short notice. How short? Mid-May. That’s about one and a half month before. After about 2 weeks of performers’ confirmation, 3 performers requested drop out of the performers. I had to modify the script and rearrange the stage positions. It’s not easy to find replacement. to Now that I think of it, I think I should have selected people who can guarantee availability and committment, and fulfill performance criteria, e.g. rhythmic sense, at least 3 months ahead ahead! It is important to brief the expected commitment level.
Fix the “drama” script asap, and expect many modifications along the way. When we were planning this production, the estimated (more like guessed) time length of performance was about 20min to 30min. I find that the skeleton of the story plot is pretty much kept simple and easy to flow over. However, the STOMP details couldn’t be planned detailedly as to “how does what rhythm after how many bars”… This is because of the lack of expertise and experience.
FD is PolyDINS’ first STOMP production, and we try to incorporate a story plot in it to deliver a message across. Such an attempt is almost like a fusion of drama and STOMP. Regarding this, some people who initially heard about Freedom Disorder asked, “Is this going to be a musical?” My answer to this: FD is primarily a STOMP performance, and the drama part will have as little oral conversation as possible.
Further challenges I encountered.
Availability. In so far, I only have 3 full attendance of the 8 performers during Nexus rehearsals. On one occasion, 2 person were sick. On another occasion, some have NS guard duty, or school tests on the following day of rehearsal. As some of us are working adults, they are only free after 6pm, usually. Even though Nexus may be available for booking in the day time, we can’t rehearse without the actual performers. We tried to counter this challenge by having temporary replacements of each others’ roles. The advantage is we could proceed with the drama and rhythmic design. The disadvantage is we have to teach the actual performer what the temporary replacement did, and the feel will be different when done by different person, somehow.
Venue. For the initial rehearsals of scene 1, we used SMU’s public open space to STOMP. We used poles and sticks and imagined the tom and crash, and every other props. We also used SMU for planning of plot scenes together. We had about 5 meetings at SMU, and 4 rehearsals at Nexus itself. We used only 1 Thursday for full dress rehearsal, and technical run though of the whole performance. It’s crazy.
Props. It is good to keep in constant communication with the decoration and props in-charge. Bing Chuan did an awesome job in making the decorations and providing he props. For this STOMP productions, the props list is considerably long. I kept modifying the list, such as adding and dropping certain props. Bing Chuan often initiates to ask check with me for changes and updates in the props. He did a lot of research in sourcing for good cheap, if not free, attires, and literally made the props for us. He travelled places on his own bike, and spent late hours making the props, even when he has work on the next working day. He even tried to apply for leave and off just to avail himself. He has a supportive spirit, and I know I can trust him with the tasks I requested of him. If he were to say he cannot provide the props, I’d believe him instantly because I know he has already thought through all available alternatives and possibilities. Not only that, he can balance his work and personal life. His team will be under-affirmed even with my mention here. Bing Chuan displayed one of the best support and role model I ever know.
Even more challenges I faced.
Due to the shortage of time, the selected performers are mainly PolyDINS service duty musicians. As we only had 2 bands, each week a band will be alternated to be on duty. In the end, we had to mix the band with those not on duty, and some managed to be out of the STOMP performance. If possible, try and avoid having duty musicians as the STOMP performers.
As I am the head of PolyDINS Communications, a.k.s Beat, I am responsible for the publicity of FD as well. I figured I can’t juggle everything on my own, so I asked for help from my core team. I put Valens in charge of the publicity, and tasked her of what I expect. Then, we carry out our job respectively. I am grateful for my core team… all of them.
Alright, that’s about the main stuff I learnt. There’s definitely more, but I ain’t writing them down here. This post is long enough. If you wish to find out more, you may contact us.