Self-Awareness
Understanding your strengths, blind spots, and leadership style
Week 1 Day 1: Nobody Taught You How to Lead
Most leaders were never trained to lead. They were good at their job, so someone handed them a team. That is not preparation -- it is a promotion.
Read commentary →Week 1 Day 2: Wonder -- The Gift of Asking Why
The best leaders are not the ones with all the answers. They are the ones who cannot stop asking questions nobody else thought to ask.
Read commentary →Week 1 Day 3: Galvanizing -- Moving People Without Commanding Them
Galvanizing is not about giving speeches. It is about making people feel like the work matters and they are the right ones to do it.
Read commentary →Week 1 Day 4: Self-Awareness Is Not Optional
You cannot lead people well if you do not understand yourself first. Your patterns, your triggers, your blind spots -- they are all showing, whether you see them or not.
Read commentary →Week 1 Day 5: The Leader You Think You Are vs. The Leader Your Team Sees
There are two versions of you as a leader. The one in your head is generous and reasonable. The one your team experiences may be very different.
Read commentary →Week 1 Day 6: Charisma Fades, Clarity Stays
Charismatic leaders fill rooms. Clear leaders build teams that do not need them in the room.
Read commentary →Week 1 Day 7: The First Assignment -- Write Down Who You Actually Are
Before you can lead anyone else, you need an honest document that describes how you work, what drains you, and where you need help. Write it this week.
Read commentary →Week 2 Day 1: The Six Types of Working Genius
There are six types of work. You are naturally gifted at two of them, competent at two, and frustrated by two. Knowing which is which changes everything.
Read commentary →Week 2 Day 2: Wonder Is Not Daydreaming
Wonder is the genius of pondering -- sitting with big questions before rushing to answers. It looks like staring out the window. It is actually the beginning of every breakthrough.
Read commentary →Week 2 Day 3: Galvanizing Is Not Cheerleading
Galvanizing is the genius of rallying people around an idea. It is not about being loud or positive. It is about making the mission feel urgent and personal.
Read commentary →Week 2 Day 4: When Wonder and Galvanizing Pair Together
The leader who sees what others miss and then makes everyone care about it -- that is the Wonder-Galvanizer combination. It is powerful, and it has a dangerous blind spot.
Read commentary →Week 2 Day 5: The Visionary Trap -- Seeing Everything, Finishing Nothing
Vision without execution is hallucination. If your team has heard fifteen priorities this quarter, you do not have a vision problem. You have a discipline problem.
Read commentary →Week 2 Day 6: Why Visionaries Need Operators (and Vice Versa)
The leader who sees the future and the leader who builds the present are not in conflict. They need each other. The mistake is thinking one is more important.
Read commentary →Week 2 Day 7: Assignment: Take the Working Genius Assessment
This is not optional. Take the Working Genius assessment this week. Until you know your genius and frustration areas, you are leading blind.
Read commentary →Week 3 Day 1: The 95% Delusion
Ninety-five percent of people believe they are self-aware. About ten to fifteen percent actually are. That gap is where most leadership failures live.
Read commentary →Week 3 Day 2: Internal vs External Self-Awareness
Internal self-awareness is knowing what drives you. External self-awareness is knowing how you land on other people. Most leaders have one without the other.
Read commentary →Week 3 Day 3: Your Stress Signature
Every leader has a predictable pattern of behavior under stress. Your team already knows yours. You should too.
Read commentary →Week 3 Day 4: The Feedback Vacuum
The higher you go, the less honest feedback you receive. This is not a perk -- it is a threat.
Read commentary →Week 3 Day 5: How to Actually Ask for Feedback
Saying 'my door is always open' is not a feedback strategy. It is a way to feel open while remaining unreachable.
Read commentary →Week 3 Day 6: Knowing Your Gaps vs Hiding Them
There is a difference between a leader who does not know their weaknesses and a leader who knows them but hides them. Both fail, but the second one fails faster.
Read commentary →Week 3 Day 7: Assignment: Ask Three People What It Is Like to Work With You
This week's assignment is simple and uncomfortable: ask three people who work with you a specific question and write down what they say without defending yourself.
Read commentary →Week 4 Day 1: Servant Leadership Is Not Weakness
Servant leadership is the most misunderstood concept in management. It does not mean you serve your team's every request. It means you serve their ability to do great work.
Read commentary →Week 4 Day 2: The Hero Complex -- When Helping Becomes Hurting
The leader who saves the day every time is not a hero. They are a single point of failure wearing a cape.
Read commentary →Week 4 Day 3: You Are Not Responsible for Solving Every Problem
Your team has problems. That is normal. Your job is not to solve all of them. Your job is to make sure the right people are solving the right ones.
Read commentary →Week 4 Day 4: Serving Means Removing Obstacles, Not Doing the Work
The servant leader's primary question is not 'How can I help you do your job?' It is 'What is preventing you from doing your job, and how do I remove it?'
Read commentary →Week 4 Day 5: When Servants Burn Out -- The Cost of Always Being Available
The servant leader who never says no does not serve anyone. They just burn slower than they realize.
Read commentary →Week 4 Day 6: The Difference Between a Servant Leader and a Doormat
A servant leader serves the mission through the team. A doormat serves the team's comfort at the expense of the mission. The line matters.
Read commentary →Week 4 Day 7: Assignment: Identify One Thing You Do That Your Team Should Own
This week's assignment: find one task you do regularly that someone on your team could and should own instead. Then hand it over -- properly.
Read commentary →Week 6 Day 1: Humility Is Not Uncertainty
Humility does not mean you are unsure. It means you are sure enough to hold your position while remaining open to being wrong.
Read commentary →Week 6 Day 2: You Can Be Humble and Still Make Hard Calls
The hardest calls in leadership are not the ones where the data is clear. They are the ones where reasonable people disagree, the stakes are high, and someone has to decide.
Read commentary →Week 6 Day 3: Authority Without Humility Is Tyranny; Humility Without Authority Is Abdication
Authority and humility are not enemies. They are the two legs you need to stand on. Remove either one and you fall.
Read commentary →Week 6 Day 4: The Leader Who Apologizes vs. The Leader Who Never Admits Fault
An apology from a leader is not a sign of weakness. It is proof that truth matters more to them than image.
Read commentary →Week 6 Day 5: How to Hold a Strong Position While Staying Open to Being Wrong
Strong opinions, loosely held is not a cliche. It is a discipline. Hold your position with conviction until better evidence shows up, then update without shame.
Read commentary →Week 6 Day 6: When Humility Gets Weaponized -- False Modesty and Indecision
False humility is not humility. It is a performance designed to make you look good while avoiding the responsibility of leading.
Read commentary →Week 6 Day 7: Assignment: Make One Decision You Have Been Avoiding
This week's assignment: identify one decision you have been postponing and make it. Write down your reasoning, communicate it clearly, and commit to revisiting it in 30 days.
Read commentary →Week 7 Day 1: Every Leader Has Two Frustration Areas
In the Working Genius model, every person has two areas of frustration -- work that drains them, slows them down, and quietly erodes their energy. Your job this week is to stop pretending yours do not exist.
Read commentary →Week 7 Day 2: The Genius You Lack Is Not a Flaw -- It Is Information
Your frustration areas are not deficiencies to fix. They are data points that tell you exactly what kind of help you need.
Read commentary →Week 7 Day 3: Why Leaders Pretend to Be Good at Everything
The pressure to appear complete is one of the most destructive forces in leadership. It wastes your energy, undermines your team, and fools nobody.
Read commentary →Week 7 Day 4: Your Gaps Are Showing Whether You Acknowledge Them or Not
The only difference between a leader who owns their gaps and one who does not is that the first one gets help and the second one gets worked around.
Read commentary →Week 7 Day 5: Building a Team Around Your Weaknesses, Not Your Strengths
Most leaders hire people who are good at the same things they are good at. The best leaders hire people who are great at the things they are terrible at.
Read commentary →Week 7 Day 6: The Courage to Say 'I Am Not Good at This'
Six words that will change your leadership: 'I am not good at this.' Not as self-deprecation. As strategy.
Read commentary →Week 7 Day 7: Assignment: Name Your Two Working Frustrations Out Loud to Your Team
This week's assignment: in your next team meeting, share your Working Genius frustration areas. Name them, explain what they mean practically, and ask your team what they would change if they knew those gaps were being addressed.
Read commentary →Week 8 Day 1: Frustrations Are Drains, Not Failures
A Working Genius frustration is not a skill you have not learned. It is a type of work that will always cost you more energy than it returns, no matter how proficient you become at doing it.
Read commentary →Week 8 Day 2: What Happens When You Force Yourself Into Frustration Work
The leader who spends 40% of their week in frustration areas is not being disciplined. They are running at half capacity and calling it dedication.
Read commentary →Week 8 Day 3: Your Team Feels It When You Are Drained
Energy is contagious. When you are operating in your frustration zone, your team does not just lose your best work -- they absorb your depletion.
Read commentary →Week 8 Day 4: The Meeting You Hate Is the Meeting Someone Else Was Born to Run
That recurring meeting that drains you every week? Someone on your team would love to own it. Your frustration is their genius -- and you are standing in the way.
Read commentary →Week 8 Day 5: Delegating Your Frustrations Is Not Laziness
Delegating your frustration areas is not avoiding work. It is routing work to the person who will do it best, fastest, and with the most energy.
Read commentary →Week 8 Day 6: How to Restructure Your Week Around Energy, Not Obligation
Most leaders build their calendars around obligations. The best leaders build theirs around energy -- front-loading genius work and containing frustration work to low-impact windows.
Read commentary →Week 8 Day 7: Assignment: Audit Your Calendar for Frustration Work
This week's assignment: color-code your calendar for the next five business days. Green for genius, yellow for competency, red for frustration. Then identify one red block to delegate or restructure.
Read commentary →Week 10 Day 1: You Are a Liability -- And That Is Okay
Every leader is a single point of failure for something. The ones who build great teams are not the ones who eliminate their flaws -- they are the ones who build systems around them.
Read commentary →Week 10 Day 2: The System Is the Safety Net, Not Your Willpower
Willpower is a depletable resource. Systems run whether you have energy or not. The best leaders design their teams so that the right things happen automatically.
Read commentary →Week 10 Day 3: How to Automate Accountability
The best accountability systems do not depend on someone reminding you. They make the status of every commitment visible to everyone, all the time.
Read commentary →Week 10 Day 4: Creating Guardrails for Your Worst Patterns
You know your patterns by now. The question is not whether they will show up again -- it is whether you have built guardrails that catch you when they do.
Read commentary →Week 10 Day 5: What a 'Leader-Proof' Process Looks Like
A leader-proof process is one that produces good outcomes regardless of the leader's mood, energy, or attention on any given day. It is not an insult to your leadership -- it is a testament to your design skills.
Read commentary →Week 10 Day 6: Your Team Should Be Able to Succeed Even on Your Bad Days
Your worst day should not be your team's worst day. If your bad mood, low energy, or distracted attention derails the team's work, the system is designed around your presence, not around their success.
Read commentary →Week 10 Day 7: Assignment: Design One System That Compensates for Your Biggest Gap
This week's assignment: pick your single biggest leadership gap -- the pattern that costs your team the most -- and design a system that compensates for it. Not a habit. Not a reminder. A system that runs without your involvement.
Read commentary →Week 40 Day 1: Burnout Is Not a Badge of Honor -- It Is a System Failure
Burnout does not mean you worked hard enough. It means your system -- the way you structured your work, set your boundaries, and managed your energy -- failed. Burnout is a process failure, not a character strength.
Read commentary →Week 40 Day 2: The Always-Available Leader Is the Always-Exhausted Leader
The leader who is always available teaches the team to always need them. Constant availability is not service -- it is a dependency trap that prevents the team from developing self-sufficiency and prevents the leader from recovering.
Read commentary →Week 40 Day 3: Sustainable Pace Is a Competitive Advantage, Not a Weakness
The team that maintains a sustainable pace for 50 weeks outproduces the team that sprints for 10 weeks and burns out for the other 40. Sustainability is not the absence of ambition -- it is the discipline to maintain performance over the long term.
Read commentary →Week 40 Day 4: Recovery Rituals for Leaders Who Cannot Afford to Stop
Most leaders cannot take a month off to recover from accumulated stress. They need recovery that works within the constraints of a demanding role -- rituals that restore energy without requiring large blocks of time.
Read commentary →Week 40 Day 5: Your Team Mirrors Your Energy -- Protect It
The leader's energy sets the emotional tone for the entire team. A stressed, exhausted leader produces a stressed, exhausted team -- not through explicit instruction but through the unconscious emotional contagion that permeates every interaction.
Read commentary →Week 40 Day 6: Building a Team That Thrives Without You for a Week
The ultimate test of sustainable leadership: can your team operate effectively for one full week without any contact from you? If the answer is no, you have built a team that depends on you rather than a team that depends on the systems you created.
Read commentary →Week 40 Day 7: Assignment: Design Your Personal Sustainability System
This week's assignment: design a personal sustainability system that prevents burnout rather than treating it. The system should include daily, weekly, and quarterly recovery practices.
Read commentary →Week 41 Day 1: Your Genius Gives You Energy -- Your Frustration Drains It
You already know your Working Genius profile from Week 2. Now apply it to sustainability: the work that aligns with your genius -- Wonder and Galvanizing -- gives you energy even after a long day. The work that falls in your frustration area -- Tenacity -- drains you faster than any amount of difficulty or volume.
Read commentary →Week 41 Day 2: How to Structure Your Day Around Energy, Not Just Deliverables
Most leaders organize their day around what needs to be delivered. The sustainable leader organizes their day around when they have the energy to deliver each type of work. The sequence matters as much as the content.
Read commentary →Week 41 Day 3: The Morning Is for Wonder; The Afternoon Is for Operations
A practical rule for Wonder/Galvanizer leaders: mornings are for thinking and creating, afternoons are for executing and supporting. This division is not a preference -- it is an alignment with how your brain works.
Read commentary →Week 41 Day 4: Protecting Your Genius Time Is Not Selfish
The leader who protects time for their genius work often feels guilty -- 'I should be available for my team.' But the team benefits more from a leader who does 2 hours of excellent strategic work than from a leader who is available for 10 hours of mediocre reactive work.
Read commentary →Week 41 Day 5: What to Do When Your Role Demands Your Frustration Areas
Every leadership role includes some frustration-area work. The goal is not to eliminate frustration work entirely -- it is to contain it, delegate what you can, and manage the energy drain from what remains.
Read commentary →Week 41 Day 6: The Calendar Audit -- Where Is Your Energy Going?
Your calendar is a map of your energy allocation. Most leaders have never audited it against their Working Genius profile. When they do, they discover that 50-70% of their calendar is spent on work that drains rather than energizes them.
Read commentary →Week 41 Day 7: Assignment: Redesign One Day of Your Week Around Energy Flow
This week's assignment: pick one day next week and redesign it from scratch based on your energy profile. Move genius work to peak hours. Move frustration work to low-energy hours. Protect the peak window. Measure how the redesigned day feels compared to your standard day.
Read commentary →Week 42 Day 1: Leadership Should Not Require Sacrificing Your Health or Relationships
If your leadership success requires your marriage to suffer, your health to decline, or your friendships to disappear, you have not succeeded -- you have traded one form of failure for another. Sustainable leadership means performing at a high level without destroying the rest of your life.
Read commentary →Week 42 Day 2: The Leader Who Gives Everything Has Nothing Left to Give
Generosity without boundaries is not sustainable leadership -- it is slow self-destruction. The leader who gives their time, energy, and attention to everyone and everything without limit eventually has nothing left to give to anyone, including themselves.
Read commentary →Week 42 Day 3: Boundaries Are Not Selfish -- They Are Structural
A boundary is not a refusal to help. It is a structural decision about how your limited capacity is allocated. Boundaries protect the team by ensuring their leader has the energy and clarity to lead, not just the availability to react.
Read commentary →Week 42 Day 4: How to Model Healthy Leadership for Your Team
Your team will not maintain boundaries if you do not model them. The leader who sends emails at midnight is telling the team that midnight work is expected, regardless of what the handbook says. Modeling healthy leadership is one of your most impactful leadership behaviors.
Read commentary →Week 42 Day 5: What Changes When You Stop Equating Hours with Commitment
The moment you stop measuring commitment by hours worked and start measuring it by impact delivered, everything about how you lead changes. The team member who delivers exceptional results in 40 hours is more committed than the team member who delivers mediocre results in 60.
Read commentary →Week 42 Day 6: The Long Game -- A Career Is 40 Years, Not 40 Sprints
A leadership career spans three to four decades. The leader who burns brightest in year three and flames out by year five has a shorter career than the leader who maintains steady, sustainable performance for thirty years. Pace yourself for the career, not the quarter.
Read commentary →Week 42 Day 7: Assignment: Set One Boundary This Week and Hold It
This week's assignment: choose one boundary from Day 3's list and implement it. Communicate it to your team and stakeholders. Hold it for one full week without exception.
Read commentary →Week 43 Day 1: What Is a Leadership Operating Manual and Why You Need One
A Leadership Operating Manual is a written document that tells your team how you operate -- how you think, how you communicate, how you make decisions, what stresses you, and how to push back on you. It is the user manual that most leaders never write, and that every team wishes their leader had provided.
Read commentary →Week 43 Day 2: The Document Your Team Wishes You Had Written Years Ago
Ask any experienced team member what they wish they had known about their leader on day one. The answer is always some version of: 'I wish I had known how they think, what they care about, and how to communicate with them effectively.' The Leadership Operating Manual is the answer to that wish.
Read commentary →Week 43 Day 3: Section 1: My Working Genius and My Working Frustrations
The first section of your Leadership Operating Manual tells your team where you are at your best and where you struggle. This is not weakness -- it is honesty, and honesty is the foundation of efficient collaboration.
Read commentary →Week 43 Day 4: Section 2: How I Communicate and How I Want to Be Communicated With
The second section of your Leadership Operating Manual covers communication preferences. How do you prefer to receive information? How do you deliver it? What are the norms you expect in communication with you?
Read commentary →Week 43 Day 5: Section 3: What Stresses Me and How It Shows Up
The third section of your Leadership Operating Manual discloses your stress triggers and stress behaviors. This is the section most leaders resist writing -- and the section most teams need to read.
Read commentary →Week 43 Day 6: Section 4: How to Push Back on Me
The final section of your Leadership Operating Manual gives your team explicit permission and instructions for disagreeing with you. This is the section that separates a genuine operating manual from a self-promotional document.
Read commentary →Week 43 Day 7: Assignment: Assemble Your Leadership Operating Manual
This week's assignment: assemble your complete Leadership Operating Manual. Pull together the four sections from this week along with all the exercises from the previous 42 weeks into a single document.
Read commentary →Week 44 Day 1: Writing Down How You Work Is Leadership Infrastructure
Most leaders have never written down how they actually work. They have a vague sense of their preferences and habits, but they have not articulated them with the precision needed for someone else to understand and work with them effectively. Writing it down is not navel-gazing -- it is building infrastructure for collaboration.
Read commentary →Week 44 Day 2: Default Mode vs. Best Mode
You have a default mode -- how you operate when you are not intentionally managing yourself. You also have a best mode -- how you operate when conditions are optimal and you are performing at your peak. They are not the same, and understanding the gap between them is essential to growing as a leader.
Read commentary →Week 44 Day 3: How You Make Decisions
Every leader has a decision-making style -- a default pattern for how they gather information, consider options, involve others, and commit to a direction. Understanding your style is essential because it determines how quickly and how well decisions get made on your team.
Read commentary →Week 44 Day 4: How You Handle Meetings
Your meeting style communicates your values more clearly than any mission statement. The leader who fills every meeting with their own talking communicates that their voice matters most. The leader who asks questions and listens communicates that the team's thinking matters. Understand your meeting style and design it intentionally.
Read commentary →Week 44 Day 5: How You Handle Conflict
Every leader has a default conflict response -- avoid, accommodate, compete, compromise, or collaborate. Your default serves you well in some situations and poorly in others. The goal is not to change your default but to expand your range so you can choose the appropriate response rather than defaulting to the comfortable one.
Read commentary →Week 44 Day 6: How You Give and Receive Feedback
Your feedback style shapes your team's growth trajectory more than any process, tool, or training program. The leader who gives clear, honest, specific feedback builds a team that improves rapidly. The leader who gives vague, delayed, or sugarcoated feedback builds a team that stagnates.
Read commentary →Week 44 Day 7: Assignment: Write Your 'How You Work' Document
This week's assignment: write your complete 'How You Work' document covering default mode, best mode, decision-making style, meeting style, conflict style, and feedback style. This is the companion document to your Leadership Operating Manual.
Read commentary →Week 49 Day 1: Every Leader Needs Five Stories
The most effective leaders are not the best speakers. They are the best storytellers. Not polished theatrical performers -- leaders who have five stories they can tell from personal experience that communicate who they are, what they believe, and how they lead. These stories do more work than any mission statement, company value, or leadership philosophy document.
Read commentary →Week 49 Day 2: Why Stories Persuade More Than Arguments
Arguments trigger resistance. Stories bypass it. When you present an argument -- a logical case for why the team should adopt a new process or change their behavior -- the listener's brain activates critical evaluation. They look for flaws, counter-arguments, and reasons to disagree. When you tell a story, the listener's brain activates simulation. They experience the situation alongside you. By t
Read commentary →Week 49 Day 3: Your Failure Story -- The Time You Got It Wrong
The failure story is the most important of the five because it is the hardest to tell and the most powerful when told well. A leader who can say 'here is a time I got it wrong, here is what it cost, and here is what I learned' communicates more about their character in three minutes than months of day-to-day interactions.
Read commentary →Week 49 Day 4: Your Humility Story -- The Team Member Who Taught You Something
The humility story is about a time when someone you led -- someone junior, someone with less experience, someone in a role with less organizational power -- taught you something important. This story communicates that you value learning over hierarchy, that good ideas can come from anywhere, and that leadership is not about having all the answers.
Read commentary →Week 49 Day 5: Your Team Story -- The Group That Changed Your Thinking
The team story is about a group of people who worked together in a way that shifted your understanding of what teams can achieve. Not a team that succeeded because of a star performer -- a team that succeeded because of how they functioned together. This story communicates what you value in team dynamics and what you aspire to create.
Read commentary →Week 49 Day 6: How to Tell Stories Without Making It About You
The biggest risk with leadership storytelling is making yourself the hero. The failure story becomes a humble-brag ('I failed, but learned so much that now I am amazing'). The team story becomes a credit-grab ('let me tell you about this great team that I led'). The audience detects self-serving narratives instantly, and the story loses all its power.
Read commentary →Week 49 Day 7: Assignment: Write Your First Signature Story
This week's assignment: write your first signature story. Choose one of the five types -- failure, humility, team, values, or growth -- and write it out completely. Not bullet points. Not an outline. A complete, tell-able story that you could share in a team meeting, a one-on-one, or an all-hands.
Read commentary →Week 50 Day 1: You Did Not Become a Leader by Accident
Leadership did not happen to you. A series of moments shaped your beliefs about what leadership is, what it should be, and what it should never be. Some of those moments made you better. Some of them left scars you are still working around. Until you identify and examine those moments, they control you without your awareness.
Read commentary →Week 50 Day 2: Leadership Is Different From Being Good at Your Job
The most disorienting transition in most careers is the shift from individual contributor to leader. Everything that made you successful as a contributor -- technical expertise, speed of execution, being the person with the answers -- becomes a liability when your job shifts to making other people successful. The moment you realized this was probably one of your formative leadership moments.
Read commentary →Week 50 Day 3: The Boss Who Showed You What Not to Do
Almost every leader has a formative negative leadership experience -- a boss who demonstrated exactly the leader you do not want to be. These negative moments are often more formative than positive ones because the emotional intensity of bad leadership experiences burns the lesson into memory. The question is whether you have examined that lesson consciously or whether it is running on autopilot.
Read commentary →Week 50 Day 4: The First Time You Let Someone Down as a Leader
There was a moment when you realized that your decision or your inaction caused someone on your team to suffer a consequence they did not deserve. You failed to advocate for them, or you made a promise you could not keep, or you avoided a difficult conversation until it became a crisis. That moment lives in you. It shaped how you think about the responsibility of leadership.
Read commentary →Week 50 Day 5: The Moment You Chose the Easy Path Instead of the Right One
Every leader has a moment where they knew the right thing to do and chose the easier thing instead. They avoided the difficult conversation. They went along with the political decision rather than advocating for the team. They let a performance issue slide because addressing it would be uncomfortable. These moments are the most valuable for self-examination because they reveal the specific conditi
Read commentary →Week 50 Day 6: Turning Formative Moments Into Teaching Moments
The formative moments you have examined this week are not just self-improvement material. They are teaching material. When you share these moments with your team -- as signature stories, as context in one-on-ones, as examples in team discussions -- you convert personal experience into organizational wisdom. The leader who teaches from their own examined experience produces a team that learns faste
Read commentary →Week 50 Day 7: Assignment: Write Three Moments That Shaped Your Leadership
This week's assignment: write three formative leadership moments. One positive moment (a leadership experience that taught you something you want to replicate), one negative moment (a leadership experience that taught you something you want to avoid), and one moment of personal failure (a time when your own leadership fell short).
Read commentary →Week 51 Day 1: Your Biggest Lessons Came From Your Worst Days
The days that shaped you most as a leader were not the victories. They were the days something went wrong and you had to decide who you were going to be in the wreckage. Success teaches you that your approach works. Failure teaches you why it works, when it does not work, and what to do when it stops working. That second kind of knowledge is worth more.
Read commentary →Week 51 Day 2: The Project You Should Have Killed Sooner
Every leader has at least one project they kept alive too long. The signs of failure were visible early -- the milestones kept slipping, the team's energy was declining, the original business case had eroded -- but you kept going because killing the project felt like admitting you were wrong. The cost of continuing was larger than the cost of stopping, but the cost of stopping was more visible.
Read commentary →Week 51 Day 3: The Person You Hired Who You Knew Was Wrong
There is a specific kind of hiring failure that haunts leaders: the hire you made when something in your gut said no, but you talked yourself into yes. The resume was strong. The interview was adequate. The team needed someone. And so you overrode the signal because the cost of not hiring felt larger than the risk of hiring wrong.
Read commentary →Week 51 Day 4: The Feedback You Gave Too Late
There was a conversation you needed to have with a team member -- about their performance, their behavior, their impact on the team -- and you waited too long. By the time you had the conversation, the pattern was entrenched, the damage was done, and the team member felt blindsided because the problem was 'suddenly' serious even though you had been aware of it for months.
Read commentary →Week 51 Day 5: The Time You Chose Comfort Over Courage
Last week you examined the moment you chose the easy path over the right one. This is the same territory, but the lens is different. Last week was about the decision. This week is about the pattern. If you are honest with yourself, the time you chose comfort was not an isolated incident -- it was a moment when a recurring pattern became visible enough to acknowledge.
Read commentary →Week 51 Day 6: Why Sharing Failure Stories Builds More Trust Than Success Stories
You learned in Week 49 that leaders need five signature stories. This week has given you raw material for the most powerful of those stories: the failure stories. When you share these stories with your team, you are not just being vulnerable. You are building the psychological safety infrastructure that allows the team to take risks, report errors, and learn from failures without fear.
Read commentary →Week 51 Day 7: Assignment: Tell One Failure Story to Your Team This Week
This week's assignment: take one of the failure stories you have examined this week and tell it to your team. Not in writing. Not in a carefully crafted email. In person (or on a video call), in a team meeting or a relevant one-on-one, with the specificity, ownership, and actionable lesson that makes the story a teaching tool rather than a confession.
Read commentary →Week 52 Day 1: Leadership Is Learned From People, Not Books
You have spent 52 weeks absorbing frameworks, tools, research, and practice assignments. But the most honest thing this course can tell you in its final week is this: leadership is not learned from courses. Leadership is learned from people. The frameworks gave you language. The people in your life gave you the lessons. This final week is about recognizing those people and understanding what they
Read commentary →Week 52 Day 2: The Mentor Who Saw Something in You Before You Saw It
Most leaders can point to at least one person who believed in their potential before they believed in it themselves. Someone who gave them a stretch assignment, fought for their promotion, provided feedback that shifted their trajectory, or simply said 'you can do this' at a moment when they were not sure. That person changed the course of your career not by teaching you a skill but by changing wh
Read commentary →Week 52 Day 3: The Peer Who Made You Better by Being Honest
Mentors see you from above. Direct reports see you from below. But peers see you from the side -- the angle with the least distortion and the most clarity. The peer who made you a better leader did so because they had no power dynamic to navigate. They could be honest in a way your boss could not (because your boss evaluates you) and your team could not (because you evaluate them).
Read commentary →Week 52 Day 4: The Direct Report Who Taught You More Than You Taught Them
Leadership is framed as a one-direction development flow: the leader develops the team. But the leaders who grow the most are the ones who recognize that development flows both directions. Your direct reports teach you about your blind spots, your impact, your patterns, and the gap between the leader you think you are and the leader they actually experience.
Read commentary →Week 52 Day 5: The Leader You Watched Fail and What You Learned From It
You already examined the boss who showed you what not to do (Week 50, Day 3). This is different. This is about a leader you respected -- someone whose failure was not about character but about a specific error in a specific context. They were a good leader who got something wrong, and watching them navigate that failure taught you more than watching their successes ever did.
Read commentary →Week 52 Day 6: Great Leaders Are Built by the People Around Them
The myth of leadership is that great leaders are self-made. They had a vision, they developed their skills, they built their teams, and they succeeded through personal excellence. The reality is that every great leader was built by the people around them -- the mentors who invested in them, the peers who challenged them, the direct reports who taught them, and the leaders they observed (both succe
Read commentary →Week 52 Day 7: Assignment: Thank One Person Who Shaped Your Leadership
This is the final assignment of the course. It is the simplest and possibly the most important. Choose one person -- a mentor, a peer, a direct report, a leader you observed -- who significantly shaped how you lead. Contact them and tell them specifically what they taught you and how it changed your leadership. Do not send a generic thank-you. Send a specific acknowledgment of their impact.
Read commentary →Get Self-Awareness Daily
Receive one 52-week leadership course entry each morning with commentary. Free, no spam, unsubscribe anytime.
Start Free Daily Email