An AI-generated podcast companion to this article, produced with Google Gemini Notebook.
Most leaders eventually hear some version of the same feedback. Stop operating like you did two roles ago. Get out of the weeds. Spend more time on what only you can do. It's correct advice, and almost useless on its own, because it tells you what to stop doing without telling you how to recognize the difference between the meeting that deserves your attention and the one you simply stopped questioning.
Time management systems don't solve this, because they evaluate every task in isolation: urgent or not, quick or long, yours or someone else's. What's missing isn't a better list. It's a filter for separating signal from noise, a standard everything on your plate has to pass before you decide what to do with it. And that filter doesn't originate with you. It comes from understanding, specifically, how your role connects to the reason your organization wins in the first place.
The Winning Proposition
Strategist Willie Pietersen gave that filter a name: a winning proposition. He frames it as the answer to two linked questions. What unique benefit will the organization deliver that gives a customer a compelling reason to choose it over any alternative? And how will it convert that value into superior financial returns for the enterprise and the people who've invested in it?
A winning proposition isn't personal. It belongs to the organization, not to any one role within it. I use a simple framework to make it concrete: Who, What, and How. It's my own way of operationalizing Pietersen's two questions.
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. How is more than just a strategic moat, though. Very often, it's also what makes the Who choose that particular What in the first place, not just what protects the choice once it's made.
None of the three means much on its own. Who without What is a target market with nothing distinctive to offer it. What without Who is a well-built product aimed at no one in particular. Who and What without a real How is an idea that competitors can easily copy and doesn't deliver superior value. A winning proposition lives in the intersection of the three.
When Who, What, and How are clear 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: How You Access the Signal
Many organizations, even those that are well-run, often hit the same wall. Leadership has some vague, implicit understanding of their organization's winning proposition, but the people doing the actual work can't tell you how what they do connects to it. The strategy may be real, but it simply isn't visible from where most employees sit.
That visibility has a name: line of sight. It's the clarity an individual has about how their role, team, and daily decisions ladder up into the organization's chosen Who, What, and How. Not a general sense that their work "matters," but a specific understanding of which part of the winning proposition they're responsible for advancing, and how.
Line of sight isn't the same 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 just keeps them busy. Line of sight means tracing 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.
Line of sight isn't something you can just wait to receive, either. It takes real discipline to keep asking how your own role connects to the organization's Who, What, and How, rather than assuming someone above you is holding the full picture so you don't have to.
Stepping Up, Stepping Back
Elsbeth Johnson's Step Up, Step Back model was built on years of research into why strategic change efforts stall, and her logic is just as useful for a leader who needs to distill signal from noise and lead at the right level. It all starts with stepping up: creating real clarity and deliberate alignment around the organization's winning proposition, backed by the everyday conversations leaders have, the actions they visibly take, the resourcing they commit, and the metrics they actually hold people to. Skip this work, Johnson's research found, and leaders don't get calmer organizations. They get manager heroism: the people below them compensating, through sheer individual effort, for direction the leader never provided.
This is exactly where line of sight comes from. It isn't something individuals piece together on their own. It's the product of a leader doing real stepping-up work, specific enough about the organization's Who, What, and How, and reinforced consistently enough through conversation, action, resourcing, and metrics, that people several levels down can trace their own work back to it. Skip the stepping up, and no amount of individual effort produces real line of sight. There's nothing solid to connect to.
Stepping back is the second phase, and it only works once the first is genuinely done. With clarity and alignment in place, a leader can do less on purpose: stop making decisions that belong to 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. 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 space. The 5 Ds are how an individual, at any level, decides what to do with it.
The Five Ds: How to Triage Once You Have the Signal
Once you have real line of sight to your organization's winning proposition, every task, meeting, and recurring commitment can run through the same comparative question: does this support the winning proposition more, or less, than the other ways I could spend this time right now? It's not a yes-or-no test. It's a relative one. Almost everything on a calendar sounds like signal until you actually compare it to the alternatives. What matters is which things support the winning proposition most, given everything else competing for the same hours.
That comparative question resolves into five decisions, not a priority matrix that sorts by urgency and importance and stops there, but five specific answers to what you actually do with 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 attention when, measured against everything else competing for that time, it does the most to advance the piece of the winning proposition your role owns, and it specifically requires your judgment or authority. Urgency alone doesn't qualify a task here. Neither does importance alone. The test is narrower: 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. They just lose the comparison to something more time-sensitive or valuable. Deferring isn't 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 Value 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. In instances like these, a quarterly report becomes a one-page brief. A recurring meeting becomes an asynchronous update. A deliverable scoped for "flawless" gets rescoped for "adequate and on time." Downsizing takes a specific kind of judgment: recognizing when done is genuinely better than perfect, rather than defaulting to more polish than the winning proposition actually requires. It brings a task's size back in line with the value it actually provides, relative to everything else competing for the same hours.
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 takes 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. ACCORD: A Framework for Delegation That Develops People walks through how to have that delegation conversation well.
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 earns deletion when, held up against the organization's Who, What, and How, it contributes nothing measurable, however established or comfortable it's become. It survives on habit, inherited obligation, or somebody else's priorities, not a real line back to the winning proposition. Some of what lands here will still feel important. It may be, to a different priority, in a different part of the organization. Just not the one your role exists to advance.
The four Ds that aren't Do all exist to maximize your value to the organization. Defer, downsize, delegate, and delete are how "stepping back" actually gets done, one task at a time.
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 remove anything from your plate by itself. The Ds are the mechanism.
The 5 Ds without line of sight collapse just as easily, into a generic productivity exercise. You can defer, downsize, delegate, and delete your way through a task list on instinct alone and still have no idea whether what's left reflects the priorities your role is meant to serve. Sorting isn't 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 both halves of the same problem. Line of sight tells you what stepping up actually means, specifically enough 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 spend this time?
You don't need to run this exercise on every item forever. Run it once, honestly, and 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 gone missing, not that you've lost the ability to prioritize.