Trust
Building and maintaining trust as the foundation of leadership
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....
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....
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....
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....
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....
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....
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....
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....
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....
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....
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....
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....
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....
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....
Week 12 Day 1: Teaching Your Team to Think Like Owners
The best teams do not just execute -- they think like owners. That shift does not happen by accident. It happens when leaders share the context that owners have....
Week 12 Day 2: Revenue vs. Profit -- The Distinction That Changes Behavior
Revenue is vanity. Profit is sanity. Most teams celebrate the wrong number because nobody taught them the difference....
Week 12 Day 3: How to Explain Margin Without a Finance Degree
Margin is not a finance concept -- it is a decision-making tool. And it is simpler than most leaders make it....
Week 12 Day 4: The Power of Showing Your Team the Real Numbers
Sanitized numbers create sanitized thinking. Real numbers create real accountability....
Week 12 Day 5: When Transparency Feels Risky -- What to Share and What Not To
Full transparency is not the goal. Strategic transparency is. Know the difference before you open the books....
Week 12 Day 6: Teams That Understand the Math Make Better Decisions
The evidence is clear -- teams with business context outperform teams without it. This is not opinion. It is measurement....
Week 12 Day 7: Assignment: Share One Business Metric Your Team Has Never Seen
This week's assignment is simple but uncomfortable -- pick one business metric your team has never been shown and share it with them....
Week 14 Day 1: Information Hoarding Is Not Protection -- It Is Control
Leaders who withhold business information from their teams call it protection. Their teams call it something else....
Week 14 Day 2: What Your Team Assumes When You Do Not Share
In the absence of information, people do not assume nothing. They assume the worst....
Week 14 Day 3: The Trust Tax of Secrecy
Every piece of information you withhold has a compounding cost. It is not a one-time decision -- it is a tax on every future interaction....
Week 14 Day 4: How to Share Bad News Without Creating Panic
Bad news does not create panic. Uncontextualized bad news does. The difference is framing, not filtering....
Week 14 Day 5: Financial Transparency as a Retention Tool
The best retention strategy is not perks or promotions -- it is making your team feel like insiders rather than employees....
Week 14 Day 6: The Leader Who Shares vs. The Leader Who Shields
Shielding your team from business reality feels protective. It is actually a vote of no confidence in their ability to handle the truth....
Week 14 Day 7: Assignment: Hold an Open-Books Meeting With Your Team
This week's assignment is the most uncomfortable one yet -- hold an open-books meeting where you share real financial information with your team....
Week 15 Day 1: Trust Is Not a Feeling -- It Is a Measurement
Most leaders think trust is something you feel. It is not. Trust is something you measure -- and most teams have never measured it....
Week 15 Day 2: What a Trust Audit Actually Looks Like
A Trust Audit is not a survey. It is a structured conversation with each team member that reveals the specific dimensions of trust that need work....
Week 15 Day 3: The Five Questions That Reveal Team Health
Five questions, asked consistently, will tell you more about your team's health than any annual survey, any engagement score, or any HR dashboard....
Week 15 Day 4: Psychological Safety Is Not Comfort -- It Is Candor
Psychological safety is the most misunderstood concept in modern management. It does not mean everyone feels comfortable. It means everyone can be honest....
Week 15 Day 5: Why High-Performing Teams Fight More, Not Less
If your team never argues, that is not harmony -- it is suppression. The best teams fight about ideas because they care enough to get it right....
Week 15 Day 6: The Meeting Everyone Dreads Is the Meeting You Need Most
The meeting your team avoids is the meeting that would fix your biggest problem. Dread is a signal, not a reason to cancel....
Week 15 Day 7: Assignment: Run Your First Trust Audit
This week's assignment brings together everything from this section -- schedule and run a Trust Audit with every member of your team....
Week 16 Day 1: Your Team Is Filtering What They Tell You
Every piece of information that travels from your team to you passes through a filter. The filter is shaped by fear, politics, and self-preservation -- and you built it....
Week 16 Day 2: The Hierarchy Filter -- Why Bad News Stops at Middle Management
Bad news does not just slow down on the way to leadership -- it stops entirely at the middle management layer, where the incentives to filter are strongest....
Week 16 Day 3: How to Ask Questions That Bypass the Filter
The quality of the information you receive depends entirely on the questions you ask. Vague questions get filtered answers. Specific questions get real ones....
Week 16 Day 4: Creating Rituals for Honest Feedback
Honest feedback does not happen because you ask for it once. It happens because you build rituals that make it expected, normal, and safe....
Week 16 Day 5: What to Do When the Truth Is Ugly
You asked for the truth. You got it. Now what you do next determines whether you ever get it again....
Week 16 Day 6: The Leader's Response to Honesty Determines Whether They Get It Again
Your team is running a continuous experiment: 'What happens when I tell the leader the truth?' Your response is the result....
Week 16 Day 7: Assignment: Ask 'What Am I Not Seeing?' in Your Next One-on-One
This week's assignment is deceptively simple -- ask every team member one question in their next one-on-one: 'What am I not seeing?'...
Week 23 Day 1: 'Culture Fit' Is Often Code for 'Thinks Like Us'
When a hiring panel says a candidate is 'not a culture fit,' they usually mean the candidate is different from the people already on the team. That is not a reason to reject someone -- it is a reason ...
Week 23 Day 2: What You Actually Want Is Culture Add
Culture add asks: 'What does this person bring that we do not already have?' The answer is what makes teams smarter, more resilient, and harder to disrupt....
Week 23 Day 3: Diversity of Thought Requires Diversity of People
You cannot get diverse thinking from homogeneous teams. The backgrounds, experiences, and identities of your team members determine the range of solutions they can imagine....
Week 23 Day 4: How to Interview for Different Perspectives
Interviewing for culture add requires asking different questions than interviewing for culture fit. You are looking for complementarity, not similarity....
Week 23 Day 5: The Team That Agrees on Everything Is a Team That Misses Everything
If your team never disagrees, you do not have alignment. You have conformity. And conformity is the enemy of every form of excellence....
Week 23 Day 6: When Culture Add Feels Uncomfortable -- That Is the Point
The person who challenges your thinking will make you uncomfortable. The person who confirms your thinking will make you feel good. The first one makes your team better. The second one makes it more f...
Week 23 Day 7: Assignment: Review Your Last Three Hires for Pattern Bias
This week's assignment holds a mirror up to your hiring history -- examine your last three hires to identify whether you have been hiring for similarity rather than complementarity....
Week 27 Day 1: The Most Dangerous Phrase in Leadership
Six words that destroy trust, silence questions, and guarantee failure: 'All you gotta do is...' It is the phrase leaders use when they have forgotten what it feels like to not know....
Week 27 Day 2: When Leaders Minimize Complexity, Teams Lose Trust
Every time you describe hard work as easy, your team learns something about you: you either do not understand the work or you do not respect the people doing it. Both conclusions damage trust....
Week 27 Day 3: 'All You Gotta Do' Assumes Your Mental Model Is Shared
The phrase assumes that the picture in your head -- the full context, the connections, the nuances -- exists in the other person's head. It never does....
Week 27 Day 4: The Expert's Curse -- You Forgot How Hard This Was to Learn
The reason you think it is simple is because you already know how to do it. Expertise compresses difficulty into intuition, making the expert unable to remember what it felt like to not understand....
Week 27 Day 5: How to Describe Work Honestly Without Demoralizing
There is a space between minimizing difficulty and catastrophizing it. That space is called honesty, and it is where trust lives....
Week 27 Day 6: Respecting the Difficulty Is Respecting the Person
When you acknowledge that work is hard, you are not lowering the bar. You are honoring the effort of the person who will clear it....
Week 27 Day 7: Assignment: Catch Yourself Saying It This Week
This week's assignment is a real-time self-awareness exercise -- catch yourself every time you minimize the difficulty of work you are handing to someone else....
Week 32 Day 1: The Line Between Coaching and Controlling Is Thinner Than You Think
Coaching and micromanaging both involve a leader paying close attention to how someone does their work. The difference is intent: coaching develops the person, micromanaging protects the leader's anxi...
Week 32 Day 2: Coaching Asks Questions; Micromanaging Gives Answers
The single clearest behavioral indicator is the ratio of questions to statements. Coaches ask. Micromanagers tell....
Week 32 Day 3: How to Coach Someone Through a Problem Without Solving It
The hardest skill in coaching is restraint -- holding back the answer you already know so the other person can discover it themselves....
Week 32 Day 4: When Coaching Feels Slow but Micromanaging Feels Productive
Micromanaging produces faster short-term results but slower long-term progress. Coaching produces slower short-term results but exponentially faster long-term progress. The leader's time horizon deter...
Week 32 Day 5: The Long Game -- Teams That Are Coached Outgrow Teams That Are Managed
A managed team can only perform at the level of its manager's bandwidth. A coached team performs at the collective level of every person on it, which grows with each coaching interaction....
Week 32 Day 6: How to Tell If You Have Crossed the Line
The most reliable indicator that you have crossed from coaching to micromanaging is not your behavior -- it is the team's behavior. If the team has stopped making independent decisions, you have cross...
Week 32 Day 7: Assignment: In Your Next One-on-One, Ask Only Questions
This week's assignment is a behavioral experiment: in your next one-on-one meeting, ask only questions. No answers, no instructions, no opinions. Questions only....
Week 35 Day 1: A Process Is a Promise -- It Tells the Team What to Expect
Every process is an implicit promise: 'This is how things work here. You can depend on it.' When the process is reliable, trust grows. When the process is inconsistent or ignored, trust erodes....
Week 35 Day 2: Good Process Liberates; Bad Process Imprisons
The reason people hate process is not that process is inherently bad -- it is that they have experienced bad process. Good process removes friction and frees people to focus on their work. Bad process...
Week 35 Day 3: The Minimum Viable Process -- Start Light and Add Weight Only When Needed
The biggest mistake in process design is starting too heavy. Begin with the lightest process that prevents the most common failure mode. Add complexity only when the light version fails in a specific,...
Week 35 Day 4: How Repeatable Processes Scale Trust Across the Organization
Trust does not scale through relationships alone. At some point, the organization grows beyond the number of people any individual can know personally. At that point, trust must be embedded in process...
Week 35 Day 5: The Playbook Model -- Documenting How Your Team Works
A team playbook is a living document that captures how the team operates: how decisions are made, how work is prioritized, how communication flows, and how problems are handled. It is the codification...
Week 35 Day 6: When to Break Your Own Process
Good process includes a defined mechanism for overriding the process when circumstances demand it. A process without an override mechanism becomes a cage; a process with an override mechanism becomes ...
Week 35 Day 7: Assignment: Design One Repeatable Process for Your Team's Most Common Handoff
This week's assignment: identify your team's most common handoff (the point where work passes from one person or team to another) and design a repeatable process for it....
Week 45 Day 1: Giving Your Team Permission to Disagree
Permission to disagree is not granted by saying 'my door is always open.' It is granted by demonstrating, repeatedly, that disagreement produces better outcomes and zero punishment. The difference bet...
Week 45 Day 2: How to Tell Your Boss They Are Wrong
Your team needs to know how to tell you that you are wrong. Not how to hint at it, dance around it, or wait for you to figure it out -- how to actually say the words in a way that you can hear. This i...
Week 45 Day 3: Building a Constructive Pushback Framework for Your Team
Ad hoc pushback is inconsistent and stressful. A pushback framework gives the team a structured, repeatable process for raising concerns, challenging decisions, and proposing alternatives. The framewo...
Week 45 Day 4: What Healthy Pushback Looks Like in Practice
Healthy pushback improves decisions without damaging relationships. It is specific, timely, solution-oriented, and delivered with the assumption that the leader has good intentions. It is also receive...
Week 45 Day 5: How Punishing Pushback Destroys Trust
A single punished pushback event can undo months of trust-building. The leader who encourages disagreement and then retaliates -- even subtly -- teaches the team that disagreement is a trap. Recovery ...
Week 45 Day 6: How to React When Someone Challenges You -- A Script
Knowing how to respond to pushback is a skill, not a personality trait. Like any skill, it can be practiced and refined. Here is a script for responding to disagreement that maintains your authority w...
Week 45 Day 7: Assignment: Establish Your Team's Pushback Protocol
This week's assignment: create a written pushback protocol for your team. Share it in your next team meeting. Then create one opportunity for pushback and demonstrate the response script in real time....
Week 46 Day 1: Trust Is Measurable If You Ask the Right Questions
Most leaders treat trust as a feeling -- something they sense but cannot quantify. Trust is not a feeling. It is a set of observable behaviors, and observable behaviors can be measured. The Trust Audi...
Week 46 Day 2: The Six Trust Audit Questions
Here are the six questions that form the Trust Audit. Each question measures a specific dimension of team trust. Together, they give you a complete diagnostic of where trust is strong and where it nee...
Week 46 Day 3: Do You Feel Safe Bringing Me Bad News?
This is the most important question in the Trust Audit. If the answer is no, you are leading blind. The team is filtering what they tell you, showing you the version of reality that will not trigger a...
Week 46 Day 4: Do You Understand Why Your Work Matters?
If your team cannot articulate why their work matters -- not what they do, but why it matters -- you have a meaning deficit. Meaning deficits produce technically competent work that misses the point, ...
Week 46 Day 5: Do You Feel Like I Have Your Back?
Having your team's back means absorbing pressure from above so the team can focus on the work. It means defending the team's decisions to stakeholders. It means taking responsibility for team failures...
Week 46 Day 6: How to Use Trust Audit Results Without Getting Defensive
The Trust Audit will produce uncomfortable data. Some team members will report that they do not feel safe, do not understand why their work matters, or do not believe you follow through on commitments...
Week 46 Day 7: Assignment: Run a Full Trust Audit With Your Team
This week's assignment: run a complete Trust Audit using the six questions. Collect anonymous responses, analyze the results, identify your highest-priority repair area, and share the results and your...
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 co...
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 c...
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, a...
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 ...
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 s...
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 cre...
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. ...
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 ...
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...
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 adequat...
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, th...
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. I...
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 you...
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 tea...
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 co...
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 fe...
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...
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...
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 speci...
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 ...
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 shape...