Are the features used by the user ?
Are the proposed features expected and used by your main users and do they bring real value to your product?
According to studies (software cast and standish group), 70% of the features are never or hardly used. (ref 115 best practices) The number of functionalities available in a digital service directly impact the consumption of resources and the environmental footprint, by creating functionalities of little use. These are totally unnecessary sources of environmental debt. The functionalities also increase the volume of the service, which introduces loading delays and additional storage spaces.
Users journeys are simulated and validated to confirm features usage. Production ata are collected and processed (Analytics, probe, ...)
8 other criteria related to the recommendation: "Less is More": Focus on essential features and simplify your interface
Is a visual soberness implemented so as to reduce energy resources use and the impact on the material deterioration of the visual, sound and tactile interface's components ?
Are decision-making justified and approved by reliable indicators on the use of functionalities throughout the service life cycle ?
Is there a policy / approach / routine for the progressive reduction and prioritization of functionalities, interactions and graphic elements ?
Are the stakeholders of the SEO service involved, starting from the design phase ?
Is the practice of e-mailing considered, justified and reduced to what is strictly necessary ?
Are an archiving schedule and a lighter version of the old searchable content implemented ?
Has the analytics been limited to what is strictly necessary to optimize the service ?
Are third-party services (social network feeds, social wall, carousels, google maps, etc.) not used for convenience to compensate for the lack of content production resources ?