What Is 'Let's Make Quality the Norm Again'?

'Let’s make quality the norm again' is a consumer policy report and campaign published by Norway's Consumer Council (Forbrukerrådet) that targets premature obsolescence in consumer electronics and domestic goods. It presents concrete regulatory mechanisms to mandate repairability, long-term software maintenance, and durable physical design across consumer markets.

Core Architecture and Mechanics

The 'Let's make quality the norm again' initiative targets the systemic incentives that prioritize rapid hardware replacement cycles over longevity. Modern consumer tech frequently fails not from mechanical wear, but through deliberate physical locks, non-replaceable batteries, and artificial software cutoffs.

The framework addresses product life cycles through three structural vectors:

• Physical Durability: Prohibiting adhesives and proprietary fasteners that prevent non-destructive teardowns.
• Component Access: Requiring original equipment manufacturers (OEMs) to supply replacement modules and schematics at non-punitive prices.
• Software Decoupling: Mandating long-term security updates and preventing software updates from bricking or degrading functional hardware.

Technical Implementation & Workflows

Implementing the recommendations requires fundamental adjustments in embedded systems development, hardware manufacturing, and downstream firmware distribution.

At the hardware layer, engineering teams must transition away from glued sub-assemblies. This involves adopting modular interconnects, standard screw interfaces (such as Torx or Phillips), and accessible test points for diagnostic evaluation.

Product Life Cycle Standard:
Design Modularly -> Publish Schematics -> Support Firmware (5-10 yrs) -> Unlock Bootloaders on EOL

At the software layer, the report aligns with right-to-repair and circularity frameworks by targeting firmware end-of-life (EOL) mechanics. When active upstream vendor support terminates, manufacturers should be required to provide open access to bootloaders, driver packages, and basic diagnostic tools. This enables third-party maintainers and postmarket distributions to preserve device utility.

Practical Trade-offs & Limitations

Adopting forced durability standards involves measurable engineering and economic trade-offs. Designing hardware for disassembly can increase unit volume and bill-of-materials (BOM) costs. It can also complicate ingress protection (IP68 water and dust resistance), which frequently relies on permanent adhesive seals.

From a software maintenance perspective, long-term support (LTS) requirements burden embedded development teams. Maintaining board support packages (BSPs) across legacy system-on-chips (SoCs) requires dedicated engineering hours, particularly when upstream silicon vendors terminate driver updates prematurely.

Additionally, small hardware manufacturers face higher relative compliance costs compared to vertically integrated market leaders. Without harmonized international enforcement, localized policies risk driving niche hardware vendors out of target jurisdictions.

Developer Verdict & Ecosystem Impact

The initiative represents a pivotal shift toward legislative accountability for consumer tech lifecycles. Developer reaction—reflected in high-engagement engineering forums like Hacker News—highlights strong community consensus against planned obsolescence, proprietary diagnostic barriers, and software lock-in.

For systems engineers and consumer hardware developers, these regulatory shifts signal an incoming baseline standard across the European Economic Area. Designing for longevity, modular component replacement, and firmware openness is shifting from a marketing preference to an unavoidable regulatory compliance requirement.

Latest Verified Updates

• 9/16/2026: New software release detected: v25.6