
I watched the Social Network tonight and was fascinated with the part of the movie when the young Zuckerberg initially built Facemash (a hot-or-not type website for on-campus Harvard students) in one night. Whether this was fictional or not, as a skilled programmer by trade, I believe he totally could do it in one night (and drunk, as portrayed), assuming no bureaucracy was stifling his innovation.
These are real problems that need to be seriously considered and dealt with appropriately. But these constraints should not constrain innovation.
Too often large corporations put big processes in place to solve these big problems. And that's fine when it comes to deploying to production, or the public eye. But the amount of effort and cost needed to spin up innovative environments, needs to be free of these constraints.
Let me give you an example of what I mean: Marketing Department A has an idea to create a consolidated Twitter account made up of employee's tweets, tagged appropriately, to be fed into a corporate Twitter account. This is a smart idea, crowdsource tweets for the corporate account (this is what we do by the way).
Do I need to go through a heavy-set bureaucratic ITIL process to see if this can work? What if I'm not sure if I even want to launch it until I beta test it? If I can hire a programmer for $2K to beta test this, why do I need to spend additional thousands of dollars to justify the spin up of an innovative environment?
Infrastructure departments need to keep pace with innovation. And although it's important that they maintain consistent records of what environments exist and where, don't stifle innovation with bureaucracy. Utilize virtualization to feed development and test environments to your user-base on demand, as needed (private cloud baby!). And put an expiration date on them and spin them down for pilot projects that never make it to the real world.
Don't punish innovation with process. If you're a big corporation, use your capital and your data centers to encourage innovation. Leave the ITIL process to when things are baked enough to go to production, that's where the due diligence is needed. Maybe even use cloud environments for these innovation test beds. And if a company is truly being innovative and Agile, there may be a small percentage of environments that are actually spun up for production use. Finally, the owners of these seed-environments should not be punished, but commended. This is what keeps companies alive, kicking and competing with the dorm rooms ready to redefine any and all industries.
Does your company have this figured out? Let others know in the comments below.

