Is there a policy / approach / routine for the progressive reduction and prioritization of functionalities, interactions and graphic elements ?
Is there a tracking tool to prioritize, and evaluate the functionalities' use throughout the service life cyle?
The deletions of elements on interfaces may not disrupt users, and therefore generate a reduced footprint with fewer elements and functionality without degrading the value of the service while limiting its environmental footprint.
- Simplification reviews - Absence tests - Fanatic focus - Poker planning
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 the features used by the user ?
Are decision-making justified and approved by reliable indicators on the use of functionalities throughout the service life cycle ?
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 ?