---
title: "Role Evolution & Works Council"
description: "How existing IT roles evolve into cloud equivalents, the emerging role of the Data Sovereignty Officer, and why the works council can be a transformation ally."
sidebar:
  order: 4
  label: "Roles & Works Council"
source_url: "https://framework.stackit.cloud/advisory/cultural-change/roles-and-works-council/"
source_file: "docs/advisory/cultural-change/roles-and-works-council.mdx"
---

## The role evolution map

The most common fear in cloud transformations: "My position will disappear." The right response is not reassurance — it is a concrete map that shows where the journey leads.

| Current role         | Cloud equivalent                     | New focus                                       | Training track |
| -------------------- | ------------------------------------ | ----------------------------------------------- | -------------- |
| System Administrator | Platform/Cloud Engineer              | IaC, managed services, automation               | Track C        |
| DBA                  | Managed Database Specialist          | Database-as-a-Service, performance optimisation | Track C + D    |
| Network Engineer     | Cloud Network Architect              | Software-defined networking, VPC design         | Track C + D    |
| Security Analyst     | Cloud Security Engineer              | IAM, policy-as-code, DevSecOps                  | Track E        |
| IT Controller        | FinOps Analyst                       | Cloud economics, tagging, chargeback management | Track F        |
| IT Operations        | Site Reliability Engineer (SRE)      | Observability, incident response, runbooks      | Track C        |
| Enterprise Architect | Cloud Solution Architect             | Cloud-native patterns, multi-service design     | Track D        |
| Project Manager      | Cloud Product Manager / Scrum Master | Agile delivery, team coordination               | Track A + B    |

**Core message:** Cloud transformation does not eliminate IT roles — it evolves them towards higher-value work. Manual configuration management (low value) is replaced by IaC authorship (higher value).

## Data Sovereignty Officer: an emerging role

As DACH organisations operationalize their sovereign cloud strategies, a new functional role is emerging. In some organisations it sits with the CISO, in others with the Data Protection Officer; in regulated industries it often becomes a standalone function.

**Responsibilities of the Data Sovereignty Officer:**

- Maintaining workload classification (sovereignty levels 1/2/3)
- Reviewing new architecture proposals for sovereignty implications
- Liaison with the Data Protection Officer on cloud data residency questions
- Maintaining the sovereignty matrix (living document)
- Communicating with customers and partners about sovereignty evidence

**Profile:** A combination of technical cloud understanding, data protection law knowledge and communication capability. Often filled by: an experienced security architect with a data protection background, or a Data Protection Officer with technical further training.

## Works council: engage early, do not steamroller

In German organisations, the works council (Betriebsrat) has **co-determination rights** regarding workplace changes, including changes to IT systems used by employees (§ 87 Para. 1 No. 6 BetrVG). Cloud transformation touches on these co-determination rights in many respects.

**What co-determination means in cloud transformation:**

| Area                                 | Co-determination relevance                      | Recommendation                          |
| ------------------------------------ | ----------------------------------------------- | --------------------------------------- |
| Monitoring systems (Observability)   | High — if employee behaviour becomes measurable | Early information, clear demarcation    |
| Changes to working processes         | Medium                                          | Information before decision             |
| New work tools (cloud console, IDEs) | Medium                                          | Works agreement for substantial changes |
| Role elimination or change           | High                                            | Qualification agreement                 |
| Shift work / on-call                 | High                                            | Works agreement required                |

**The golden rule:** Inform the works council before decisions are made — not after. Confronting the works council with a fait accompli creates distrust and resistance. Engaging them as a partner wins a transformation ally.

**What the works council typically wants:**

- Assurance that no redundancy decisions are hidden behind the transformation
- A qualification commitment — concrete promises for training and retraining
- Transparency about monitoring and data protection for employees
- Adequate advance notice before changes

**Recommended measure:** The Cloud Strategy Board invites the works council chair to an information meeting before the cloud strategy is adopted. The signal: "We take you seriously."

## Qualification agreement with the works council

In larger organisations, a written qualification agreement is recommended that governs:

- Which training offerings the organisation provides for all employees
- How much working time is released for training
- How employees are treated if they do not successfully complete the qualification
- What role the works council plays in monitoring the qualification programme

## Practical steps

1. **Complete the role evolution map** for all IT roles in your organisation
2. **Formally communicate the training commitment** (before the works council)
3. **Convene the works council information meeting** — before the strategy resolution
4. **Negotiate a qualification agreement** with the works council
5. **Define and staff** the Data Sovereignty Officer role