---
title: "Tech Tip #55: Put energy in your definition of done (video)"
description: "Energy is in almost nobody's definition of done."
url: https://greencode.ai/shorts/55-energy-in-definition-of-done/
---

# Tech Tip #55: Put energy in your definition of done (video)

## Tech Tip #55: Put energy in your definition of done

**Energy is in almost nobody's definition of done.**

[Watch the video](https://media.greencode.ai/shorts/energy-in-definition-of-done-3ad7a1278979.mp4)

Video created by [explainapaper.com](https://explainapaper.com/?utm_source=greencode.ai&utm_medium=film&utm_campaign=made-by)

### The problem

Sustainability stays incidental because nothing in the delivery process asks for it. Changes pass review on features, tests and security, and energy regressions ship unnoticed.

### The fix you can use today

- Add an energy check for performance-critical changes to your definition of done.
- Gate releases on an energy regression test for key scenarios.
- Review energy trends in the same meeting as performance and cost.

GreenCode researchers found that energy is almost never part of a team's definition of done.

### Tools that help

- [Eco CI](https://github.com/green-coding-solutions/eco-ci-energy-estimation?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode): estimates the energy of CI pipeline runs on GitHub Actions and GitLab, per step
- [Green Metrics Tool](https://github.com/green-coding-solutions/green-metrics-tool?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode): measures the energy of whole software scenarios run in containers, so runs can be repeated and compared

### How GreenCode helps

GreenCode helps tackle this by building the energy test for you: a load test generated from the system's own endpoints that records energy as well as speed and ranks the hotspots by the energy they use. [More on this](https://greencode.ai/feature/automated-performance-testing/).

### Tags

#governance#ci-cd#testing

### Sources

- [GreenCode State of the Art Review, D2.1 (2025), PDF p. 63: sustainability not present in definition of done or acceptance criteria; efficiency regressions go unnoticed for months](https://greencode.ai/publications/d2-1-state-of-the-art-review/)

### Transcript

Energy is in almost nobody's definition of done. Changes pass review on features, tests and security. But nothing in the process asks about energy. So a change that uses more power ships without anyone noticing. It can go unnoticed for months. Here is the fix you can use today. First, add an energy check to your definition of done. Start with the changes where speed matters most. Then add an energy test for your key scenarios. Tools like Eco CI and the Green Metrics Tool fit it into your pipeline. If energy goes up, the release waits. And look at energy trends in the same meeting as speed and cost. GreenCode researchers found that energy is almost never part of a team's definition of done. GreenCode helps tackle this by building that energy test from your system's own endpoints. It records energy as well as speed, and ranks the hotspots by energy. That was GreenCode Tech Tip number fifty-five. Follow for the next tip, and find more on greencode.ai/tech-tips.

[The tip in full](https://greencode.ai/tech-tips/55-energy-in-definition-of-done/)

[« Tech Tip #54: Profile before you optimise](https://greencode.ai/shorts/54-profile-before-you-optimise/)[Tech Tip #56: Look up what your job actually used »](https://greencode.ai/shorts/56-look-up-your-job-energy/)

[All GreenCode Tech Tips](https://greencode.ai/tech-tips/) · [All GreenCode videos](https://greencode.ai/videos/)

#### Key Facts

- Tip **#55**
- For **CTOs and technical leads**
- Length **1:05**
- Category **Testing, CI and code quality**
![GreenCode](https://greencode.ai/wp-content/uploads/2024/12/greencode-logo-website-small-colours-2.webp)

Want this checked on your own system? Talk to the GreenCode team.

[Get in touch](https://greencode.ai/contact/)
