Lessons IT can take away from Romney campaign's Orca project?
Putting aside who you wanted to win the presidential campaign, one thing that I was interested in was the Romney campaign's Project Orca, which in concept allowed real time updates to individual voter status as reported by in situ observers at polling stations. In practice, Orca was a wonderfully named fail whale example. http://www.ucstrategies.com/unified-communications-newsroom/project-orca...
To lay it out as simply as possible, the campaign set up a website, and in real time campaign personnel was to check off that an individual voter had appeared and voted. This would allow targeted efforts to contact likely Romney voters that had not yet cast their ballot to remind/encourage them to vote. Sounds pretty good in theory. Except that on election day, the website was pretty much down (or at least inaccessible) the entire time, presumably due to the sudden influx of heavy traffic, which one would think would be expected seeing as how this was a one day, big event. To use the language of one of my old colleagues, is this a "teaching moment". What can we take away from this epic fail to make sure something similar doesn't happen to us on major projects?
Ask a question
White Papers & Webcasts