Description
Diagnoses why a method declined: complexity, technological displacement, paradigm shift, lost training infrastructure, faster competitors, failed validity, or fashion.
The treatise's systematic analysis of why methods die names seven causes. Complexity exceeds organisational patience (contextual inquiry demanded too much). Technological displacement (desktop methods not transferring to mobile, often producing death where adaptation would do). Paradigm shift (the 1990s move from cognitive to social perspectives; agile marginalising sequential methods). Loss of training infrastructure (curricula, consultancies and textbooks disappear; GOMS is in every history but almost no programme teaches it). Competitive displacement by faster methods (richer outputs are hard to demonstrate, cost differences obvious). Failed replication and validity concerns (legitimate, but often confused with implementation failure). Fashion and novelty preference. Diagnosing the cause tells you whether a method should stay dead or how to revive it.
Attributes
- Discipline
- Community-Proposed Frameworks
- Loss type
- Community-proposed
- Tested
- Not yet tested
- Goal
- Support a decision
- Stage
- Strategy
- Data
- Analytical / expert
- Effort
- Hours
Steps
- Select a method in decline or already lost.
- Trace its lifecycle: development, early adoption, mainstream simplification and decline.
- Gather evidence on each of the seven causes (literature, practitioner interviews, curricula).
- Distinguish legitimate validity failure from implementation failure.
- Identify the dominant causes and their reversibility.
- Design a recovery strategy targeted at those causes, or archive the method.
Sources
- Lost Methods in UX — A Complete Treatise (Gopinath)
- Rogers EM (2003) Diffusion of Innovations
- Kuhn TS (1962) The Structure of Scientific Revolutions
Also known as
- Why methods die
- Method mortality analysis
Categories
- Community-Proposed Frameworks