The first step for me is to get motivated.
If I can find a reason to get excited to start something the next steps become so much easier. This is usually a moment in a show that catches my imagination while I read it, or even trying to solve the puzzles that the playwright gives us. Such as in Urinetown, I found that my motivation for the show was finding out what made each side tick.

The second step is to gain my own direction.
Once I have solved the issue of getting motivated I need to find a problem to solve. I can usually do this by defining parameters by which to contain the design, this creates an isolated problem in which I can work from many directions to find a solution. To define these parameters I like to break down ideas in the show   into one concise, poetic statement that defines some aspect of the show (action, mood, themes). I can use this as a grounding for my view of the show while talking to designers and directors.

These two steps lead to a great place jumping off point to create any kind of design. It boils down the show to the essence of what is happening to constrain it to the text, while be flexible enough for the director to make decisions on how the overall productions will look.

I have found an issue with this beginning process, I will create an analogy within the concise summary statement that is difficult to alter if the director views the show fundamentally different than I, which of course plays into my natural stubbornness.

There is a lot of hype about the Arduino in the theatrical world right now. The open source microprocessor provides a platform to base new design ideas and different solutions for old problems like triggering sound effects on an action. The Arduino allows for electronics that can be completely customizable to a large extent, and is very affordable, however at the lower price it starts to suffer from functional shortcomings.

First and foremost being memory. The chip can only hold so much information on it, and this isn’t just how large the program uploaded is, but also the buffers and allocated memory that the program needs to run. To make an LED blink is a simple program, however when we get into more complicated actions, such as communicating through midi or DMX the program becomes much more complex and needs to hold large amounts of information.

Secondly, the timers and the logic has some latency problems. The timers can only be so accurate and when pushing the processor the it tends to slow down in its computation, like an computer.

New solutions are emerging however, the Raspberry pi (http://www.raspberrypi.org/) is the next step. This board is more like a computer. It has a graphic user interface and allows for USB connections and ethernet connections built in. The board boasts a better processor, better networking capabilities, and easier integration with store bought technology.

These both have their Pros and Cons, but in a world that is becoming more integrated with technology and where more people are willing to learn rather than buy, i foresee these boards become very powerful, very quickly, and having many more uses in theater than we know now.