Responsibility at work can easily become a big word.

It can mean sustainability, ethics, wellbeing, inclusion, good governance, long-term thinking, customer impact, or all of the above. And because it can mean so many things, it sometimes becomes something abstract.

Most organizations have strategies, values, goals, and nice-looking slide decks about how work should happen.

But then there is the other layer.

Sustainability in software is often treated as a personal responsibility. A developer might care about energy use, efficient code, cloud resources, or long-term maintainability. But in everyday work, these concerns are rarely built into the structures that guide software teams.