A producer has two strong projects that both seem worth doing. One could be finished in ninety days; the other could change the next five years. Both are attractive, but only one can receive the hours that make that attraction matter.
People often first ask “Could I do this?” It is the wrong question since the answer is usually yes for plenty of things on any list and capability alone does not resolve the list. A person who can write, structure, teach, sell and finish could, in principle, do any of the fifteen things on last week’s list. The fact that each is possible is precisely why the list does not get smaller.
Possibility is a statement about ability. It is not a statement about this season or the consequences that would follow from spending the next ninety days on one thing rather than another. The question, then, has to go beyond attraction. A project can remain appealing while still being wrong for this season. Timing and capacity matter more than whether it pulls you in. Only those considerations can tell you what is yours to finish.
Deserving feels different. A project deserves this season when there is a reason it has to happen now, a reason that would be weaker next year. That reason might be external, like a closing window of opportunity, a person who is available now, or a question that is live in the world but will not remain so. It might also be internal, like a skill at its strongest, a question you cannot stop asking or an obligation whose weight is at its maximum. Whatever it is, it has a date attached to it. If you cannot name why it has to happen now, it may be attractive, but attractive projects can wait.
There are three checks that can help decide what is yours to finish:
First, does the project require you specifically and not just someone who is capable? The question is not whether you could do it well. If another capable person would end up with roughly the same result, the project may still be worth doing, but its claim on your time is weaker. And the slot it occupies is where the thing only you can make could’ve gone.
Second, can it be closed within a season you can name? Some work genuinely takes years, but a project without a clear season tends to consume every season. The test is not “is it finishable in principle,” because everything is finishable in principle. The test is whether you can name, right now, the month in which it would be done and believe that date.
Third, does finishing it change what you can do next? Some projects, once finished, open a new door from which the next thing becomes possible. Others only close a loop. Both are legitimate, but a slot given to the second kind can cost you the first kind. If you cannot say what finishing a project would let you do that you cannot do now, it may be something worth completing eventually rather than something that deserves the next ninety days.
Score each project and keep the result. A project that passes only two tests is not automatically rejected. Rather, treat it as unresolved: identify which test(s) it failed and decide whether that failure can be fixed, time-bounded or accepted before granting the slot. In this framework, unresolved projects are parked with a return date rather than allowed to continue drifting forward.
Now the exercise for this week.
Suppose the next ninety days has room for exactly one project to finish. Not necessarily the one you love most, but the one that earns the slot when you run it through the three tests. Which is it?
If the answer arrives instantly, inspect what that immediate answer skipped. Attraction is relevant, but it is not the same as fit for this season. Run the tests again slowly and make the trade-offs explicit. If no answer arrives because the projects seem tied, that is also information. A tie among fifteen means the tests were not actually applied; they were consulted and then overruled by the feeling that everything matters. But the tests are not about what matters. They are about what has a claim on your slot this season, and ties are rare once you hold the question that tightly.
A project that fails the first test can be delegated, pursued through collaboration or done at lower intensity in the background. One that fails the second can be split or parked until a season can be named. A project that fails the third can wait until something it would unlock becomes needed. None of them is killed by this exercise. That decision is separate, requires its own evidence and comes later. This exercise decides only which project gets the slot.
There is one more thing the tests do, and it is the real reason to run them. If attraction is the only selection rule, it may not distinguish work that specifically requires your judgment from work another capable person could also make. These tests are therefore designed to give more weight to specificity, seasonality and consequence. They are a selection framework, not proof that the chosen work is uniquely “yours.”
So: one slot, ninety days. Which project earns it, and what did it have that the others did not?
Wednesday for paid members. The One-Slot Decision turns this judgment into a five-line card for each project, including the line you cannot skip: what loses the next ninety days if this project wins. Attraction does not get a line. Tune in then.



