Medium impact πΏ
Occasionally, you may find that features you have developed for a product or service have little to no active users or could be better implemented to bring better value. Undertaking research to identify redundancy allows you to optimize your codebase (and reduce emissions).
Consider visitor feedback and monitor adoption and churn rates of product or service features, incorporating insights into future releases.
π¦Ύ
Medium impact πΏ
Try to ethically measure how efficient a visitor's experience is, by doing so you might be able to reduce any issues they may have encountered previously and reduce the burden of loading unnecessary pages.
Only collect the data required to provide a streamlined and effective user-journey, put policies in place to ensure strict adherence, and comply with relevant accessibility policies and privacy laws, such as the General Data Protection Regulation (GDPR).
π¦Ύ
Medium impact πΏ
There are many variables which can impact the user-experience, and a bunch of these can impact how sustainable your website will be. Attempting to identify where you can make a difference to the visitor and give them a more sustainable experience will be beneficial.
List the negative external variables and identify where your product's sustainable impact can be diminished (systemic design).
π¦Ύπ¦Ύ
Medium impact πΏ
Products and services at any stage of a project can suffer bugs or issues which need to be resolved. Fixing these regressions also generates additional development and environmental costs. By resolving such issues, you can reduce the chances of a visitor giving up on a session and thereby reduce the amount of wasted energy your website emits overall.
Check your codebase for bugs, identify any performance issues, and account for accessibility or security problems at either monthly or quarterly timeframes (depending on your scheduling allowance).
Non-regression tests are implemented for all important functionality.
Incorporate regression testing into each release cycle to ensure that new features don't introduce bugs or otherwise conflict with existing software functionality.
π¦Ύπ¦Ύ
Medium impact πΏ
Everything produced by designers, developers, writers and those involved with a project should be in an open format, well maintained, and curated in a common format (so everyone is working from the same model).
The deliverables output, including documentation, are used upstream of the project and produced in ways that will allow it to be reused in subsequent projects.
Design functionality and technical specifications are documented so that deliverables are comprehensible by the project team and transferable to the development team.
π¦Ύπ¦Ύπ¦Ύ
Medium impact πΏ
Brainstorming allows you to flush out ideas before you commit to pursuing a path. Being considerate of not just your visitors but other individuals who may be affected by your product or service (including non-humans, like the environment!) is a useful practical exercise as it may influence your decisions in how you scope your project.
In the brainstorming process, consider all stakeholders using a human-centered approach.
In the brainstorming process, take the planetary needs and ecological boundaries into account.
π¦Ύπ¦Ύ
Medium impact πΏ
Languages evolve regularly, and it's important for security and performance reasons to keep on-top of the technology stack you are using.
Use the latest build of your chosen syntax language and its coupled framework.
π¦Ύπ¦Ύ
Medium impact πΏ
Printing or downloading documents can both be a net benefit and a net cost in terms of sustainability as it can reduce repeat requests to websites, but the act of printing (especially when unoptimized) wastes valuable ink and paper.
Design documents to limit the printing impact. If the production of paper documents is essential, it should be designed to limit its impact to the lowest possible. Create a CSS Print stylesheet and test it with different types of content. Ensure PDF printing is encouraged over paper-based storage.
Offer optimized, compressed documents in a variety of accessible file formats.
If a document is likely to be re-used, generate the document once on the server-side (preferably on a cookie-free domain) rather than forcing the effort to be duplicated.
Clearly display the document name, a summary, the file size, and the format, allowing the visitor a choice if possible of both the format, and the language (if not the same as the web page). Furthermore, be sure to avoid embedding the document within Web pages (provide a direct link to download or view within the browser instead).
π¦Ύ