2. Defining the essential and eliminating the superfluous
The sooner we intervene, i.e. during the definition of requirements, during the designing of functionality and during the layout phase, the greater the lever effect in terms of reducing the environmental footprint.
(Translated from the French Eco-design / the 115 best practices, 2019)
Before moving on to the design stage, it is crucial to accurately assess needs to avoid unintentionally adding any unnecessary functionality. Around 45% of requested features are never used, and 70% are not essential. (Eco-design for the web: 115 best practices (French)). Defining needs is therefore a crucial stage, and must be done in conjunction with the project's stakeholders.
Eco-design is a comprehensive approach to continuous improvement, with the aim of reducing environmental impacts, in particular through restraint. One of the principal cornerstones of this approach is the functional unit.
The functional unit corresponds to the main purpose of the service, and is often expressed in the form of a specific action. For example: “Buying a concert ticket”, “Watching a 5-minute video from a smartphone with 4G”, “Searching for a phone number”, “Making a 20-minute video call”, “Booking a doctor's appointment from a laptop”, etc.
Questions to be asked
The first need to be assessed is that of the digital service itself:
- Is it necessary to use digital technology for this service?
- Are there other, non-digital solutions to meet this need? (see Dedigitize, rematerialize)
RGSEN Criterion 1.9
Favoring interoperable technologies (such as texts over online notifications) would fulfill the recommendations of Criterion 1.9 of the General Repository for the Eco-design of Digital Services (Référentiel Général de l'Ecoconception des Services Numériques - RGESN).
See the repository (French)
Once this is done we can consider other requirements to be defined:
- What actual needs justify the creation of the service?
- Does the added value of the service justify mobilizing the resources required to create it? Do we create more value than we destroy?
- Is this functionality really necessary? Can we do things differently?
- What would happen if we did not have it?
- What is the lowest number required to meet user needs? Number of results, image resolution, sound quality, video length, etc.
RGSEN Criterion 1.1
Providing well-argued answers to the questions above would fulfill the recommendations of Criterion 1.1 of the General Repository for the Eco-design of Digital Services (Référentiel Général de l'Ecoconception des Services Numériques - RGESN). Note: It is recommended to lead a "qualitative analysis of the environmental impacts, whether direct or indirect, that could potentially result from the service in the form of a flowchart."
See the repository (French)
RGSEN Criterion 4.7
Choosing the most frugal medium to meet each of the user's needs (text, image, audio or video) would fulfill the recommendations of Criterion 4.7 of the General Repository for the Eco-design of Digital Services (Référentiel Général de l'Ecoconception des Services Numériques - RGESN).
See the repository (French)
RGSEN Criterion 6.6
Refraining from making use of the user terminal's sensors (such as GPS localization) unless specifically required by user needs would fulfill the recommendations of Criterion 6.6 of the General Repository for the Eco-design of Digital Services (Référentiel Général de l'Ecoconception des Services Numériques - RGESN).
See the repository (French)
Non-essential features
BBC podcast offers two download options: “high quality” and “low quality”.
If you don't know the impact of one or the other, you will likely default to the “high quality” option, which is twice as heavy, yet the difference is barely perceptible to the ear.
The feature should be “Listen to a podcast”, not “Listen to a program in high or low quality”.
So we could eliminate a non-essential feature here and keep just one download option: the "low quality" option, without naming it this way!

For further information
- Eco-design: 115 best practices - 4th edition on github - GreenIT (French)
- Questioning guide for the development of digital services (PDF) - ADEME (French)
- An eco-designed app to promote short-distance sales - GreenIT (French)
The essential role of user experience (Green UX)
Green UX means focusing on the actual needs and expectations of users, to limit environmental impact. Eco-design means going back to the fundamental principles of user-centered design, sometimes misused for commercial purposes (see the section on the risk of greenwashing and persuasive design).
Focusing on the must-haves does not mean sacrificing the user experience - quite the contrary. An example of this is the difference between Google's simple search engine layout (a logo and a search box), as opposed to Yahoo's which is loaded with superfluous information (weather, stock market, news, horoscopes, ads, etc.). (Eco-design: 115 best practices (French))
Not to mention the number of server requests when a search query is run, these two extreme examples meet the same requirement for a search engine, i.e. the functional unit “Searching the web”, but with two completely different UX approaches. The first approach is the most effective in terms of needs, but also the most appreciated by users. Other search engines such as Qwant or DuckDuckGo, more respectful of privacy than Google, also apply this principle of simplicity.
Moreover, applying a “Green-UX” approach has consequences for the entire digital service creation process:
- interface layout decisions,
- selection of components and functionalities,
- the navigation sequence.
This automatically impacts the design, development, maintenance and upkeep of the service. It is therefore essential to think in terms of sobriety and efficiency, with users as our focus, in order to reduce the service's final environmental footprint.
RGSEN Criterion 1.2
Clearly defining target users and their actual expectations for the digital service would fulfill the recommendations of Criterion 1.2 of the General Repository for the Eco-design of Digital Services (Référentiel Général de l'Ecoconception des Services Numériques - RGESN).
See the repository (French)