Management & Leadership – Control with System, Leadership with Attitude

Management and leadership belong together – but are not the same. Management creates clarity: analyzing situations, evaluating options, deciding, prioritizing, controlling resources, and delivering results reliably. Leadership creates effectiveness in the team: providing orientation, shaping culture, enabling responsibility, and developing people so that performance does not come from "above" but arises from the system.

In practice, leadership is the part that decides whether management can take hold at all: whether standards are lived, whether problems are openly addressed, whether responsibility is taken – and whether change is really anchored.

The core difference in one sentence:
- Management ensures that things are done correctly (planning, prioritization, control, monitoring).
- Leadership ensures that the right things are done – and that people support them (meaning, attitude, behavior, culture).


Leadership means being a role model – every day, in small things

Leadership works less through words than through behavior. That's why "being a role model" is not a soft topic for me, but an operational lever:

- Show respect – especially under pressure.
- Live integrity – make decisions traceable, keep promises, clearly define boundaries.
- Live a culture of mistakes – look for causes instead of culprits, learn instead of justifying.
- Live standards – not only demand them, but also consistently use them yourself.
- Show openness and willingness to learn – even as a leader, don't be "finished".

The values that guide me in everyday life – respect, tolerance, empathy, appreciation, integrity, sense of responsibility, reliability, openness, and willingness to learn – are not a claim, but the standard by which teams can experience leadership.

Leadership is not a style – but a conscious choice depending on the situation

There is no one right leadership style. There is the right approach for maturity, risk, time pressure, and task:

- Situational leadership: guide, coach, support, or delegate consistently, depending on ability and commitment.
- Transactional leadership: goals, roles, standards, and consequences – important for stability, security, and performance.
- Transformational leadership: meaning, direction, motivation – important for change, culture, and innovation.
- Agile/servant leadership: set framework, remove obstacles, promote ownership – leadership as enablement rather than control.
- Coaching leadership: ask questions, promote reflection, build problem-solving skills – especially strong in KVP environments.

The common denominator: leadership is effective when it enables development – not dependence.


My leadership principle: "If I do my job right, I make myself superfluous."

This sentence does not describe withdrawal, but maturity: a team is so developed that it can stabilize the operational routine itself. Leadership does not become less important – it changes focus:

- In everyday life, the system runs over routines, standards, visualization, clear responsibilities, and decision logic.
- I am needed especially when it comes to conflicts, emergencies, escalations, or decisions on direction.
- This creates space for what makes organizations strong in the long term: strategy, further development, technology and trend evaluation, capability building.

The goal is a team that can, wants, may, and does – i.e., combines competence, motivation, authorization, and implementation power. Exactly there, leadership becomes measurable: not by the presence of the leader, but by the autonomy of the system.


From "being led" to "self-steering": the logic of a learning organization

A self-organizing, self-learning company does not arise from a new organizational chart – but from consistent training in everyday life:

- Transparency: make problems visible (do not conceal them).
- Problem solving: causes instead of symptoms (e.g., structured via PDCA/A3/DMAIC logic).
- Decision-making ability: clear guidelines, who decides what – and according to which criteria.
- Competence building: leadership develops leadership; experts develop experts.
- Learning loops: standards are not "rigid", but the best known state – until the next improvement.

This is how KVP remains alive: because the ability to improve does not depend on individual people, but is anchored in the system – and because new technologies/methods are not a "trend", but targeted further development: what really helps the team? What increases stability, quality, speed, safety – and learning ability?


My practical approach in the context of the 5M Lean House

I combine management and leadership into a common system – with a clear goal: stabilize value creation, enable people, accelerate learning.

- Motivation & Mindset: meaning, responsibility, psychological safety – so that problems come openly to the table.
- Management & Routines: control via standards, KPIs, shop floor logic, and clean escalation – so that leadership is not "firefighting".
- Develop people: lead in a coaching style, couple delegation with competence building – so that "may" really becomes "can".
- Anchor change: not as a project, but as a habit in collaboration and decision-making paths.

This is how leadership arises that does not make people dependent, but self-sufficient – until the point where my guiding principle becomes a reality:

If I do my job right, I make myself superfluous in the operational routine – and the system becomes stronger than the person.