digest
Short Summary
Main recommendation: Develop your own leadership code, a short written set of statements that distills how you want to lead, then share it with others and live by it daily. The speaker, Lars Sudmann, frames the "reality gap" between believing leadership matters and experiencing good leadership as the problem this code addresses. He describes it as a five-step process that turns self-knowledge, inspiration, and written clarity into consistent, predictable behavior.
Key Points
- Leadership fails often because leaders misjudge themselves, which can mislead others; start by distilling your strengths and values into an "essence droplet."
- Draw inspiration from people outside yourself, such as a coach, a CEO, or a family member, and ask how they would act in your situation.
- Write the code down, limited to 25 words per essence statement, because writing exposes vague thinking that seems clear only in your head.
- Predictability matters: a leader's inconsistency confuses teams, so aim for high predictability while still allowing autonomy.
- The "illusion of transparency" means what is obvious to you may not be obvious to others, so share your code face to face early in a working relationship.
- Keep the code active by reading it daily and checking your decisions against it, to counter the daily "FUZZ" of firefighting and interruptions.
Details Worth Noting
- Concrete instructions:
- Ask yourself how you want to be as a leader, and identify your strengths, values, and how you best perform.
- Identify frequently made leadership mistakes (FMLMs) you have made, and write them down as part of your self-knowledge.
- Think of someone who inspired you, examine how that person acted, and distill it into a droplet of essence: a statement of how you will act.
- Write your code down, aiming for five statements, each about 25 words, which the speaker says are long enough to capture essentials but short enough to remember.
- Share the code early in a leadership interaction, ideally face to face, saying how you lead, your standard, your values, and your FMLMs.
- Put the code on a small card (the speaker uses an A6 card), read it every day for about one minute, and each morning ask how the leader you want to be would handle today's challenges.
- The speaker's example: a self-described proactive leader who over-shielded his team from information was asked for more information, and he revised his essence to "an optimal information balance" with regular check-ins.
- The project manager example: she moved from micromanaging to calm, clear leadership after drawing inspiration from a new volleyball player on her national team, and her droplet promised calm clarity, direction, and listening.
- The "E on the forehead" experiment (Gilovich and others) illustrates the illusion of transparency; the speaker notes that in the study, people in power positions took others' perspectives less.
- FUZZ stands for firefighting, unplanned interruptions, and a schedule stuffed with meetings.
Bottom Line
A leadership code only works when it is specific, written, shared with others, and reviewed daily; the speaker's core claim is that consistent, predictable leadership comes from deliberate self-definition rather than assumption.
