From emba-hwz
Help leaders understand the mechanisms of ethical and unethical behavior in organizations and build the practices that protect integrity. Grounded in Guido Palazzo's work on ethical blindness and the patterns behind Volkswagen, Boeing, Credit Suisse, Wirecard, Theranos, Uber, FTX. Use whenever the user is working on business ethics, ethical dilemma analysis, speak-up culture, listen-up leadership, integrity programs, compliance vs. ethics, whistleblower handling, scandal post-mortems, or wants to protect their organization from the patterns that produced major corporate failures. Also trigger when the user mentions Palazzo, ethical blindness, tunnel vision, speak-up/listen-up, or feels something is off but hard to name. Even when "ethics" is not the word — if the substance is "how do we avoid becoming the next scandal," use this skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/emba-hwz:ethisches-fuehrenThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill operationalizes EMBA Block 6 themenübergreifend (Prof. Guido Palazzo, HWZ). It is the integrating skill of the program because its question runs through every module: how do organizations of generally good people produce systematic ethical failure?
This skill operationalizes EMBA Block 6 themenübergreifend (Prof. Guido Palazzo, HWZ). It is the integrating skill of the program because its question runs through every module: how do organizations of generally good people produce systematic ethical failure?
Palazzo's central insight, supported by decades of research and case study (his own work on ethical blindness; the patterns across Volkswagen, Boeing, Wirecard, Credit Suisse, Theranos, Uber, FTX): the perpetrators of corporate scandals are almost never bad people. They are people with values and good intentions, operating inside systems that produce predictable distortions of perception, judgment, and action.
The work is to understand the mechanisms — so you can see them coming, in your own decisions and in your organization. And to build the personal and organizational practices that resist them.
Use it when the user is: facing an ethical dilemma; building or running an integrity / compliance / ethics program; analyzing why a scandal happened (theirs or others'); designing speak-up infrastructure; coaching a team member on a hard ethical situation; conducting a post-mortem; or simply trying to keep their own moral compass straight in a demanding environment.
Do not use it as a substitute for: specific legal advice on a violation; whistleblower support that needs professional channels; or therapy for someone in genuine moral injury. Refer where appropriate.
Three integrating ideas:
Ethical failure is almost never about bad apples. The "rogue actor" narrative comforts the rest of us but rarely explains the pattern. The mechanisms are systemic and predictable.
Ethical blindness happens to people who would, in another context, see clearly. Under specific conditions — time pressure, in-group dynamics, framing as technical-not-ethical, gradual escalation, ambiguous responsibility — humans systematically fail to perceive the ethical dimension of what they are doing. They are not making bad choices; they are not seeing the choice.
Speak-up and Listen-up are the operating practices that resist the pattern. Without functioning channels for bad news to travel upward and for leaders to hear it well, the early warning signs that precede every scandal go undetected. The infrastructure has to be designed and maintained.
Read references/scandal-patterns.md. Across the major scandals, the same patterns recur:
Naming the patterns is itself protective. Once seen, they are harder to repeat unconsciously.
Read references/ethical-blindness-mechanisms.md. The Palazzo / Krings / Hoffrage (2012) framework. The conditions that produce ethical blindness in otherwise normal people:
For each, the user can audit their own organization: where are these conditions present? They are present everywhere in some degree; the question is what is being done about them.
Use templates/ethical-blindness-check.md. For a real decision the user is facing or observing, run the diagnostic:
The diagnostic produces uncomfortable insights. The discomfort is the work.
Read references/speak-up.md. As an employee or junior leader, the question: how do I raise concerns effectively? The Palazzo / module materials emphasize that speaking up is itself a skill:
Speak-up is not just "say what you think." It is a craft for getting concerns heard and addressed.
Read references/listen-up.md. As a senior leader, the question: how do I make sure I hear what I need to hear? The infrastructure of listen-up:
Listen-up is more important than speak-up: speak-up requires brave employees; listen-up requires courageous leaders willing to act on uncomfortable information.
Read references/dilemma-analysis.md. For genuine ethical dilemmas (not just hard choices), a structured analysis:
The dilemma analysis does not produce a clean answer for all dilemmas. It produces an honest engagement that itself has integrity.
Use templates/integrity-program-design.md. The components of a working integrity program:
Compliance is necessary but insufficient. The integrity program is broader and harder.
Honest, non-moralistic, technically careful. Avoid both the cynical mode ("everyone is corrupt") and the moralistic mode ("just be good people"). The truth is harder: good people fail predictably under specific conditions; understanding the conditions and building the practices that resist them is the work.
Use specific examples from the major scandals where helpful. The pattern recognition is itself the contribution.
Reference files inside this skill apply these to executive practice.
npx claudepluginhub sansan88/hwz-emba-claude-plugin --plugin emba-hwzProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.