An AI-generated podcast companion to this article, produced with Google Gemini Notebook.
Most leaders who reach a certain level get the same feedback, worded differently by different bosses. Stop operating like you did two roles ago. Get out of the weeds. Spend more time on the things only you can do. The advice is correct, and it's almost useless on its own, because it tells you what to stop doing without giving you a way to tell the difference between the meeting that deserves your attention and the one that's just a habit you haven't examined.
This is why time management systems tend to disappoint. They evaluate every task on its own terms: urgent or not, quick or long, in your inbox or someone else's. What's actually missing isn't a better list. It's a filter, a standard everything on your plate has to pass through before you decide what to do with it. And that filter doesn't come from you. It comes from understanding, with real clarity, how your role connects to the reason your organization wins in the first place.
The Winning Proposition Belongs to the Organization
Strategist Willie Pietersen coined the term for that reason: a winning proposition. He frames it as the answer to two linked questions. What unique benefits will the organization deliver that give a customer a compelling reason to choose it over any alternative? And how will it translate that value into superior financial returns for the enterprise and the people invested in it?
A winning proposition is not a personal thing. It belongs to the organization. There is one of them, and it sits above any individual role. The framework I use to make it concrete — Who, What, and How — is my own way of operationalizing Pietersen's two questions into something an organization can actually articulate and use.
Who is the specific customer or market segment the organization has chosen to serve, not "everyone who might buy this," but the particular group whose needs it has decided to prioritize above all others. What is the offering built to meet a defined need for that group: the product, service, or experience that gives them a genuine reason to choose it. How is the delivery model, the way that offering actually gets built and brought to that customer in a manner competitors can't easily copy: the operating model, the channel, the capability, or the relationship that makes the value real rather than theoretical.
None of the three means much on its own. Who without What is just a target market with nothing distinctive to offer it. What without Who is a product looking for a home, technically well built but aimed at no one in particular. And Who plus What without a real How is a good idea with no way to deliver it better than anyone else could. A winning proposition lives in the intersection of the three: a specific customer, with a specific offering built for their need, delivered in a specific way that's genuinely hard to replicate. Change any one of the three and the other two usually have to change with it. A different Who often demands a different What. A different How can open up a Who that wasn't viable before.
This is also why defining a winning proposition is rarely a one-pass exercise. It usually takes testing more than one combination before something holds up: trying a Who against more than one possible What, or testing whether a promising How could serve more than one Who, until a combination emerges that's both genuinely valuable to the customer and genuinely difficult for a competitor to match. A well-known example: Warby Parker didn't start by deciding to sell cheap glasses. It found its winning proposition at the intersection of a specific Who, style-conscious but cost-conscious eyewear buyers frustrated with high prices, a specific What, affordable prescription eyewear that didn't look cheap, and a specific How, a direct-to-consumer model with home try-on that eliminated the traditional optical retail markup. Any one of those three alone was a common idea. The combination was not.
When Who, What, and How are clear, tested, and aligned, an organization has a winning proposition it can actually compete on. When they aren't, what gets called "strategy" is usually just a list of activities with a mission statement stapled to the front.
Line of Sight: Where the Filter Actually Lives
Here is the problem a lot of otherwise well-run organizations have. Leadership can articulate the winning proposition with total clarity in a boardroom, and most of the people doing the actual work still have no idea how what they do in an ordinary week connects to it. The strategy is real. It just isn't visible from where they sit.
That visibility has a name: line of sight. It's the clarity an individual has about how their specific role, team, and decisions ladder up into the organization's chosen Who, What, and How. Not a general sense that their work "matters." A specific understanding of which part of the winning proposition they're responsible for advancing, and how.
Line of sight is not the same thing as knowing the mission statement. Plenty of people can recite one and still have no idea whether the project in front of them moves the organization closer to its winning proposition or simply keeps them busy. Line of sight means being able to trace a straight line from a specific task to a specific piece of Who, What, or How. When that line exists, you have something most calendars lack: a working filter. When it doesn't, every task looks equally justified, because there's nothing to measure it against.
Building that line of sight is a shared responsibility. Leaders owe their people a genuinely clear, current picture of the organization's Who, What, and How, not a slogan, not a values poster, the actual logic of how the organization intends to win. And individuals owe themselves the discipline to keep asking how their own role connects to it, rather than assuming someone above them is holding that picture so they don't have to.
Stepping Up, Stepping Back
Leadership scholar Elsbeth Johnson's Step Up, Step Back model, developed from years of research into why strategic change efforts stall, argues that leading change well requires two distinct phases, done in the right order, rather than a leader simply picking a style and staying in it.
Stepping up comes first, and it requires more from a leader than most expect, not more charisma or more visible activity, but more clarity and more deliberate alignment. Clarity means being specific about what the change is meant to deliver, what outcomes will result, how people need to behave differently with each other and with customers, and how this connects to what the organization has already been doing rather than arriving as one more disconnected initiative. Alignment means backing that clarity with substance, through the everyday conversations leaders have, the actions they visibly take, the resourcing and people they commit to the effort, and the metrics they actually hold people to. Johnson's research found that leaders who skip this stepping-up work don't get calmer organizations. They get what she calls manager heroism: the people below them left to compensate, through sheer individual effort, for direction the leader never provided.
This is exactly where line of sight comes from. It isn't something individuals are supposed to piece together on their own. It's the product of a leader doing real stepping-up work: being specific enough about the organization's Who, What, and How, and reinforcing it consistently enough through conversation, action, resourcing, and metrics, that people several levels down can trace their own work back to it. Where that stepping up hasn't happened, no amount of individual effort produces real line of sight, because there's nothing solid to connect to.
Stepping back is the second phase, and it only works once the first one is genuinely done. With clarity and alignment in place, a leader can deliberately do less: stop making decisions that belong to the people now equipped to make them, and let the organization run on the line of sight it's been given rather than on constant intervention. Leaders who never step back become the bottleneck. But leaders who try to step back before they've stepped up just create confusion, because there was never a real filter for anyone to use in the first place.
The individual side of stepping back is where the 5 Ds come in. A leader stepping back creates the room; the 5 Ds are how an individual, at any level, actually decides what to do with it.
The Five Ds: Turning Line of Sight Into a Practice
Once you have real line of sight to your organization's winning proposition, every task, meeting, and recurring commitment can be run through the same comparative question: does this support the winning proposition more, or less, than the other ways I could be spending this time right now? Not a yes-or-no test. A relative one. Almost everything on a calendar supports the mission somewhat. The filter that matters is which things support it most, given everything else competing for the same hours.
That comparative question resolves into five decisions. Not a priority matrix that sorts things by urgency and importance and stops there. Five specific answers to what you actually do about each item, once you know how it stacks up against the alternatives.
1. Do — It Ranks Highest Against the Alternatives
A task earns your direct, personal attention when, measured against everything else you could do with that time, it does the most to advance the piece of the winning proposition your role is responsible for, and it specifically requires your judgment or authority to do well. Urgency alone doesn't qualify a task for this category. Importance alone doesn't either. The test is comparative and specific: of everything competing for this hour, is this genuinely the highest-leverage use of it, and am I the right person for it right now?
2. Defer — It Matters, Just Not More Than What's Ahead of It
Some tasks clearly connect to the winning proposition but lose the comparison to something more time-sensitive. Deferring is not avoidance. It's ranking honestly and choosing when to act with intention rather than reacting to whatever feels loudest today. A task can matter and still not be the best use of this particular week.
3. Downsize — It Costs More Than the Support It Provides
Some items resist progress because they've grown too large, too vague, or too perfectionist relative to how much they actually advance the winning proposition. A quarterly report can become a one-page brief. A recurring meeting can become an async update. A deliverable scoped for "flawless" can be rescoped for "adequate and on time." Downsizing brings a task's size back in line with the amount of support it actually provides, relative to everything else it's competing against.
4. Delegate — Someone Else Can Deliver the Same or More Support
A task can clearly support the winning proposition and still not require you specifically. That's the signal to delegate, not because you're too busy, but because someone else is genuinely positioned to deliver as much or more of that support, while building their own capability in the process. Delegation done well requires the same rigor as any other decision: a real match of skill to task, clarity about context and expectations, and an accountability structure that lets you let go without losing visibility.
5. Delete — It Doesn't Move the Winning Proposition at All
Delete is the most direct application of the filter, and the one leaders resist most. A task or meeting deserves deletion when, held up against the organization's Who, What, and How, it contributes nothing measurable, however established or comfortable it's become. It exists out of habit, inherited obligation, or somebody else's priorities rather than a real line back to the winning proposition. The uncomfortable version of this is that some items land here even though they feel important. They may be genuinely important, to a different priority, in a different part of the organization. Just not the one your role exists to advance.
The 4 Ds that aren't Do exist for a single reason: to protect the one D that is. Defer, downsize, delegate, and delete are how "stepping back" actually gets done, one task at a time, instead of remaining a nice idea you agree with in the abstract.
Why the Two Have to Work Together
Line of sight without the discipline to defer, downsize, delegate, and delete stays aspirational. You can understand exactly how your role connects to the winning proposition and still end up with a calendar that looks identical to last year's, because understanding the connection doesn't by itself remove anything from your plate. The Ds are the mechanism.
Just as clearly, the 5 Ds without line of sight collapse into a generic productivity exercise. You can defer, downsize, delegate, and delete your way through a task list using nothing but instinct, and still have no idea whether what's left actually reflects the priorities your role is meant to serve. Sorting is not the same as leading. Line of sight is what turns sorting into a strategic act, because it gives you something real to sort against.
Used together, they answer the two halves of the same problem. Line of sight tells you what stepping up actually means, in specific enough terms to act on. The 5 Ds tell you, task by task, how to step back from everything that isn't that.
The Question
For everything on my calendar this week: does this support my organization's winning proposition more, or less, than the other ways I could be spending this time?
You don't need to run this exercise on every item forever. You need to run it once, honestly, and then again whenever the calendar starts to feel like it's running you instead of the other way around. That's usually the surest sign your line of sight has quietly gone missing, not that you've lost the ability to prioritize.