5.12 Implement Continuous Improvement Procedures
The organization has policies and practices in place to embrace experimentation, foster a growth mindset, support organizational agility, and provide continuous improvement. Product creators should iterate, regularly, though never at the cost of getting things done (such as working on larger, long-term features).
Criteria
- Continuous Improvement: The organization has created policies and practices to enable continuous improvement and has resourced the organization appropriately to support these efforts over time.
- Agile Reviews: Agile sprints and update frequency have gone through a review process to ensure project teams have enough time to conduct user-research, identify technical debt, and produce quality output.
- Iterative Consideration: A track record of continuous improvement (iteration) usage to analyze your website or application while also addressing the by-products and potential consequences of ongoing experimentation, such as technical debt, product performance, emissions, and related issues is clearly visible. Analytics are limited to only necessary features to aid with decision-making, encouraging visitor feedback, and comparing performance against business goals and visitor needs.
- Functionality Decisions: The retention of existing features, the creation of new functionality, and the decommission or elimination of unused functionality, and unvisited pages through the product’s life cycle have been justified and prioritized on a case by case basis.
- Security Updates: Corrective security and policy updates during the product or service lifecycle are provided, while such improvements are distinguished from more extensive evolutionary updates.
- Skills And Maintenance: Sustainable product and data strategies have been developed with appropriate training techniques. These should help your team (managers, colleagues, etc) build capacity and learn new skills to manage and maintain products and services over time.
Impact
High
Effort
High
Benefits
- Environmental:
Focusing on continuous improvement reduces waste and energy use by iteratively identifying opportunities to improve the product or service. - Operations:
A culture of experimentation fosters more innovation. This supports team-building and improves overall organizational resilience and efficiency. - Security:
Products or services that are maintained and updated over time reduce risk and improve security. - Privacy:
Having a high-quality, regularly kept up-to-date product or service will reduce the chances of a data breach, which will in turn increase the privacy potential of the website or application. - Accessibility:
Iteration is important for inclusive design as different visitors will have different needs, and no two individuals are alike. As such, being agile and adaptable will benefit authors in expanding their accessibility. - Performance:
Technical debt is reduced if review processes exist. Focusing on continuous improvement rather than large single-scale releases, bottlenecks in a website or application’s speed can be resolved quickly as they become apparent. This is especially useful as new releases of Web browsers can alter the performance of products and services. - Economic:
Agility and continuous improvement help an organization be more resilient in the face of disruption and a changing climate. Long-term, these practices save the organization time, money, and resources. They also provide security benefits that decrease risk and can potentially reduce emissions. - Conversion:
If a website or application renders correctly, it will naturally encourage more trust with its visitors, and thereby have the potential for repeat custom.
GRI
- materials: High
- energy: High
- water: High
- emissions: High
Example
- A showcase of how a website layers content, structure, and style. The Sustainable Web Design toolkit provides you with information relating to optimizing your product or service for the environment. The continuous improvement toolkit also has numerous business templates to work from.
Resources
- 6 stages of continuous improvement and why it is important
- An Introduction to Growth Driven Design (PDF)
- Best Practices for Material Updates to Your Privacy Policy
- Cradle to Cradle
- Demystifying digital dark matter
- Digital Eco-Design: Test, assess and maintain
- The Design Process
- [GPFEDS] 1.4 – Strategy (Regular Reviews) (PDF)
- [GPFEDS] 2.6 – Specifications (Design Review) (PDF)
- [GPFEDS] 3.1 – Architecture (Impact Reduction) (PDF)
- [GPFEDS] 3.4 – Architecture (Supplied Updates) (PDF)
- [GPFEDS] 3.5 – Architecture (Patch Updates) (PDF)
- [GPFEDS] 3.6 – Architecture (Incremental Updates) (PDF)
- [GR491] 1-3006 – Planned Sustainability Improvements
- [GR491] 2-3012 – Iterative Validation Process
- [GR491] 5-3031 – Decision Making
- [GR491] 5-3032 – Functionality Use Policy
- [GR491] 5-3036 – Necessary Analytics
- [GR491] 7-3049 – Behavior and Feedback
- [GR491] 7-3053 – Continuous Improvement
- GreenIT (French) 4001 – Limiter les outils d’analytics et les données collectées
- GreenIT (French) 4036 – Entretenir son site régulièrement
- Growth Driven Design
- How B Corp Certification Guides Rituals on a Journey of Continuous Improvement
- How to Design a Sustainable Data Strategy
- The Impact Of Agile Methodologies On Code Quality
- Measuring Web Performance
- Measuring Web Performance in 2024: The Definitive Guide
- Sustainability debt: A metaphor to support Sustainability design decisions
- SCRUM Guide
- Sprint length in Scrum
- Technical Debt, Agile, and Sustainability
- The overlooked environmental footprint of increasing Internet use
- United Nations [SDGS] Goal 8 (Economics & Work)
- United Nations [SDGS] Goal 16 (Sustainable Society)
- Using UX Design to Build a Sustainable Future
- Web Almanac: Sustainability
- What Is Continuous Improvement? The Complete Guide
- What is Technical Debt and how can you manage it?