Lesson plan
Blinking twelve problem
In software design, the blinking twelve problem is when features in software or computer systems are rendered unusable to most users by the complexity of the interface to them. The usage emanates from the 'clock' feature provided on many VCRs manufactured in the late 1980s or early 1990s. The clock could be set by using a combination of buttons provided on the VCR in a specific sequence that was found complicated by most users. As a result, VCR users were known to seldom set the time on the VCR clock. This resulted in the default time of '12:00' blinking on the VCR display at all times of the day, which is the origin of this term. 'The blinking twelve problem' thus refers to any situation in which features or functions of a program go unused for reasons that the designers never anticipated, largely because developers were unable to anticipate the level of understanding the users would have of the technology. The term may also refer to the challenge faced by developers of addressing the real causes of users' difficulties, as well as the challenge of providing helpful documentation or technical support without knowing beforehand how well the user understands their own problem.…
Article summary
In software design, the blinking twelve problem is when features in software or computer systems are rendered unusable to most users by the complexity of the interface to them. The usage emanates from the 'clock' feature provided on many VCRs manufactured in the late 1980s or early 1990s. The clock could be set by using a combination of buttons provided on the VCR in a specific sequence that was found complicated by most users. As a result, VCR users were known to seldom set the time on the VCR clock. This resulted in the default time of '12:00' blinking on the VCR display at all times of the day, which is the origin of this term. 'The blinking twelve problem' thus refers to any situation in which features or functions of a program go unused for reasons that the designers never anticipated, largely because developers were unable to anticipate the level of understanding the users would have of the technology. The term may also refer to the challenge faced by developers of addressing the real causes of users' difficulties, as well as the challenge of providing helpful documentation or technical support without knowing beforehand how well the user understands their own problem.…
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.