Sustainability Is an Architecture Problem-and a Skills Problem

We often discuss the green transition as though better technology will do most of the heavy lifting.

More efficient infrastructure. Cleaner energy. Smarter software.

But technology cannot compensate for an organisation that does not know what to measure, which trade-offs to evaluate, or who owns the outcome. The missing layer is often human capability.

University College Cork’s launch of a Sustainability Academy caught my attention for precisely this reason. Its proposed model combines short, stackable, accredited courses with research expertise and industry practitioners to address sustainability skills shortages across Ireland’s workforce.

The important signal is not another educational programme. It is the recognition that sustainability must become an operational competency-not remain a specialist conversation.

From reporting obligations to design decisions

As a software architect, I see a useful parallel with cybersecurity.

For years, security was treated as a review conducted after development. Mature organisations eventually recognised that it belongs inside requirements, architecture, procurement and everyday engineering decisions.

Sustainability needs a similar shift.

A dashboard might report energy consumption. But the decisions shaping that consumption happen much earlier: when teams select infrastructure, establish data-retention policies, choose deployment regions or decide whether an AI workload needs a large model at all.

Sustainability reporting describes the system. Sustainability capability changes how the system is designed.

This distinction matters because efficiency is not automatically sustainability. Reducing the cost of an AI inference may encourage far greater usage. Moving a workload to the cloud may improve utilisation, but its wider impact still depends on workload behaviour, electricity sources and hardware lifecycle.

The architectural question is therefore not simply, “Can we make this cheaper?”

It is, “Can we deliver the required outcome with fewer resources, without compromising resilience, accessibility or trust?”

Build capability where decisions happen

Short, stackable learning is particularly relevant to working professionals. A procurement officer, cloud engineer and municipal administrator do not need identical sustainability curricula.

They need a shared foundation-and different applied skills.

For enterprise leaders, I would translate this into three priorities:

• Teach decision-making, not just terminology. Engineers should evaluate workload utilisation and data growth. Procurement teams should question lifecycle assumptions. Executives should understand uncertainty in environmental metrics.
• Connect learning to live systems. A course should lead to a practical exercise: reviewing an overprovisioned application, assessing a retention policy or comparing alternative service designs.
• Measure changed behaviour. Completion certificates are useful signals, but the stronger evidence is whether teams make better decisions afterward.

There is a trade-off here. Standardisation makes training scalable; contextualisation makes it useful. The strongest programmes will need both.

Universities can contribute research discipline and credible assessment. Practitioners can expose learners to messy constraints: legacy infrastructure, incomplete data and budgets that cannot accommodate a wholesale rebuild.

Neither perspective is sufficient alone.

A practical opportunity for Northeast India

This has a direct relevance to Northeast India, where digital services must often operate across uneven connectivity and constrained local infrastructure.

Consider a public-service application designed around constant connectivity, repeated document uploads and unlimited data retention. Its inefficiency is not only computational. It also consumes citizens’ time, bandwidth and money.

Offline-capable workflows, smaller data transfers and thoughtful retention policies can improve access while reducing resource demand. Those benefits should be measured rather than assumed-but they belong in the same design conversation.

For our universities, startups and public institutions, the opportunity is to connect sustainability education with practical digital engineering.

Start small: one team, one service, one measurable improvement. Establish a baseline, document the trade-offs and turn the results into reusable learning.

The green transition will not be delivered by a sustainability department alone.

It will advance when responsible resource use becomes an ordinary part of professional competence-and an expected property of good architecture.

---

About the Author: Sanjeev Sarma is the Founder Director and Chief Software Architect at Webx Technologies. With a core focus on Generative AI integration, Cloud-Native Scalability, and Enterprise Software Architecture, he has spent over two decades driving digital transformation across Northeast India and beyond. Beyond his corporate leadership, Sanjeev is deeply invested in shaping the future of the IT industry. He serves as an Industry Expert on the Board of Studies for Assam Don Bosco University’s School of Technology, advises state technology committees, and actively mentors emerging tech startups at STPI. He brings a unique, dual perspective of high-level enterprise execution and future-ready academic curriculum development.