Home / Showroom / Data Strategy at enercity
DE EN
Case Study · Energy Utility

Data Strategy at enercity: From Vision to Roadmap

enercity AG
FormatIntensive strategy sparring
SetupCross-functional · Business + IT
FocusVision · Governance · Use Cases · Enablement
Shared target picture
“Enercity powered by Data” — aligned across business and IT
Governance framework
Roles, principles, processes and responsibilities — explicit and documented
MVP roadmap
Concrete next steps for coordination, marketing, core data and BI integration

Starting point

The energy sector is in the middle of a profound transformation: personalised product experiences, digital customer portals, intelligent grid operations, and regulatory demands that all keep rising at the same time. enercity wanted strategic clarity on the question every utility eventually faces — “how do we become a truly data-driven organisation, and how do we get there from here?”

The starting point was not a missing piece of technology. It was the need to align business and IT on a single, shared target picture — and to translate that into concrete next steps the organisation can actually execute.

The vision: “Enercity powered by Data”

Out of the joint sessions came a clear vision. “Enercity powered by Data” is not just a technical aspiration — it’s a company-wide commitment to making decisions based on data: fast, informed, efficient. Not as a slogan, but as a working principle that the leadership team carries together.

What changed in the conversation: data strategy stopped being “an IT topic with business sponsorship” and became a shared, company-wide commitment with explicit business ownership.

Data platform, governance & use cases

A modern data platform was framed as the technical backbone — not as a tool, but as the data hub at the centre of an integrated, scalable data ecosystem. Three threads were woven into that picture:

  • Self-service capabilities and the data-as-a-product mindset — data sets treated as products with owners, SLAs and consumers, not as artefacts that emerge as a side effect of reporting
  • The interplay between technical and business components — explicit handovers, contracts and language so that every team works on the same model of reality
  • A clear governance framework — roles, processes, principles and responsibilities defined and named, so that decisions don’t need to be re-litigated every quarter

Concrete use cases were at the heart of the discussion as the actual impact drivers — illustrating the complexity of operational execution and the importance of close coordination between business, IT and governance functions. The use cases were not the conclusion; they were the lens through which every architectural and governance question got pressure-tested.

Results & outlook: from ideas to initiatives

After the deep working sessions, the focus moved to a strategic action plan. Four threads emerged as the immediate next steps:

  • Storytelling for the data strategy — how do we communicate the value of this work internally and externally, in a language stakeholders can carry forward?
  • Enablement and upskilling — data literacy as the foundation of a real data culture; without it, governance and platform are just decoration
  • Cross-functional collaboration — business and IT operating as real partners, not as a supplier-customer dyad
  • MVPs & data products — concrete first deliverables defined: coordination, marketing, core data provisioning and BI integration

What stands out is the move from “ideas” to “initiatives”: not a Powerpoint with a list of buzzwords, but four work-tracks with explicit owners, scope and the question of what success looks like.

Lessons learned

A data strategy is not a deliverable; it’s an alignment. A clearly structured, content-rich exchange — where business and IT actually argue with each other on the same data and the same model — is what brings a strategy to life. Workshop facilitation is technique; the substance comes from the room.

The second lesson: tangible MVPs matter more than perfect frameworks. A platform vision is necessary, but it stays abstract until someone owns the first concrete data product and ships it. The sequencing — vision → governance → MVP — only works in that order if every step is explicitly named and assigned.

A heartfelt thank you to the enercity participants for the open dialogue, thoughtful contributions and shared ambition — and to Lennard Nobbe for the trust and the structured way the engagement was set up.

Similar challenge in your company?

30 minutes, no strings attached. We’ll share what we’ve learned in comparable conversations.

Request a conversation