Draft:Unusability Preservation Law

Submission declined on 8 November 2024 by Idoghor Melody (talk).

This submission is not adequately supported by reliable sources. Reliable sources are required so that information can be verified. If you need help with referencing, please see Referencing for beginners and Citing sources.

This draft's references do not show that the subject qualifies for a Wikipedia article. In summary, the draft needs multiple published sources that are:

in-depth (not just passing mentions about the subject)
reliable
secondary
independent of the subject

Make sure you add references that meet these criteria before resubmitting. Learn about mistakes to avoid when addressing this issue. If no additional references exist, the subject is not suitable for Wikipedia.

If you would like to continue working on the submission, click on the "Edit" tab at the top of the window.
If you have not resolved the issues listed above, your draft will be declined again and potentially deleted.
If you need extra help, please ask us a question at the AfC Help Desk or get live help from experienced editors.
Please do not remove reviewer comments or this notice until the submission is accepted.

Where to get help

If you need help editing or submitting your draft, please ask us a question at the AfC Help Desk or get live help from experienced editors. These venues are only for help with editing and the submission process, not to get reviews.
If you need feedback on your draft, or if the review is taking a lot of time, you can try asking for help on the talk page of a relevant WikiProject. Some WikiProjects are more active than others so a speedy reply is not guaranteed.

How to improve a draft

Wikipedia:Contributing to Wikipedia – a basic overview on how to edit Wikipedia.
Help:Wikitext – how to use the markup
Help:Referencing for beginners – how to include references
Wikipedia:Article development – how to develop your article
Wikipedia:Writing better articles – how to improve your article
Wikipedia:Verifiability – make sure your article includes reliable third-party sources

You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article.

Improving your odds of a speedy review

To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags.

Add tags to your draft

Editor resources

Easy tools: Citation bot (help) | Advanced: Fix bare URLs

Declined by Idoghor Melody 34 days ago. Last edited by Idoghor Melody 34 days ago. Reviewer: Inform author.

Resubmit

Please note that if the issues are not fixed, the draft will be declined again.

Unusability Preservation Law

The Unusability Preservation Law is an informal adage that suggests whenever a technology reaches a state of optimal usability—when it aligns well with user needs and satisfaction—it will inevitably undergo changes that impair its usability or significantly detract from the user experience. This concept is often cited in discussions about software development, user interface design, and technological evolution, highlighting the tension between innovation and user comfort.

Overview

The law posits that as technologies mature and users become proficient and comfortable with them, changes—whether through updates, redesigns, or corporate decisions—tend to disrupt this equilibrium. These changes may not always stem from user needs but could be driven by market trends, technological shifts, or strategic objectives that overlook the existing user base's preferences.

Origins

The concept originates from observations within the technology community, particularly among users and developers who have experienced repeated cycles of software and hardware becoming less user-friendly after updates or new versions. While not a formally recognized law, it encapsulates a common sentiment about the challenges of maintaining usability amid constant technological change.

This concept was inspired by discussions in the technology community, notably articulated in the Czech article Zákon zachování nepoužitelnosti, where the law's name and formulation were proposed.^[1]

Examples

Software Redesigns

User Interface Overhauls: Major updates to operating systems or applications often introduce new user interfaces that can confuse or frustrate existing users. For example, the transition from familiar desktop environments to touch-optimized interfaces has been met with resistance from users who prefer traditional navigation methods.
Feature Removal: Software updates may remove or alter features that users rely on, impacting their workflows. The deprecation of certain functions without adequate replacements can lead to decreased productivity and satisfaction.

Corporate Decisions

Protocol Discontinuation: Companies might discontinue support for widely used protocols, forcing users to adopt alternative solutions that may not offer the same level of interoperability or convenience. An instance of this is the removal of standard messaging protocols in favor of proprietary systems.
Product Termination: The sudden shutdown of services or products can leave users without critical tools, necessitating a search for replacements that may not fully meet their needs.

Open Source Projects

Radical Changes: Open source projects sometimes undergo significant changes that prioritize new directions over existing functionalities. For example, shifts to new architectures or frameworks can render previous configurations obsolete, requiring users to adapt to entirely new systems.
Fragmentation: Forks in open source projects can divide development efforts and lead to inconsistencies, affecting the overall usability of the software.

Implications

The Unusability Preservation Law underscores the importance of balancing innovation with user needs. While technological advancement is essential, disregarding the user experience can lead to dissatisfaction and erosion of user trust. It serves as a cautionary principle for developers and companies to consider the impacts of changes on their existing user base.

Related Concepts

Software Bloat: The tendency of software to become resource-intensive over time due to the accumulation of features.
Feature Creep: The excessive addition of new features that complicate the product and detract from its core functionality.
User Experience (UX): The overall experience of a person using a product, particularly in terms of how easy or pleasing it is to use.
Technological Lock-In: A situation where a user becomes dependent on a vendor for products and services, unable to use another vendor without substantial costs.

References

^ Křivánek, P. Zákon zachování nepoužitelnosti. ABC Linuxu, 2018.

Zákon zachování nepoužitelnosti – Original article in Czech by Pavel Křivánek on ABC Linuxu.

[1] Křivánek, P. Zákon zachování nepoužitelnosti. ABC Linuxu, 2018.

[1]