/ Library/ Not Enough Meaning/ Declinism
Connect Bias № 037 · Last updated 6 June 2026

Declinism.

"The past feels golden, the present feels broken — even when the metrics say otherwise."

01Overview

Declinism is the belief that society — or a domain within it — is in decline compared to the past. In product work, the same cognitive posture appears as "the old version was better," "users used to love us," or "design quality isn't what it was." The golden age is reconstructive. The present is vivid and disappointing.

For designers, declinism fuels reactionary redesigns, nostalgia-driven feature resurrection, and dismissive attitudes toward new users who lack shared history. It also shapes research: long-tenured users compare everything to a remembered peak, while newer users lack that anchor — two populations, two realities, one synthesis deck trying to please both.

02Detailed explanation

Declinism combines rosy retrospection for the past with negativity bias toward the present. Evidence is asymmetric:

  • Veteran users remember early product simplicity while forgetting early bugs, missing features, and slower performance.
  • Teams cite "engagement was higher before the redesign" without adjusting for market saturation, competition, or cohort mix.
  • Industry discourse declares UX "dead" or "worse every year" while measurable accessibility and usability benchmarks often improve.
  • Executive nostalgia resurrects retired flows that failed for documented reasons — because failure faded from memory faster than affection.

Declinism is not always wrong — products do degrade, companies do extract, trust does erode. The bias is in the default direction: decline feels true before evidence is checked.

03Why it exists

Memory edits the past upward and emotion weights the present downward when expectations are unmet. Change disrupts competence; users mourn the skill they had in the old UI.

Status and identity attach to tenure. "Back when it was good" can mean "back when I felt competent and central" — a user identity story, not an objective quality score.

The short version

Nostalgia is data about feeling, not proof about quality. Ask what specifically was better — and for whom.

04Effects on users

Long-time users experience declinism as moral betrayal: each redesign reads as decline because it costs them automaticity. They report the old version was "honest" or "for real users" — affect speaking as history.

New users lack golden-age memory. They compare you to current competitors, not to your 2016 UI. A roadmap driven by declinist veterans may ignore the population still growing.

05Effects on designers & teams

Teams internalise declinism in familiar ways:

  • Redesign rollback pressure. Vocal minorities with tenure dominate forums; silent new adopters don't counterbalance.
  • Research overweighting OGs. Power users who remember v1 shape strategy for casual users who never saw v1.
  • Industry cynicism as identity. "Everything is worse now" becomes designer culture — discouraging measurement and improvement.
  • Selective benchmarks. Compare today's product to yesterday's best day, not to yesterday's median Tuesday.

6Introspective view

Look inward. Teams judge the past rose-tinted and the present harshly, distorting strategy and trend reading.

From an introspective perspective, ask how Declinism may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.

Research Synthesis

Themes that fit the deck

During synthesis, Declinism nudges teams toward a tidy narrative — quotes that support the emerging story rise to the top; outliers stay in the spreadsheet. Teams judge the past rose-tinted and the present harshly, distorting strategy and trend reading.

Retrospectives

The story of the sprint

Retros on Declinism tend to rehearse the narrative that is easiest to tell — usually the one that matches how people already feel about the work. Teams judge the past rose-tinted and the present harshly, distorting strategy and trend reading.

Strategy

The brief you inherited

Strategy work on Declinism often starts from a problem statement someone else wrote — and that opening frame limits which solutions feel in scope. Teams judge the past rose-tinted and the present harshly, distorting strategy and trend reading.

User Interviews

What you hear first sticks

In early interviews about Declinism, the opening participant can set the frame for everyone after — which pains feel central, which workflows seem broken, which quotes get repeated in synthesis. Teams judge the past rose-tinted and the present harshly, distorting strategy and trend reading.

07Practical takeaways

  • Segment research by tenure. Separate what veterans mourn from what newcomers struggle with.
  • Ask for concrete comparisons. "What task worked better before?" not "Was it better before?"
  • Pair memory with metrics. Completion time, error rate, and support volume from the golden era — if you can reconstruct them.
  • Respect skill loss, not only nostalgia. Migration paths and retraining reduce declinism driven by disrupted competence.
  • Watch survivorship in feedback channels. Forums amplify users who stayed; churned users who agreed it got worse are already gone.
  • Document why you removed things. Future teams will face declinism without your context unless you write it down.

08Design examples

Redesign

Bring back the old settings

A settings overhaul triggers a petition for the "classic" layout. Telemetry shows task success improved 18%. Petition signers skew toward five-plus-year accounts. Declinism meets real skill disruption — both need answers, not only rollback.

Research

It used to be simpler

Interviews with early adopters uniformly praise the original onboarding. Cohort analysis shows original onboarding had 40% drop-off — rosy retrospection turned a flawed flow into a sacred object.

Industry discourse

Design is dying

A team skips usability testing because "nobody cares about UX anymore." Competitors who still test gain share. Declinism became process abandonment.

Feature resurrection

The beloved export

Leadership demands revival of a retired export format. Incident logs from retirement year show it caused 30% of support tickets. Memory kept the power users who loved it, lost the majority who didn't.

09Ethical risks

Designing only for declinist veterans abandons users who arrived after the golden age — often more diverse, less privileged, and less loud in feedback channels.

Cynical declinism can justify cutting accessibility and research investment — "quality doesn't matter anymore" — while users who depend on quality most pay first.

Self-test: What part of your product's past do you personally miss — and what evidence would change your mind about whether it was actually better?

10Suggested reading