Communication
Clear messaging, active listening, and difficult conversations
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 11 Day 1: Most Teams Do Not Know How the Business Makes Money
Your team ships code, closes tickets, and hits deadlines -- but ask them how the business actually makes money and most will guess wrong.
Read commentary →Week 11 Day 2: The Value Pyramid -- Revenue, Margin, Overhead
Every business runs on three layers: revenue at the top, margin in the middle, and overhead at the base. Most teams only see the overhead.
Read commentary →Week 11 Day 3: Why Business Literacy Is a Leadership Responsibility
If your team does not understand the business model, that is not their failure -- it is yours.
Read commentary →Week 11 Day 4: Your Team Cannot Prioritize What They Do Not Understand
Every prioritization failure on your team is an information failure. They are not bad at prioritizing -- they are missing the data.
Read commentary →Week 11 Day 5: The Difference Between Busy Work and Value Work
Busy work feels productive. Value work is productive. Your team cannot tell the difference without the Value Pyramid.
Read commentary →Week 11 Day 6: What Happens When Only the Leader Understands the Numbers
A team that depends on one person for business context is a team that cannot function when that person is unavailable.
Read commentary →Week 11 Day 7: Assignment: Draw Your Team's Value Pyramid
This week's assignment is concrete and visual -- draw the Value Pyramid for your business and share it with your team.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →Week 12 Day 4: The Power of Showing Your Team the Real Numbers
Sanitized numbers create sanitized thinking. Real numbers create real accountability.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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?'
Read commentary →Week 17 Day 1: Engagement Surveys Miss Everything That Matters
Your company runs an engagement survey once a year. It tells you nothing useful. The real data lives in the questions you ask weekly.
Read commentary →Week 17 Day 2: The Questions You Should Be Asking Weekly
Five questions, asked consistently in every one-on-one, will give you a clearer picture of team health than any dashboard, survey, or metric.
Read commentary →Week 17 Day 3: 'Do You Know What Is Expected of You?' -- The Most Underrated Question
The most powerful question in management is also the simplest: 'Do you know what is expected of you?' Most teams fail not from lack of talent but from lack of clarity.
Read commentary →Week 17 Day 4: 'Do You Have What You Need to Do Your Job?'
The second most powerful question asks whether your team has the tools, information, and authority to do what you asked them to do. Most of the time, they do not.
Read commentary →Week 17 Day 5: 'When Was the Last Time You Felt Recognized?'
Recognition is not a nice-to-have. It is a performance lever. And most leaders are running a severe deficit.
Read commentary →Week 17 Day 6: 'Is There Anything You Are Afraid to Tell Me?'
This is the question that separates good managers from transformative ones. Most will never ask it. The few who do will learn things that change how they lead.
Read commentary →Week 17 Day 7: Assignment: Pick Three Questions and Use Them This Week
This week's assignment is practical and immediate -- choose three of the five weekly questions and use them in every one-on-one this week.
Read commentary →Week 18 Day 1: The Military Concept That Changes How You Give Direction
Commander's Intent is a military communication framework that separates the desired outcome from the plan to achieve it. It is the most powerful delegation tool most leaders never learn.
Read commentary →Week 18 Day 2: Commander's Intent -- The What and Why, Not the How
Commander's Intent has exactly two components: what needs to happen and why it matters. The 'how' is deliberately left to the person doing the work.
Read commentary →Week 18 Day 3: Why Micromanagement Is a Clarity Failure
Micromanagement is not a trust problem. It is a clarity problem. Leaders micromanage when they have not communicated intent clearly enough to let go.
Read commentary →Week 18 Day 4: The Two-Sentence Test -- Can You State the Mission That Simply?
If you cannot state your team's mission in two sentences, you do not understand it well enough. And if you do not understand it, your team certainly does not.
Read commentary →Week 18 Day 5: What Happens When Plans Fall Apart but Intent Is Clear
Plans will always break. The question is whether your team freezes and waits for new orders or adapts and keeps moving. The answer depends entirely on whether they know the intent.
Read commentary →Week 18 Day 6: How Commander's Intent Empowers Decision-Making at Every Level
Commander's Intent does not just help your direct reports. It cascades. When your team knows the intent, they can communicate it to their teams, who can communicate it to theirs.
Read commentary →Week 18 Day 7: Assignment: Write Commander's Intent for Your Current Top Priority
This week's assignment turns theory into practice -- write Commander's Intent for your team's single most important current priority.
Read commentary →Week 19 Day 1: Tell Them Where to Go, Not How to Get There
The best leaders describe the destination with vivid clarity and then step back from the route. The worst leaders describe the route in excruciating detail and forget to mention where it goes.
Read commentary →Week 19 Day 2: The Leader Who Over-Specifies Kills Innovation
Every unnecessary instruction you give removes one degree of freedom from your team. Remove enough degrees of freedom and you have an assembly line, not a team.
Read commentary →Week 19 Day 3: 'How' Is Your Team's Job -- Stop Doing It for Them
You hired experts. Let them be experts. The 'how' belongs to the people closest to the work, not the person furthest from it.
Read commentary →Week 19 Day 4: When You Must Specify the How (and When You Must Not)
There are legitimate times when the leader must specify the how. The danger is that most leaders cannot tell the difference between those times and the times they should let go.
Read commentary →Week 19 Day 5: The Freedom Gradient -- Tight Intent, Loose Execution
The best delegation model is not binary -- tight control or complete freedom. It is a gradient: the tighter the intent, the looser the execution can be.
Read commentary →Week 19 Day 6: Your Best People Will Leave If You Keep Dictating Methods
Talented people do not leave companies. They leave leaders who will not let them use their talent.
Read commentary →Week 19 Day 7: Assignment: Rewrite One Directive as Intent-Only
This week's assignment crystallizes everything from Weeks 18 and 19 -- take one active directive and rewrite it as pure intent, stripping away every instruction about how.
Read commentary →Week 20 Day 1: Your Team Cannot Absorb a New Vision Every Quarter
The fastest way to make a team stop listening to your vision is to change it every quarter. Vision fatigue is not about the quality of the vision -- it is about the frequency of revision.
Read commentary →Week 20 Day 2: The Cost of Constantly Changing Direction
Every strategic pivot has a hidden cost: the trust and momentum that were invested in the previous direction. That cost compounds, and leaders rarely account for it.
Read commentary →Week 20 Day 3: Vision Fatigue Is Real -- And You Are Probably Causing It
Vision fatigue does not come from bad visions. It comes from too many good ones. The leader who has a new great idea every month is more dangerous than the leader who has no ideas at all.
Read commentary →Week 20 Day 4: How to Repeat the Same Vision Without Sounding Repetitive
The leader's job is not to create a new vision. It is to communicate the same vision so consistently that the team can recite it from memory -- and then keep communicating it.
Read commentary →Week 20 Day 5: The Discipline of Strategic Patience
Strategic patience is the discipline of staying the course long enough for a strategy to work -- even when the early results are ambiguous and new opportunities look more exciting.
Read commentary →Week 20 Day 6: When to Update the Vision vs. When to Stay the Course
Strategic patience does not mean strategic rigidity. The skill is knowing the difference between noise -- temporary signals that do not warrant a response -- and signal -- genuine evidence that the direction must change.
Read commentary →Week 20 Day 7: Assignment: State Your Team's Mission -- Then Ask Three People to State It Back
This week's assignment measures the gap between what you think you have communicated and what your team has actually absorbed.
Read commentary →Week 21 Day 1: Your Team's Brain Has a Bandwidth Limit
Your team can hold about three priorities in active memory at any time. You are giving them twelve. The result is not multitasking -- it is cognitive gridlock.
Read commentary →Week 21 Day 2: Horizon 1 -- What We Are Doing Now
Horizon 1 is the current sprint, the active project, the work in progress. It is what the team should be thinking about today, this week, this month.
Read commentary →Week 21 Day 3: Horizon 2 -- What We Are Building Next
Horizon 2 is the pipeline -- the work that is being designed, scoped, and prepared so that when Horizon 1 work completes, the next thing is ready to start without delay.
Read commentary →Week 21 Day 4: Horizon 3 -- What We Are Dreaming About
Horizon 3 is the future -- the ideas, possibilities, and strategic bets that live beyond the three-month window. It is where leaders should spend their creative energy and where teams should spend almost none.
Read commentary →Week 21 Day 5: Why Leaders Live in Horizon 3 While Teams Need Horizon 1
The fundamental tension of leadership is that your mind naturally gravitates to Horizon 3 while your team needs you firmly anchored in Horizon 1.
Read commentary →Week 21 Day 6: How to Communicate Across All Three Without Overwhelming
The Three Horizons model works only if the leader communicates all three horizons simultaneously without the team confusing them. This requires discipline, structure, and repetition.
Read commentary →Week 21 Day 7: Assignment: Label Your Current Initiatives by Horizon
This week's assignment brings the Three Horizons model from theory to practice -- categorize every active initiative into Horizon 1, 2, or 3.
Read commentary →Week 26 Day 1: More Work Fails in the Handoff Than in the Execution
The most dangerous moment in any project is not the hardest technical challenge -- it is the moment responsibility transfers from one person to another.
Read commentary →Week 26 Day 2: Why 'All You Gotta Do Is...' Breaks Teams
The five most destructive words in leadership are 'all you gotta do is.' They minimize the work, insult the person, and guarantee a broken handoff.
Read commentary →Week 26 Day 3: The Gap Between What You Said and What They Heard
Every handoff contains two messages: the one you sent and the one they received. They are never the same message, and the gap between them is where failures live.
Read commentary →Week 26 Day 4: Hand-Offs Fail When Context Is Assumed
The most common handoff failure is not missing information -- it is assumed context. The sender knows why the work matters, what has been tried before, and what constraints exist. The receiver knows none of it.
Read commentary →Week 26 Day 5: The Five Things Every Handoff Needs
Every clean handoff transfers five things: what needs to happen, why it matters, what has been tried, what constraints exist, and how the receiver should signal if they are stuck.
Read commentary →Week 26 Day 6: What a Clean Handoff Looks Like in Practice
A clean handoff feels unremarkable. Nobody notices it because nothing went wrong. That invisibility is what makes it hard to prioritize -- and what makes it one of the highest-leverage leadership skills you can develop.
Read commentary →Week 26 Day 7: Assignment: Audit One Recent Handoff That Went Wrong
This week's assignment turns your most recent handoff failure into a diagnostic tool -- trace the failure backward to the specific information gap and design the fix.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →Week 28 Day 1: Most Teams Argue About Completion Because They Never Defined It
The most common source of team conflict is not disagreement about how to do the work -- it is disagreement about when the work is finished.
Read commentary →Week 28 Day 2: 'Done' Is Not a Feeling -- It Is a Checklist
When done is a feeling, it means whatever the most senior person in the room decides it means. When done is a checklist, it means the same thing every time, regardless of who is in the room.
Read commentary →Week 28 Day 3: What Happens When Done Is Ambiguous
Ambiguous completion criteria create three predictable problems: rework cycles that nobody budgeted for, trust erosion between the person doing the work and the person reviewing it, and scope creep disguised as quality standards.
Read commentary →Week 28 Day 4: How to Write a Definition of Done That Actually Works
An effective Definition of Done is specific enough to be unambiguous, short enough to be remembered, and flexible enough to apply across different types of work.
Read commentary →Week 28 Day 5: The Definition of Done Prevents Rework, Not Creativity
A Definition of Done is not a constraint on how you do the work. It is a contract about when the work is finished. Inside those boundaries, the team has complete creative freedom.
Read commentary →Week 28 Day 6: When 'Good Enough' Is the Right Definition of Done
Perfectionism disguised as quality standards is one of the most expensive leadership failures. Sometimes 'good enough' is not settling -- it is the right standard for the situation.
Read commentary →Week 28 Day 7: Assignment: Write a Definition of Done for Your Team's Most Common Deliverable
This week's assignment creates a concrete Definition of Done that your team can start using immediately -- turning the concepts from this week into an operational tool.
Read commentary →Week 29 Day 1: Delegation Is Not Dumping -- It Is a Transfer of Ownership
When you delegate poorly, you do not transfer ownership. You transfer confusion. The recipient does not own the outcome -- they own the mess.
Read commentary →Week 29 Day 2: The Context Transfer Problem: What You Know but Did Not Say
The most important information in a delegation is the information you forgot to transfer because you did not realize you had it.
Read commentary →Week 29 Day 3: Three Levels of Delegation and When to Use Each
Not all delegation is the same. The level of delegation should match the recipient's experience, the risk of the task, and the trust you have built with the person.
Read commentary →Week 29 Day 4: The Check-In Cadence: How to Monitor Without Micromanaging
The difference between monitoring and micromanaging is not the frequency of check-ins -- it is the content. Micromanagers ask 'what are you doing?' Good delegators ask 'what do you need?'
Read commentary →Week 29 Day 5: Transferring the Why, Not Just the What
When you delegate the what without the why, you create an executor. When you delegate both the what and the why, you create an owner.
Read commentary →Week 29 Day 6: What to Do When Delegated Work Comes Back Wrong
When delegated work comes back wrong, the first question to ask is not 'what did they do wrong?' It is 'what did I fail to communicate?'
Read commentary →Week 29 Day 7: Assignment: Redesign Your Next Delegation Using the Full Framework
This week's assignment takes a real upcoming delegation and applies every principle from this week -- transforming it from a task handoff into a true ownership transfer.
Read commentary →Week 37 Day 1: Revenue Minus Cost Equals Your Team's Reason to Exist
Every team exists to create more value than it consumes. If you cannot articulate how your team's work translates to revenue, cost savings, or risk reduction, the team's existence is vulnerable -- and your team knows it even if you do not say it.
Read commentary →Week 37 Day 2: How to Translate Business Outcomes Into Team Metrics
Business outcomes are measured in dollars, customers, and market share. Team metrics are measured in cycle time, quality, and throughput. The translation between the two is where most measurement systems fail.
Read commentary →Week 37 Day 3: The Metrics That Matter vs. the Metrics That Are Easy to Track
Organizations measure what is easy to count, not what is important to know. Lines of code, story points completed, and tickets closed are easy to track. Customer impact, code quality, and decision speed are hard to track. The easy metrics dominate because they are easy, not because they matter.
Read commentary →Week 37 Day 4: Why Vanity Metrics Destroy Focus
Vanity metrics are numbers that look impressive in a report but do not indicate whether the team is actually improving. They give the appearance of progress while hiding the absence of impact.
Read commentary →Week 37 Day 5: Connecting Individual Work to Team-Level Impact
Every person on the team should be able to trace their daily work to the team's outcome metrics. If a team member cannot explain how their work this week contributes to the team's mission, the connection has been lost.
Read commentary →Week 37 Day 6: Your Team Should Be Able to Explain Their Business Value in Two Sentences
The ultimate test of business alignment: can every person on your team explain what the team does and why it matters to the business in two sentences or fewer? If not, the connection between work and value is unclear.
Read commentary →Week 37 Day 7: Assignment: Write Your Team's Profit Equation
This week's assignment: construct the profit equation for your team. Quantify the value your team creates, the cost your team consumes, and the ratio between the two.
Read commentary →Week 38 Day 1: Strategy Means Nothing Until It Changes What People Do on Monday
A strategy that lives in a slide deck but does not change how anyone spends their time on Monday morning is not a strategy. It is a wish. Strategy becomes real only when it changes behavior.
Read commentary →Week 38 Day 2: How to Turn a Company Goal Into a Team Habit
Goals produce intention. Habits produce results. The leader's job is to translate the company's goals into the team's daily habits -- the specific, recurring behaviors that make the goal inevitable.
Read commentary →Week 38 Day 3: The Behavior Bridge -- From Big Picture to Daily Action
Between 'the company's strategic vision' and 'what I do today' lies a bridge that most organizations fail to build. That bridge is a sequence of translations: vision to priorities, priorities to objectives, objectives to behaviors, behaviors to daily actions.
Read commentary →Week 38 Day 4: Why OKRs Fail When Behaviors Are Not Defined
OKRs (Objectives and Key Results) are the most popular goal-setting framework in technology companies and one of the most commonly failed. The failure is almost never in the OKRs themselves -- it is in the missing translation from OKRs to team behaviors.
Read commentary →Week 38 Day 5: Making the Link Between 'Our Revenue Target' and 'How I Spend My Day'
The most powerful motivational tool a leader has is the ability to connect each person's daily work to the organization's most important outcome. When a person understands that their Tuesday afternoon task contributes to a $10 million revenue target, the task acquires meaning it did not have before.
Read commentary →Week 38 Day 6: What Good Translation Looks Like in Practice
Good strategy translation is specific, measurable, time-bound, and directly connected to both the strategic intent above and the daily work below. Here is what it looks like when the entire chain -- from company vision to individual task -- is working.
Read commentary →Week 38 Day 7: Assignment: Take One Company Goal and Define Three Team Behaviors
This week's assignment: pick one of your company's current strategic goals and translate it into three specific, recurring team behaviors that will move your team toward that goal.
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 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 between verbal permission and demonstrated permission is the difference between a policy and a culture.
Read commentary →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 is a skill you need to teach, not a behavior you can simply expect.
Read commentary →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 framework makes pushback normal rather than exceptional.
Read commentary →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 received with the assumption that the team member has good intentions. Both sides of the exchange matter.
Read commentary →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 from a punished pushback event takes 5-10 times longer than building the trust took in the first place.
Read commentary →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 while genuinely engaging with the challenge.
Read commentary →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.
Read commentary →Week 47 Day 1: Two Tools That Eliminate 80% of Miscommunication
Most miscommunication between a leader and their team falls into two categories: the team did not understand what done looked like, or the team did not understand why the work mattered. The Definition of Done eliminates the first. Commander's Intent eliminates the second. Together, they handle the vast majority of alignment failures.
Read commentary →Week 47 Day 2: The Definition of Done Template -- Fill In the Blanks
Here is the Definition of Done template. It has six fields. Fill in all six for every project that matters, and you will eliminate the ambiguity that produces rework, misalignment, and wasted effort.
Read commentary →Week 47 Day 3: Commander's Intent Template -- Purpose, Key Tasks, End State
The Commander's Intent template has three fields: Purpose (why we are doing this), Key Tasks (what must happen), and End State (what success looks like when we are done). These three fields give the team everything they need to make good decisions when they encounter situations you did not anticipate.
Read commentary →Week 47 Day 4: How to Introduce These Tools Without Sounding Like a Process Nerd
The fastest way to kill a useful tool is to introduce it as a process requirement. The team hears 'new process' and thinks 'more overhead.' Instead, introduce these tools as solutions to problems the team already experiences. The tool is the answer to a pain they already feel.
Read commentary →Week 47 Day 5: When Templates Fail -- The Spirit Matters More Than the Format
Templates fail when they become compliance exercises instead of thinking exercises. The team fills in the fields because they are required, not because they are thinking through the answers. When this happens, you have a completed form and no actual clarity. The spirit of the tool matters more than the format.
Read commentary →Week 47 Day 6: Adapting the Templates to Your Team's Culture
The templates are starting points, not sacred documents. Every team operates differently, and the most effective version of these tools is the version your team has adapted to fit their workflow, their communication style, and their project types.
Read commentary →Week 47 Day 7: Assignment: Use Both Templates on a Live Project This Week
This week's assignment: take a real project that your team is about to start (or one that recently started without clear alignment) and apply both templates. Fill in the Commander's Intent and the Definition of Done. Share them with the team and use them as the reference for the project.
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 →Get Communication Daily
Receive one 52-week leadership course entry each morning with commentary. Free, no spam, unsubscribe anytime.
Start Free Daily Email