Delegation
Assigning work effectively and letting go of control
Week 5 Day 1: Your Job Is to Make Their Job Possible
Your team does not need you to do their work. They need you to make it possible for them to do their work without fighting the organization to get it done....
Week 5 Day 2: Carrying the Load Feels Noble but Breaks Teams
The leader who carries the heaviest load is not the strongest leader. They are the leader whose team never learned to carry anything....
Week 5 Day 3: What Clearing the Path Actually Looks Like
Clearing the path is not a metaphor. It is a series of specific, boring, structural actions that make your team's work flow without friction....
Week 5 Day 4: The Three Questions: What Is Blocking You? What Do You Need? What Should I Stop Doing?
Three questions will tell you more about your effectiveness as a leader than any engagement survey ever written....
Week 5 Day 5: When the Path Is Unclear Because You Made It Unclear
Sometimes the biggest obstacle in your team's path is the ambiguity you created and never cleaned up....
Week 5 Day 6: The Leader Who Does Too Much Creates a Team That Does Too Little
Every task you take on that your team could handle is a vote of no confidence they can feel even if you never say it out loud....
Week 5 Day 7: Assignment: Ask Your Team What Is Slowing Them Down
This week's assignment: in your next one-on-one with each team member, ask one question and write down every answer. The question is: 'What is the biggest thing slowing you down right now that I could...
Week 8 Day 1: Frustrations Are Drains, Not Failures
A Working Genius frustration is not a skill you have not learned. It is a type of work that will always cost you more energy than it returns, no matter how proficient you become at doing it....
Week 8 Day 2: What Happens When You Force Yourself Into Frustration Work
The leader who spends 40% of their week in frustration areas is not being disciplined. They are running at half capacity and calling it dedication....
Week 8 Day 3: Your Team Feels It When You Are Drained
Energy is contagious. When you are operating in your frustration zone, your team does not just lose your best work -- they absorb your depletion....
Week 8 Day 4: The Meeting You Hate Is the Meeting Someone Else Was Born to Run
That recurring meeting that drains you every week? Someone on your team would love to own it. Your frustration is their genius -- and you are standing in the way....
Week 8 Day 5: Delegating Your Frustrations Is Not Laziness
Delegating your frustration areas is not avoiding work. It is routing work to the person who will do it best, fastest, and with the most energy....
Week 8 Day 6: How to Restructure Your Week Around Energy, Not Obligation
Most leaders build their calendars around obligations. The best leaders build theirs around energy -- front-loading genius work and containing frustration work to low-impact windows....
Week 8 Day 7: Assignment: Audit Your Calendar for Frustration Work
This week's assignment: color-code your calendar for the next five business days. Green for genius, yellow for competency, red for frustration. Then identify one red block to delegate or restructure....
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 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....
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....
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....
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....
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....
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....
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....
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....
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....
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....
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 n...
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....
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 skil...
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....
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 31 Day 1: Your Team Has Different Geniuses -- Use Them
Every person on your team has a different combination of Working Genius types. The leader who assigns work without understanding those types is wasting talent and generating frustration....
Week 31 Day 2: The Inventor Needs Freedom, Not Process
Inventors -- the people whose genius is creating novel solutions -- thrive in unstructured space. Put them in a rigid process and you will get compliance where you needed creativity....
Week 31 Day 3: The Discerner Needs Input, Not Isolation
Discerners have a gut-level ability to evaluate ideas, solutions, and plans. But that ability only activates when they have something to evaluate. A Discerner without input is wasted talent....
Week 31 Day 4: The Finisher Needs Clarity, Not Ambiguity
Finishers -- the people with Tenacity genius -- turn ideas into completed work. They thrive on clear targets and defined endpoints. Ambiguity is not a challenge for them; it is poison....
Week 31 Day 5: What Happens When You Put the Wrong Genius in the Wrong Role
Putting an Inventor in a Finisher role does not just produce bad work. It produces a demoralized person who starts to believe they are incompetent at their job....
Week 31 Day 6: How to Structure Work So Every Genius Thrives
The goal is not to protect people from work they dislike. The goal is to structure the workflow so each phase is led by the person whose genius matches that phase....
Week 31 Day 7: Assignment: Map Your Team's Working Genius Profiles
This week's assignment creates a visual map of your team's collective Working Genius, revealing where you have surplus, where you have gaps, and how to restructure work for maximum alignment....
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 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 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...