Prioritization
Choosing what matters most and protecting focus
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 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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
Read commentary →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.
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 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 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 nothing forward while appearing busy.
Read commentary →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 about what matters most. Priority debt compounds faster than technical debt because it wastes human capacity, which is your most expensive and least recoverable resource.
Read commentary →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 -- not just listing -- is where the leadership value lies.
Read commentary →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 whether the no is explicit (you choose) or implicit (your team's capacity chooses for you).
Read commentary →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 because it does not account for the scarcity of attention, which is the true constraint on team performance.
Read commentary →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 eliminates the overhead that kills productivity.
Read commentary →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.
Read commentary →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. Liking someone is not the same as evaluating them. And hiring based on liking produces teams that feel comfortable but underperform.
Read commentary →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 do the work. Section three: culture add -- what this person brings to the team that the team does not already have.
Read commentary →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 justify the score they want to give rather than giving the score the evidence supports. Objective scoring requires discipline.
Read commentary →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 instead of clarity. You cannot know what will happen in every week of the quarter. You can know the three things that matter most and protect them from everything else.
Read commentary →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 spoke loudest or the stakeholder who pushed hardest. Good facilitation means every voice is heard, the best ideas win regardless of source, and decisions are made rather than deferred.
Read commentary →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 understanding the document represents. When the plan changes, update the roadmap. When it needs to stay, protect it.
Read commentary →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 role you would hire if you had the budget. The exercise is valuable even as a hypothetical because it forces you to articulate what you actually need.
Read commentary →Get Prioritization Daily
Receive one 52-week leadership course entry each morning with commentary. Free, no spam, unsubscribe anytime.
Start Free Daily Email