Sustainable technology and GreenOps: Role profiles and accountability

We expect that many organisations will not create a dedicated GreenOps analyst post, so the profiles are written to be added to roles that already exist. The table shows three patterns we have observed. 

Most medium and large organisations will already have someone doing the work of the accountable technology owner, the business service owner and the sustainability lead, whatever their titles. The patterns differ in who does the operational work, while accountability for the result stays with those three roles.

The profiles are best read as points in an accountability system rather than a proposed organisational structure. An organisation may combine them, embed them in existing jobs or create specialist roles. What matters is that the necessary responsibilities and decision rights are covered at the appropriate SFIA levels.

A common starting point for sustainable technology and GreenOps is to list operational activities: collecting energy data, monitoring utilisation, improving infrastructure efficiency or producing sustainability reports. These activities matter, but organisations should not start by creating operational roles in isolation. Analysts whose findings have nowhere to go produce dashboards that nobody owns.

Start instead with accountability and decision-making, then work down to operational capability.

1. Start with outcomes and decisions. Identify the sustainability outcomes that matter to the organisation and the decisions that most influence them, such as technology strategy and investment, architecture and cloud strategy, service levels, infrastructure capacity, service demand, hardware refresh, sourcing and contracts, facilities, and measurement and reporting. The decision table later in this document is a starting list.

2. Identify senior accountability (level 7). Decide who is accountable for technology’s contribution to sustainability outcomes. This may be a CIO, CTO or another senior leader, and SFIA does not require a particular title. At this level the SFIA contribution often comes from existing skills such as Strategic planning (ITSP), Governance (GOVN) and Portfolio management (POMG), rather than from a sustainability-labelled skill. What matters is that someone has authority over priorities, investment, governance and the trade-offs that operational teams cannot make themselves.

3. Identify cross-functional leadership (level 6). Identify who shapes policy and influences decisions across functions: sustainability policy and reporting, procurement requirements, architecture standards, investment approaches, demand and service decisions, and governance.

4. Establish operational ownership (level 5). Decide who will make sure the practices work in each area. These may be GreenOps leads, infrastructure and cloud managers, software engineering leads, architects, finance or FinOps leads, procurement leads and facilities managers. Level 5 is where SFIA moves from performing activities to authoritative guidance and accountability for significant work outcomes.

5. Then define practitioner and analyst capability (levels 2,3 and 4). Once the accountability chain is clear, define the work of collecting reliable data, analysing utilisation, finding inefficient resources, applying agreed optimisation, maintaining baselines, testing evidence and identifying improvements.

6. Connect each finding to a decision owner. Every material finding should have a route to someone with authority to act on it. An analyst can identify over-provisioning, but a service owner may need to change demand, finance may need to change funding assumptions, procurement may need to change contract terms, architecture may need to change standards and a senior technology leader may need to change investment priorities.

The sequence can be summarised as follows.

This is not an argument against bottom-up initiative. Operational teams often see the problems first. The point is that operational capability needs clear routes to the people who control the decisions, otherwise the organisation can measure problems but lacks the authority to resolve them.

The table sets out, for SFIA levels 2 to 7, who produces the evidence, who decides, who is accountable and what evidence they work with. The level names are SFIA’s own.

Typically the accountability chain most often breaks between levels 4 and 6.

• Analysts produce findings, but nobody with the authority to act on them owns the decision, so the findings stay in dashboards.
• Each finding at levels 3 and 4 needs a named owner at the level that controls the budget, contract or standard involved.
• Every level above depends on the evidence produced at levels 2 and 3.
• If an organisation treats collecting it as an administrative chore with no quality expectations, senior decisions and external reports end up based on modelled estimates without anyone noticing.
• Separating measured from modelled data has to start with the people who collect it.

This is the standard SFIA responsibility model

The progression above is not specific to GreenOps. It applies SFIA’s generic attributes, which describe how autonomy, influence and complexity grow at each level. Much of the argument about authority and accountability rests on these attributes rather than on the professional skills alone.

Read this way, the GreenOps lead’s typical problem of responsibility without authority is easy to explain.

• Level 5 brings accountability for significant outcomes within an area, but the defined authority over financial aspects of a significant area of work, and the influence over strategy, sit at level 6.
• Decisions about money, policy and targets therefore need level 6 or 7 owners.

One progression, from analyst to owner

The four GreenOps and technology leadership profiles show what changes as a role moves up the levels.

Moving to level 4 gives the role ownership of method, and level 5 adds authority over priorities and standards within an area. Many decisions that change the footprint need level 6 or 7 authority, because they involve money, policy and targets.

It would be easy to conclude that SFIA covers sustainable technology through one sustainability skill and leaves the rest to chance. The profiles show a more complete picture, built from five layers.

1. An explicit sustainability anchor. Sustainability (SUST) covers reducing environmental impact and compliance with relevant standards and regulations. Its guidance already includes sustainability metrics and benchmarks and policies to minimise the environmental impact of IT operations and assets.

2. Sustainability distributed across established professional skills. Most GreenOps work is carried by skills whose names do not mention sustainability: ITOP and CPMG for operational efficiency, ARCH and IFDN for design decisions, SWDN, PROG and NFTS for software efficiency, MEAS, DAAN and DATM for evidence, SORC, SUPP, ITCM and ASMG for supply chain and lifecycle, FIAN, COMG, INVA and BUDF for financial decisions, and ITSP, GOVN and POMG for strategic accountability. Several of these already mention sustainability or resource efficiency in SFIA 9, including ITOP, CPMG, ITCM, NFTS and Facilities management (DCMA).

3. Levels that show this is not just operational work. SFIA adds a vertical dimension that a task list lacks: evidence, then analysis, then methods, then accountable management, then organisational policy, then enterprise strategy. This helps organisations see where operational capability exists but decision authority is missing.

4. Support for specialist and embedded models. The same framework works whether an organisation has specialist GreenOps roles, sustainability responsibilities embedded in existing jobs, or a mixture.

5. Domain knowledge kept in context. PUE, WUE, CUE, emissions factors, Scope 1, 2 and 3, carbon accounting methods and cloud provider data can be attached to the relevant roles and skills as knowledge, standards, measures and methods. They do not need to become SFIA skill names.

Put together, the model runs from need to skill to level to role, with context-specific knowledge attached at the end. Here is an example based on reducing over-provisioned cloud capacity

Many of the decisions that shape technology’s footprint are made outside the teams that measure it. The table maps the main ones to the profile that usually owns the decision, the profile that supplies the evidence and the evidence the decision needs. Every name in it is one of the twelve profiles below.

SFIA does not attempt to describe the complete professional profile of a CFO or an estates director. It can, however, describe the digital and technology-related capabilities those people need, and the technology side of each interface: producing evidence decision-makers can use, and allocating impact back to whoever creates the demand.