Frameworks
Mental models and structured approaches to leadership decisions
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....
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....
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....
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....
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....
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....
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....
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 13 Day 1: The 'Why Does This Matter?' Question
Every task on your backlog should be able to answer one question in a single sentence: 'Why does this matter to the business?' If it cannot, it should not be there....
Week 13 Day 2: Every Task Either Creates Value or Protects Value
There are only two valid reasons for any task to exist: it creates new value for customers, or it protects existing value from degradation. Everything else is waste....
Week 13 Day 3: How to Map a Sprint to Business Outcomes
A sprint that cannot be described in business outcome terms is a sprint the business cannot evaluate. And a sprint the business cannot evaluate is a sprint that will eventually be questioned....
Week 13 Day 4: When Your Team's Work Is Three Steps Removed From Revenue
Not every team builds customer-facing features. Some teams are three steps removed from revenue -- and they need a different value narrative....
Week 13 Day 5: Making the Connection Visible Without Oversimplifying
The gap between 'everything connects to value' and 'here is exactly how' is where most leaders fail. Precision matters more than enthusiasm....
Week 13 Day 6: The Danger of Only Valuing What You Can Measure
Not everything that counts can be counted. If you only value measurable work, you will systematically underinvest in the work that matters most long-term....
Week 13 Day 7: Assignment: Build Your Leadership Operating Manual (Draft 1)
This is the assignment that Week 1 promised -- your first draft of a Leadership Operating Manual. A written document that tells your team how you work, what you value, and what to expect from you....
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 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....
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....
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....
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....
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....
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....
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....
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....
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....
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....
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 alm...
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....
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....
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....
Week 22 Day 1: Most Interviews Measure Confidence, Not Competence
The standard technical interview is a confidence test disguised as a competence test. The most articulate candidate wins, not the most capable one....
Week 22 Day 2: The Resume Is the Least Useful Part of Hiring
Resumes tell you where someone has been. They tell you nothing about how they behaved while they were there....
Week 22 Day 3: Behavioral Questions That Reveal Character
The right behavioral questions do not ask 'what would you do?' -- they ask 'what did you do?' Hypotheticals reveal intentions. Behavior reveals character....
Week 22 Day 4: How to Detect Rehearsed Answers vs. Real Experience
The most dangerous candidates are the ones who have practiced their stories so thoroughly that fiction sounds indistinguishable from experience. But there are tells....
Week 22 Day 5: The Three Traits That Predict Long-Term Success
After two decades of hiring, three traits consistently predict who will succeed on a team over the long term: intellectual humility, follow-through, and the ability to receive feedback without defensi...
Week 22 Day 6: Why Technical Skills Are Trainable but Character Is Not
You can teach someone a new programming language in three months. You cannot teach them to care about their teammates in three years....
Week 22 Day 7: Assignment: Rewrite Your Next Interview to Be 80% Behavioral
This week's assignment transforms your interview process -- take your next scheduled interview and restructure it so that 80% of the questions are behavioral....
Week 24 Day 1: Every Great Leader Has Questions Only They Ask
The best leaders develop signature interview questions -- questions refined through hundreds of conversations that reveal something no standard question can reach....
Week 24 Day 2: The Question That Reveals How Someone Handles Failure
How a candidate describes their failures tells you more about their character than how they describe their successes. The failure question is the most diagnostic tool in your interview arsenal....
Week 24 Day 3: The Question That Reveals How Someone Learns
The speed and quality of a person's learning determines their long-term value to a team. One question can tell you whether someone learns deliberately or accidentally....
Week 24 Day 4: The Question That Reveals How Someone Treats People
How a candidate talks about former colleagues and managers tells you exactly how they will talk about you and your team in two years....
Week 24 Day 5: Building a Question Library That Evolves With You
Your best interview questions will come from your worst hiring mistakes. Every time someone fails on your team, there is a question you did not ask that would have predicted it....
Week 24 Day 6: Reference Checks That Actually Work
Most reference checks confirm what you already know. The reference check that changes a hiring decision is one that asks questions the candidate cannot prepare the reference to answer....
Week 24 Day 7: Assignment: Develop Three Signature Questions
This week's assignment creates your personal interview toolkit -- develop three signature questions that target the traits you value most and commit to testing them in your next ten interviews....
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....
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....
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 di...
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....
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....
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....
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....
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....
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....
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....
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?'...
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....
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?'...
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....
Week 33 Day 1: If You Are Always Putting Out Fires, You Built a Flammable Organization
Firefighting is not leadership. It is the evidence that leadership failed to build systems that prevent fires in the first place....
Week 33 Day 2: Why Firefighting Feels Heroic but Is Actually a Failure
The leader who swoops in to save the day feels like a hero. The team cheers, the crisis is averted, and the adrenaline is addictive. But every heroic save is evidence that the system failed -- and the...
Week 33 Day 3: The Leader as Arsonist -- When Your Chaos Creates the Emergencies
Some leaders do not just fail to prevent fires. They start them. Last-minute direction changes, unclear priorities, unrealistic deadlines, and constant re-prioritization -- these are not leadership. T...
Week 33 Day 4: How to Diagnose Recurring Fires
The first step in building systems is diagnosing which fires are recurring. Not all problems need systems. Only the ones that keep coming back....
Week 33 Day 5: Building a System Is Slower Than Fixing the Problem (and That Is the Point)
The reason leaders default to firefighting instead of system-building is that fixing the immediate problem takes an hour and building a system takes a week. But the leader who invests the week saves m...
Week 33 Day 6: What a Team Looks Like When Systems Actually Work
A team with good systems looks boring from the outside. No drama, no heroics, no all-nighters. Just consistent, predictable delivery. That boring consistency is the result of excellent leadership....
Week 33 Day 7: Assignment: List Your Team's Top Three Recurring Fires
This week's assignment starts the diagnostic process: identify the three recurring problems that consume the most of your team's unplanned time, and calculate the cost of each....
Week 34 Day 1: Chaos Is Not a Market Condition -- It Is an Internal Design Choice
Leaders blame chaos on market conditions, competitive pressure, and organizational complexity. In reality, internal chaos is almost always a design choice -- the result of decisions the leader made or...
Week 34 Day 2: The Hidden Cost of Constant Re-Prioritization
Every time you change the team's priorities, you pay a cost. The visible cost is the rework. The hidden costs are the context-switching overhead, the trust erosion, and the learned helplessness that a...
Week 34 Day 3: The Urgent-Important Matrix Is Not Just a Framework -- It Is a Survival Tool
Eisenhower's urgent-important matrix is the most cited and least applied framework in leadership. If your team spends most of its time in the urgent quadrants, the organization is dying slowly under t...
Week 34 Day 4: How Lack of Process Creates the Appearance of Speed
Leaders who resist process believe that process slows teams down. They are half right -- bad process slows teams down. The absence of process creates the illusion of speed while producing less than a ...
Week 34 Day 5: The Organization's Tolerance for Chaos Reveals Its Leader's Tolerance for Chaos
Organizations reflect their leaders. If the leader tolerates chaos -- or worse, thrives in it -- the organization will be chaotic. The fish rots from the head....
Week 34 Day 6: How to Introduce Calm Into a Chaotic Organization Without Slowing Down
The fear behind resisting process is that calm equals slow. In reality, calm equals focused. A focused team produces more than a frenzied team, faster and with fewer errors....
Week 34 Day 7: Assignment: Audit Your Team's Chaos Sources
This week's assignment: catalog every source of unplanned work and disruption on your team for the past month, and classify each as externally caused or internally caused....
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 36 Day 1: Stop Operating and Start Designing
The most important transition in a leader's career is the shift from operating -- doing the work and managing the work -- to designing -- building the systems that enable others to do and manage the w...
Week 36 Day 2: The Architect Thinks About the System; The Operator Thinks About the Task
When a problem occurs, the operator asks 'How do I fix this?' The architect asks 'Why did the system produce this problem, and how do I change the system so it does not produce this problem again?'...
Week 36 Day 3: What It Means to Design Your Organization Instead of Running It
Designing your organization means making deliberate decisions about structure, process, communication, and decision-making authority -- rather than letting these evolve by accident....
Week 36 Day 4: When to Step Out of Operations -- The 80/20 Rule for Leaders
You cannot design the organization while you are buried in its daily operations. The 80/20 rule for leaders: 80% of the long-term value you create comes from the 20% of your time spent on design, not ...
Week 36 Day 5: How Architects Think: Inputs, Outputs, Constraints, and Feedback Loops
The architectural mindset uses four lenses to analyze any organizational system: what goes in (inputs), what comes out (outputs), what limits the system (constraints), and what information flows back ...
Week 36 Day 6: The Hardest Part of Being an Architect Is Watching Others Operate Imperfectly
When you shift from operator to architect, you must accept that others will operate the systems you designed differently than you would -- and often less efficiently. This is not a failure. It is the ...
Week 36 Day 7: Assignment: Spend One Hour This Week Designing Instead of Doing
This week's assignment: block one hour on your calendar for organizational design work. During that hour, pick one systemic issue your team faces and design a solution -- do not fix the issue manually...
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...
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 syst...
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 spe...
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....
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 connect...
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 ...
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....
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....
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....
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 objec...
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 i...
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...
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 -- f...
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....
Week 39 Day 1: Context-Switching Is the Silent Killer of Team Performance
Every time a team member switches between unrelated tasks, they lose 15-25 minutes of productive focus. A team that juggles five concurrent priorities does not move five things forward -- it moves not...
Week 39 Day 2: Priority Debt Is More Dangerous Than Technical Debt
Technical debt accumulates when you take shortcuts in code. Priority debt accumulates when you take shortcuts in decision-making -- when you say yes to everything rather than making the hard choice ab...
Week 39 Day 3: Stack Ranking Your Priorities Forces Honest Decisions
Most leaders list their priorities as a set of equally important items. Stack ranking forces you to decide which priority is first, which is second, and which is last. The discipline of ordering -- no...
Week 39 Day 4: Saying No Is the Most Important Leadership Skill Nobody Teaches
Every yes is a no to something else. When you say yes to a stakeholder's new request, you are saying no to the time your team would have spent on something already committed. The only question is whet...
Week 39 Day 5: The Urgent-Important Matrix Is Not Enough -- You Need an Attention Budget
The Eisenhower Matrix categorizes work into four quadrants: urgent-important, urgent-not-important, not-urgent-important, and not-urgent-not-important. This categorization is useful but insufficient b...
Week 39 Day 6: What Your Team Accomplishes When They Stop Trying to Do Everything
The paradox of prioritization: teams that work on fewer things accomplish more. Not just more per project -- more total output. Reducing the number of active priorities increases throughput because it...
Week 39 Day 7: Assignment: Cut Your Active Priorities by Half
This week's assignment: count the number of active workstreams your team is pursuing. Then cut that number by half. Decide which half stays and which half is explicitly paused....
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. ...
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 ...
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 efficie...
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...
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....
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 ...
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 documen...
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 u...
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 pea...
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 becaus...
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 wh...
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...
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. Th...
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 do...
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 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...
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....
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 t...
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 ...
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...
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, thei...
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 Def...
Week 48 Day 1: You Are Hiring on Vibes and It Is Costing You
Most leaders hire on intuition. They call it 'culture fit' or 'gut feeling' or 'I just know a good candidate when I see one.' What they actually mean is: I liked this person during the interview. Liki...
Week 48 Day 2: The Hiring Scorecard: Behaviors, Skills, and Culture Add
The Hiring Scorecard has three sections. Section one: key behaviors -- the observable actions that predict success in this specific role. Section two: technical skills -- the capabilities required to ...
Week 48 Day 3: How to Score Candidates Objectively
The scorecard only works if you score honestly. Most leaders score generously -- they avoid low scores because it feels harsh, they inflate scores for candidates they liked, and they find reasons to j...
Week 48 Day 4: The Roadmap Template: How to Plan a Quarter in 90 Minutes
Most roadmap planning takes too long and produces documents that are outdated within weeks. The issue is not that planning is hard -- it is that most planning processes try to achieve certainty instea...
Week 48 Day 5: Running the 90-Minute Roadmap Session
The roadmap template is only useful if the session is well facilitated. A poorly run session produces the same output as no session at all: a list of things that sound important to the person who spok...
Week 48 Day 6: Planning Is Essential, Plans Are Useless
Eisenhower said it: 'Plans are useless, but planning is essential.' The roadmap you created will be partially wrong by week 4. That is fine. The value is not in the document -- it is in the shared und...
Week 48 Day 7: Assignment: Build a Hiring Scorecard for Your Next Open Role
This week's assignment: build a complete Hiring Scorecard for a role you are currently hiring for or expect to hire for in the next quarter. If you have no open roles, build a scorecard for the next r...