August 28th, 2006
Election Troubles
The Anchorage Daily News reports about technical problems with new Diebold voting machines. From the article:
Problems with Alaska’s new touchscreen voting machines slowed election returns Tuesday and caused elections officials to hand count and manually upload vote totals from several precincts across the state.
Election coordinator Lauri Wilson said several Diebold touchscreen machines in Southeast Alaska, the Interior and near Nome did not upload their votes into the Division of Elections’ central computing system. The machines’ modems either did not get a dial tone or had other problems, Wilson said.
The votes from touchscreen voting machines in four Kodiak precincts had to be manually uploaded because the electronic ballots were required to be presented in more than one language, Wilson said.
——————————-
“We’ve got new technology. Particularly in rural Alaska, we’re going from the paper ballot to cutting-edge technology and the entire process is being slowed down,” said Division of Elections Director Whitney Brewster.
Alaska Democratic Party spokeswoman Kay Brown said the slowdown caused by the touchscreen machines is indicative of larger problems with the machines.
“I can say there are many systematic problems with Diebold machines that have been identified in many contexts,” Brown said. “That there were technical glitches with the machines is not surprising, and it’s one indication of the kinds of things that can go wrong with the machines and it’s something to be concerned about.”
Reading between lines, it’s easy to conclude that the technology was delivered without completely understanding downstream requirements. For example, in one precinct the machines could not be used because non-English translations were required but not included. This specific example is not a technology issue, per se. Regarding the modem dialing problems, how come it wasn’t tested in advance? I’m sure the machines worked fine in the lab, but didn’t anyone think what what might happen in a remote Alaskan village with poor dial tone quality? Yet another rollout planning issue.
Fundamentally, this is no different from any technology rollout where customer and administrative requirements are not planned properly, leading to unhappy users.
Michael Krigsman is CEO of Asuret, Inc., a software and consulting company dedicated to reducing software implementation failures. Click here to discuss this post with him on Twitter. See his full profile and disclosure of his industry affiliations.
Subscribe to IT Project Failures via Email alerts or RSS.
SponsoredWhite Papers, Webcasts, and Downloads
- Five Steps to Determine When to Virtualize YourServers VMware Server virtualization isn't just for big companies. Entry-level ... Download Now
- Reducing Server Total Cost of Ownership with VMware Virtualization Software VMware VMware virtualization enables customers to reduce their server TCO and ... Download Now
- Building the Virtualized Enterprise with VMware Iinfrastructure VMware VMware virtualization software has been adopted by over 120,000 enterprise ... Download Now
- Save time and money for your business. Learn about low cost tech, software and shipping solutions.
- Grow your small business and increase efficiency with UPS tools and technology
- Most popular tools & templates for your business
- Automate shipping and save time with free tools from UPS
Recent Entries
- 18 truths: The long fail of complexity
- Please vote: Shortlisted at Computer Weekly
- Five definitions toward the maturing of Enterprise 2.0
- Seeking IT failure experts on Twitter
- Amplifying ‘weak signals’ for IT success
Most Popular Posts
- Gartner Magic Quadrant lawsuit: Sour grapes or real gripes?
- Learning from the weak signals of failure
- Seeking IT failure experts on Twitter
- Five definitions toward the maturing of Enterprise 2.0
- Amplifying 'weak signals' for IT success
- Workday, SaaS, and failure: 'A matter of trust'
Top Rated
- 18 truths: The long fail of complexity+13 votes
- Twitter suspends security researcher's account as a threat+10 votes
- Learning from the weak signals of failure+6 votes
- Five definitions toward the maturing of Enterprise 2.0+5 votes
- Workday, SaaS, and failure: 'A matter of trust'+3 votes
- Gartner Magic Quadrant lawsuit: Sour grapes or real gripes?+1 vote
- Amplifying 'weak signals' for IT success+1 vote
- Oracle's integration strategy: Customer trade-offs+1 vote
Premier Vendor Content Whitepapers, webcasts & resources from our Power Center Sponsors
Archives
ZDNet Blogs
- All About Microsoft
- The Apple Core
- Between the Lines
- BriefingsDirect
- Collaboration 2.0
- Dev Connection
- Digital Cameras & Camcorders
- Ed Bott's Microsoft Report
- Emerging Tech
- Enterprise Web 2.0
- Forrester Research
- Googling Google
- GreenTech Pastures
- Hardware 2.0
- Home Theater
- iGeneration
- Irregular Enterprise
- IT Project Failures
- Laptops & Desktops
- Lawgarithms
- Linux and Open Source
- Managing L'unix
- The Mobile Gadgeteer
- On Sustainability
- Rational Rants
- The Semantic Web
- Service Oriented
- Smartphones and Cell Phones
- Social Business
- Social CRM: The Conversation
- Software & Services Safari
- Software as Services
- Storage Bits
- Team Think
- Tech Broiler
- Technology and the Global Supply Chain
- Tom Foremski: IMHO
- The ToyBox
- Virtually Speaking
- The Web Life
- ZDNet Education
- ZDNet Government
- ZDNet Healthcare
- Zero Day
White Papers, Webcasts, and Downloads
- Five Steps to Determine When to Virtualize YourServers VMware Server virtualization isn't just for big companies. Entry-level ... Download Now
- Key Strategies for Federal Agencies - Safe and Cost Effective Migration for Legacy Hardware GovConnection The federal government has mandated that federal agencies reduce energy ... Download Now
- Email Security and Archiving - Clearer in the Cloud Google The time is NOW for businesses and organizations of all sizes to implement ... Download Now








