The findings and recommendations have mainly been picked up throughout the interviews and workshops. We conducted this part as targeted group interviews focusing on the 4 main areas of the regenerative software model.

On the first day, after the initial Continuous Delivery presentation, we had an exercise where all attendees together were asked to illustrate the process from the point where a requirement or a change request arrives until the implemented result can be accessed by the end-users.

The participants were also equipped with stickers with 6 different pictograms representing: Wait state, unplanned work, manual work, conflicts, queued work and anything that needs repair.

The result was discussed during the workshop and then used as a reference point during the various discussions on the following day.

Ecological Alignment

Observation

The card is strongest when it is tied to an explicit trigger, such as carbon intensity, time window, or batch size threshold. That makes the operational goal visible to the team instead of leaving it as a vague aspiration.

Elaboration

If the workload is allowed to run at any time, the environmental benefit becomes incidental. Treat the scheduling rule as part of the definition of done so the energy decision is made where the work is planned.

Recommendation

For this client, start with one non-interactive job and document the grid or battery condition that justifies delaying it.

Open-Source Stewardship

Socio-Technical Well-being

Observation

This practice is most credible when the team can point to a recent incident where a mistake was surfaced early and handled without blame.

Annotation

The surrounding process should make it easy to report ambiguity, not just defects. That keeps the card focused on the social system that allows technical issues to be spoken about.

Elaboration

Psychological safety is not softness. It is a control mechanism for surfacing weak signals before they become outages, handoff failures, or silent workarounds.

Generative Evolution