Personal Qualification Analysis

Why This Role is Perfect for Me

Strategic market research meets operational excellence in regulated energy markets

Dritan Mulla

Director Product Management | GERMANTECH Operations GmbH

Strategic Market & Innovation Research

5+ Years PM
€3.5M Project Budget
15+ Teams Led

Why This Role Excites Me

The Director Product & Platform position at HansenCX combines three drivers: Deep Expertise, Strategic Impact, and Measurable Results in a critical market.

1. Regulation as Intellectual Challenge

The complexity of MaKo 2022, Redispatch 2.0, and EEG billing is exactly what interests me: Creating structure from chaos. I see regulatory requirements not as burdens, but as competitive advantages that few systematically exploit.

My EWE Experience: At EWE, I translated BNetzA regulations (switching processes, market communication) into product strategies that improved customer experience AND ensured compliance.

2. Leadership Through Expertise

This role demands leadership through structure and competence, not hierarchy. That matches my leadership style: I lead teams by mastering the most complex requirements and translating them into implementable building blocks.

My Experience: At EWE, I led teams (POs, Developers, Compliance) through complex switching processes – not through hierarchy, but through technical clarity.

3. Stakeholder Management as Craft

Enterprise stakeholders seek influence, not consensus. I've learned to compress conflicting interests into solid priorities – even against resistance. This requires courage, structure, and willingness to make uncomfortable decisions.

My EWE Experience: During multi-brand strategy, I mediated between Marketing (fast launch) and IT (secure billing). I didn't moderate – I created decision templates with clear consequences.

4. Direct Impact on Critical Infrastructure

Energy transition isn't a buzzword but societally critical. Powercloud enables suppliers to operate in regulatory compliance – that's system-relevant work.

5. Plannable Complexity vs. Arbitrariness

Regulatory releases are plannable. Deadlines are hard (e.g., AS4 from April 2024) but not arbitrary. This enables structured work and measurable success.

6. Product Thinking in Regulated Environment

This role combines product thinking (User Stories, Backlog Ownership) with regulatory expertise. This combination is rare – and that makes it valuable.

My Energy Sector Expertise

During my time at EWE and strategic transformation projects, I gained direct insights into energy suppliers' challenges.

EWE AG – Strategic Energy Sector Projects

Product Management & Strategy Development for a major German energy supplier

🎯 Core Projects with Direct Relevance for powercloud:

EWE Corporate Strategy
  • Market analyses for regulatory requirements (MaKo, Redispatch, EEG)
  • Product roadmaps for digital energy supply
  • C-Level stakeholder management (Board, Division Heads)
Switching Portal – Digital Customer Processes
  • Automation of switching processes (supplier changes, tariff changes)
  • Requirements engineering: Translating regulatory requirements (BNetzA decisions) into User Stories
  • Customer experience optimization: Self-service portals

Relevance for HansenCX: Exactly the processes that MaKo 2022 standardizes – I built them from the customer perspective.

Digital Multi-Brand Strategy
  • Multi-brand architecture: Multiple brands on one technical platform
  • Tariff modeling: Time-variable tariffs, green energy products
  • Billing systems: Integration of EEG surcharges, grid fees, taxes
P2P Trading & Smart Contracting
  • Peer-to-peer energy trading: Prosumers sell electricity directly to neighbors
  • Smart contracts: Blockchain-based automation
  • Regulatory feasibility: EnWG compliance, supplier roles, balance groups

GERMANTECH Operations GmbH (since 01/2020)

Director Product Management | Strategic Transformation Projects

Relevant Achievements for HansenCX Role:

Interim CPO LIQUIBOT.health Led MDR-compliant product (€3.5M budget) from idea to market Comparable complexity to MaKo/Redispatch/EEG
Agile methodologies introduction Design Thinking, Lean Startup, Strategic Planning Toolkit for requirements translation

Why My EWE Experience Perfectly Fits powercloud:

I know your customers from the inside

EWE is a typical powercloud customer. A large utility with complex requirements, multi brand strategy and regulatory pressure. I understand how energy providers think and make decisions.

Switching assistant means I lived through MaKo processes

The switching processes I created are exactly what MaKo 2022 standardised. I felt the pain points myself, from EDIFACT chaos to manual rework. I know exactly where powercloud needs to act.

Multi brand strategy means product flexibility

I built several brands on one technical platform. That is exactly what powercloud customers need. I understand why tariff modelling is so critical.

P2P trading means understanding the future

Prosumer models, smart contracts and decentralised systems. I did not just read the theory, I built prototypes and tested them in pilots. Powercloud must be ready for this future.

Corporate strategy means C level language

I discussed digital transformation with the EWE board. I can build business cases, argue ROI and define strategic priorities. This is the language your customers use.

Regulation translation bonus MDR

Translating MDR requirements into user stories is the same craft as translating MaKo processes into epics. This craft is transferable and I master it.

My Role as "Translator & Anchor"

The three critical questions from the job description – and my answers.

01

Can you decompose MaKo processes into Epics/User Stories?

My Answer: Yes – and I've already done it in the energy sector.

Specifically at EWE (Switching Portal):

  • ✅ Translated BNetzA decisions on switching processes into implementable User Stories
  • ✅ Decomposed EDIFACT message formats into functional requirements
  • ✅ Structured supplier switching process: 15+ substeps into Epics
My Method: I decompose regulatory texts into MUST requirements (functional), SHOULD requirements (quality), and COULD requirements (nice-to-have). Then I map them to user journeys and define measurable acceptance criteria.
02

Do you master stakeholder conflicts?

My Answer: Yes – and I actively seek these conflicts.

My Approach: I see stakeholder conflicts not as problems, but as signs of unclear priorities. My job is to force these conflicts so decisions can be made.

Example (EWE – Multi-Brand Strategy): Conflict between Marketing ("New brand must go live in 6 weeks!") and IT/Billing ("Billing system needs 4 months for new tariff structure").
  • My Solution: Decision template with 3 options:
    • (A) Launch with standard tariffs – 6 weeks
    • (B) Launch with custom tariffs – 4 months
    • (C) MVP with 1 pilot tariff – 8 weeks
  • Consequences Named:
    • Option A: Missing brand differentiation (Risk: Cannibalization)
    • Option B: Market window missed (Risk: Competition)
    • Option C: Compromise, but realistic
  • Result: Management chose Option C. I forced the decision by making risks transparent – even against marketing resistance.
03

Are you ready to be "the Anchor"?

My Answer: That's exactly the role I seek.

Why? I'm most productive in situations where no one else takes responsibility. I don't wait for structure – I create it.

Concrete Examples:
  • 📍 EWE – Switching Portal: Project started with vague requirements. Within 2 weeks, I created a structured analysis: 15 regulatory MUST requirements identified, 8 user journeys defined, roadmap with 3 MVP phases created.
  • 📍 LIQUIBOT.health: Project without clear product strategy (6 months chaos). Within 4 weeks, I created roadmap, prioritized certification, focused team. Result: Market launch after 9 months (instead of planned 18).

Strategic Fit: Summary

What HansenCX Seeks

  • Energy sector / regulated market expertise
  • Product craftsmanship (PO, Requirements Engineering)
  • Enterprise-level stakeholder management
  • Leadership of ~6 people (POs & Engineers)
  • Structured working approach

What I Bring

  • Energy sector expertise (EWE: Strategy, Switching, Multi-Brand, P2P Trading)
  • Product Management (EWE Product Owner, Interim CPO €3.5M)
  • Stakeholder Leadership (EWE C-Level, Enterprise Customers)
  • Team Leadership (POs, Engineers, Compliance)
  • Structure Creation (EWE: Chaos → Roadmap in 2 weeks)

My Self-Assessment

This role is not a compromise, but a logical evolution of my expertise. I bring the regulatory translation capability that HansenCX needs – and I seek exactly the kind of responsibility that this role demands.

Strengths I Bring:

  • I know your customers: EWE is a typical powercloud customer – I know how they think, decide, prioritize
  • Built switching processes: What MaKo 2022 standardizes, I developed at EWE from the customer perspective
  • Regulatory translation: BNetzA decisions → User Stories (EWE) + MDR → Epics (LIQUIBOT)

Learning Areas I See:

  • MaKo 2022 in Detail: I know switching processes from EWE times (EDIFACT), but need to learn the 30+ new MaKo processes
  • Redispatch 2.0: I know the theory, but need to understand operational implementation in powercloud

My Solution: First 90 days = Deep dive into MaKo 2022, Redispatch 2.0, EEG details. Goal: After 3 months, I am the technical anchor for the team.

Next Steps

This analysis shows why the role as Head of Product at HansenCX perfectly fits my expertise and goals.