Skip to content
Back

About

Leon Köllerwirth

Executive Technology Leadership

I connect business accountability, product and platform architecture, governance and delivery, from the design to the running system.

The foundation is more than 20 years of responsibility: from software engineering and building and leading engineering organisations to enterprise architecture, information security and product accountability.

Why I think differently

Transformation starts with accountability, not technology.

My work starts with business value, friction, ownership, governance and the people who must make the new operating model work.

  • Strategy before technology.

  • Business architecture before tools.

  • People and adoption before automation.

  • Execution before theory.

Experience pillars

The combination matters more than any single role title.

Technology and AI transformation need translation between leadership intent, product reality, architecture constraints and organisational behaviour.

  • People Leadership & Teams

    Staff and develop teams, distribute responsibility, carry the decisions nobody likes to make, and stay approachable in difficult situations where results depend on people.

  • Enterprise Product Leadership

    Owning roadmaps, backlogs, releases and product decisions across complex environments where delivery must survive real operational constraints.

  • Architecture & Engineering

    Designing systems, platforms and integration paths with enough technical depth to separate viable transformation from attractive concepts.

  • Security & Regulated Environments

    Working with governance, auditability, access control and risk in contexts where operational trust matters as much as innovation.

  • Operations & Transformation

    Building IT organisations, improving processes and reducing friction where business outcomes depend on execution, not slideware.

  • Psychology & Adoption

    Understanding that transformation fails when people, incentives, habits and resistance are treated as secondary to the technology.

Selected enterprise context

Credibility from environments where complexity is real.

Selected context only. The point is not chronology; it is why the judgment transfers to technology and AI transformation.

  • Daimler / Mercedes-Benz financial-services context

    Enterprise architecture · cybersecurity · regulated environment

    Experience with board-level reporting, European market complexity, security governance and incident leadership in a BaFin-regulated financial-services environment.

  • SMA Solar / energy context

    Product leadership · business-critical embedded platform · energy sector

    Interim product ownership across energy software, product teams, release priorities and architecture work where reliability and execution discipline matter.

  • Tönnies / operations context

    IT management · engineering leadership · operational transformation

    Greenfield IT, production-adjacent systems, traceability, operations and delivery structures shaped in an environment where process performance is business performance.

How that turns into AI-native products

An AI-native platform needs business judgment, architecture judgment and adoption judgment at the same table.

This is where experience becomes practical: deciding where AI belongs, how it gets built and how it stays fit for approval.

  • Identify AI opportunities

    Find where autonomy can reduce friction, improve decisions or increase execution capacity.

  • Design pilots

    Define narrow pilots with value logic, boundaries, ownership and success criteria.

  • Align stakeholders

    Translate between executives, product teams, architecture, security and operations.

  • Reduce organisational friction

    Treat coordination cost, decision latency and knowledge fragmentation as transformation inputs.

  • Scale responsibly

    Move from isolated pilots toward governance, adoption and operating models that can hold up.

Beyond work

Away from architecture and governance, I photograph. Selected work at hamudi.de.

Next step

Understand what this means for your organisation.

The entry point is a clearly scoped assessment: 10 working days, fixed fee, one results conversation. A binding proposal follows a 20-minute introductory call.