Degradation is a condition in which a software product or system becomes slower or less efficient than required. It often develops without crashes or visible errors: a delayed response, sluggish interaction, or slow-loading layout gradually weakens the user experience. section 2.1 section 2.1.4
The recurring pattern is simple: a technical change appears acceptable in isolation, reaches production, and then compounds across real sessions. Users rarely report the underlying cause; they leave, convert less often, engage less, or switch competitors. Degradation therefore affects money, time, trust, and team productivity rather than performance metrics alone. section 1.2 section 2.1.4
Recognize degradation through recurring symptoms and costs:
- Measure user and business impact through conversion changes, retention, search or app-store visibility, and support consequences. section 2.0 section 2.6
- Treat small delays as cumulative: a sluggish interaction or delayed response can determine whether users convert, engage, or leave. section 2.1.4
- Track internal degradation through reactive investigations, recurring regressions, wasted engineering time, and planned work displaced by firefighting. section 2.3.1 section 2.3
- Distinguish individual-user speed problems from scalability and resilience problems before selecting architectural remedies. section 5.1
A degradation pattern in practice
A landing page loads only slightly more slowly after a change. That delay seems harmless during review, but across thousands of sessions it reduces engagement and sales. Similar degradation can appear as scripts injected through a tag manager, startup lag on older mobile devices, inefficient database queries, or frame drops in a desktop interface. section 2.1.4 section 2.3.1





