“Act One: An Autobiography” [Amazon.com] is playwright and director Moss Hart’s look at the long, arduous road that led to his breakthrough hit “Once in a Lifetime.” Designer Michael Bierut calls the book “the best, funniest, and most inspiring description of the creative process ever put down on paper.” It really is a terrific read.
One thing I found interesting in the book is the way the play’s words on the page are often meaningless. The play is slaved over by its authors and rehearsed endlessly, yet it is still almost completely rewritten after it goes in front of early audiences. In this passage, Hart describes why the only genuine test for a play is a real, paying audience.
[Fellow playwright George S.] Kaufman did not hold with the theory or the practice of having run-throughs for his friends or friends of the cast, or even for people whose judgment he respected and trusted. He held firmly to the idea that no one person or collection of persons, no matter how wise in the ways of the theatre, could ever be as sound in their reactions as a regulation audience that had planked down their money at the box-office window, and in the main I think he was correct. There is perhaps something to be learned from a run-through for friends or associates; but more often than not, it can be as fooling in one way as it is in another. I have witnessed too many run-throughs on a bare stage with nothing but kitchen chairs and a stark pilot light and seen them go beautifully, and then watched these plays disappear into the backdrop the moment the scenery and footlights hit them, to place too much reliance on either the enthusiasm or the misgivings of a well-attended runthrough. The reverse can be equally true. however well or ill a play may go at a run-through, there are bound to be both some pleasant and some unpleasant surprises in store for the authore when it hits its first real audience.
It’s the same for plenty of other products too. You can do all the planning you want. You can focus group. You can beta test. You can theorize. You can project. But nothing will ever match the feedback you get from real people, especially ones who are paying to use what you’re selling. Everything up until then is conjecture.
It’s one more reason to kick your project, whatever it is, out of the nest as soon as you can. It’s often the only way to know if it can really fly.
I know it’s tempting to counter, “But it’s not perfect yet!” Does it have to be? Trying to make it perfect often puts a shield up that closes you off from what you need most: feedback. Instead of improving, you wind up delaying the moment of truth that can provide the map to improvement.
Reminds me of a quote in “How Google Decides to Pull the Plug” [NY Times]. Jeff Jarvis, author of the new book “What Would Google Do?”, says:
Perfection closes off the process. It makes you deaf. Google purposefully puts out imperfect and unfinished products and says: ‘Help us finish them. What do you think of them?’
Google releases imperfect, unfinished products intentionally. How much does what you’re making really need to be perfect before it gets out there?
Related: Race to Running Software [Getting Real]
Rob Drimmie
on 17 Feb 09Several game companies, and among them Valve is probably the leader in this with Blizzard being a likely contender, seem to deeply subscribe to this philosophy as well.
I don’t mean in the case of releasing poor software and patching it into functionality, but in monitoring how players behave in real situations. Valve tracks a large ton of data about how players are playing and releases content updates to address such things as particular parts of a level that a large percentage of the population of players is having unexpected difficulty with.
Blizzard (and other MMO developers do similarly) is constantly tweaking the mechanics of their game to address how it is actually being played and how things that maybe a designer or developer thought would be deep and interesting but instead turn out to be too complicated, too convoluted or just plain not fun as a result of implementation details.
Greg Digneo
on 17 Feb 09Microsoft is notorious for releasing unfinished products and then releasing “service packs”. Are they the standard bearer for product development? Probably not. But they do prove that your product can be a (sales) success even if it’s not finished.
John Bender
on 17 Feb 09“Google releases imperfect, unfinished products intentionally. How much does what you’re making really need to be perfect before it gets out there?”
I fully agree, if you never put it out there, you’ll never be finished. Such a triumph to release anything really.
How many people have great ideas and never even start, let alone finish.
Morgan
on 17 Feb 09Greetings, Timely, for me at least; I just released a 2.0 of an app of mine. It was working great in beta, but as soon as it hit the real release, I got a flood of problems that hadn’t been found in the beta. This was followed by second-guessing from the users as to whether I should have released a 2.0 at all. Of course without the release, I’d never have found these problems…
I summarize the delicate juggling act ‘twixt perfection and delivering software with the following aphorism: Shoot the engineer and ship the code.
— Morgan
Rick
on 18 Feb 09From a product management perspective, it doesn’t need to be perfect… but it at least needs to be acceptable, or you’ll never attract/keep any customers to get feedback from in the first place.
I’d also note that Google (and Apple, to note another innovative product company) may not release a perfect product, but neither do they “open-source” their development process by bringing in customers as early as possible in the process. To the contrary, the products are generally developed in secret, with feedback coming from within the team or from alpha testers & focus groups who aren’t privy to the big picture… when they think the product is good enough to be labeled “insanely great” or whatever, they release it to the market as beta/1.0 and then innovate an iterative development roadmap from there.
Martial
on 18 Feb 09When I train trainers I make sure they run an actual training immediately after my course (if possible, I sit in for additional feedback). My training of trainers is structured to give them as “real” an experience as possible, but practicing in front of colleagues is just not the same as live.
This discussion is closed.