Expertise

Understand technology. Shape organisations. Connect systems.

My focus lies where technical depth, clear structures and effective collaboration come together.

From software, automation and industrial networks to requirements, systems engineering, leadership, processes and industrial management, the individual discipline matters less than how the disciplines work together.

01 / Engineering

Understand technical systems in depth.

Technical depth is not an end in itself. It provides the basis for assessing impact, risk and decisions with substance.

  1. Software & Automation

    Software-oriented system development, automation and functional logic – from requirements to robust implementation.

  2. Industrial Networks

    Communication architectures, Ethernet-based industrial networks, redundancy, diagnostics and the behaviour of distributed systems.

  3. Systems Engineering

    Structuring and understanding complex technical systems across functions, interfaces, dependencies and lifecycles.

  4. Requirements Engineering

    Formulating, structuring and tracing requirements clearly through to verification.

02 / Industrial Management

Organise technical work effectively.

For me, management is not about distance from engineering, but about enabling good technical work through clear goals, conditions and decisions.

  1. Leadership & Team Development

    Creating direction, clarifying responsibility, developing capability and enabling technical teams to work effectively.

  2. Project Management

    Structuring complex initiatives, making dependencies visible, preparing decisions and consistently following execution.

  3. Process Improvement

    Analysing workflows, reducing unnecessary friction and improving quality and speed together.

  4. Governance & Continuous Improvement

    Establishing clear decision paths, reviews, responsibilities and continuous improvement as part of everyday work.

03 / Systems & Organisation

Interfaces determine the outcome.

Many technical problems do not originate within one discipline, but at the interfaces between technology, process and organisation.

  1. Requirements & Traceability

    Connecting requirements, specifications, verification and decisions throughout the engineering process.

  2. Engineering Lifecycle

    Treating engineering not as a sequence of documents but as a continuous lifecycle from requirements through operation and improvement.

  3. Interfaces & Collaboration

    Connecting disciplines, roles and organisational units so interfaces do not lead to information loss or unclear responsibility.

  4. Quality & Governance

    Designing reviews, quality gates, responsibilities and decision structures so quality is created early rather than inspected only at the end.

Interplay

The most interesting questions lie between disciplines.

  1. How does a requirement become an unambiguous, implementable and verifiable technical solution?

  2. How can complex technical dependencies be structured so teams can make well-founded decisions?

  3. How should processes and responsibilities be designed so technical quality is not lost through organisational friction?

  4. How can technical insight feed continuous improvement of systems, processes and collaboration?

For me, expertise emerges from combining depth with perspective.

Understanding technical detail, recognising relationships and translating them into clear structures and decisions is where I focus.