Nine lines in a notes app. Learn Spanish to a conversational level, run a half marathon, read 24 books, save six months of expenses, cook five dishes from scratch without the recipe, write something every week, get stronger, finish the certification, sleep better. Each line is a real thing you want, and no single line is unreasonable. That last part is why the list survives every objection you would raise against it. Nothing on it reads as a fantasy.
The first two weeks go well, because a fresh list carries its own momentum. Then the calendar arrives with its actual contents. Weeknights after work and dinner leave ninety minutes, and half of those go to whatever the household needs. Weekends give one free morning. Add a month of that up and the total lands near forty hours of discretionary time, while the list quietly assumes sixty or eighty.
Forty hours divided by nine goals gives each one a bit more than four hours a month. Conversational Spanish does not fit in four hours a month. Neither does saving six months of expenses, or learning five dishes well enough to skip the recipe. The arithmetic was available in January. Almost nobody runs it, because a list of goals does not present itself as a budget. It presents itself as ambition, and ambition does not come with a denominator.
The part willpower cannot fix
A goal costs hours, and it costs hours whether or not you feel motivated that week. Adding a tenth goal does not add hours to the week. It divides the existing hours further, and the division happens quietly, without a notification or a warning. People read the resulting shortfall as a personal failure, which is the wrong diagnosis for a math problem.
The planning fallacy makes the error worse before the first week of work. Daniel Kahneman and Amos Tversky described it in 1979, and Roger Buehler, Dale Griffin, and Michael Ross extended the work through the 1990s with studies of personal project completion. People underestimate how long their own projects will take, and they stay optimistic even after finishing similar projects before. The finish line framework covers how that underestimate lands on a single target. Run it across nine targets and every line carries its own quiet undercount, and the undercounts add together rather than cancelling out.
Every active goal claims attention whether you are working on it or not
The common assumption is that a goal costs you the hours you spend on it. Research on goal systems says something less convenient. James Shah, Ron Friedman, and Arie Kruglanski published a set of six studies in 2002 under the title “Forgetting All Else,” and the pattern they found is that activating a goal you are committed to suppresses the accessibility of your other goals. They gave participants lists of activities they intended to complete that week and measured how quickly each goal came to mind. Committing to one goal made the alternatives harder to retrieve.
Read that mechanism from the other direction and it describes the cost of a long list. Nine committed goals sit in one attention system, and every one of them competes for retrieval against the other eight. The competition does not require you to be working. A goal you are committed to stays active, and active material draws on the same limited supply that focused work needs.
Shah’s team also found a moderator worth knowing about. The shielding effect weakened for participants reporting higher anxiety and depression. That detail matters because the people carrying the longest lists are often the ones most anxious about them. The mechanism that would normally help you tune out eight goals and focus on one gets less reliable at the point where you need it most.
This is the same territory the Zeigarnik effect covers from a different angle. An unfinished goal stays in memory, and a list of nine keeps nine of them there. The ceiling on how many open loops a person can hold without a drop in focus sits lower than most lists suggest.
A shared path splits the credit
There is a second mechanism, and it shows up when two goals happen to share the same activity. Ying Zhang, Ayelet Fishbach, and Arie Kruglanski tested this in a 2007 paper on the dilution model, across six experiments. They increased the number of salient goals that one means could satisfy and measured how much participants believed the means served each goal. The session stayed exactly as effective. What fell was the perceived instrumentality, the sense that the workout was doing its job.
The gym makes this concrete. One training session serves strength, weight loss, and stress relief at the same time. Add a fourth goal to that session, say the running base you are building, and the hour does not get more productive. It gets more crowded, and each stated reason for being there carries less weight than it did when three goals shared the hour.
The reverse case holds as well. Adding a second means to a single goal weakens the pull of both, which is why the runners who buy a treadmill, a gym membership, and a set of trail shoes in the same week often end up using none of them. Dilution runs in both directions along the same path.
Two goals can fight over the same hour
Volume is one shape of the problem. Overlap is the other. Robert Emmons and Laura King studied it directly in 1988 with a personal strivings framework. Eighty-eight undergraduates in two studies listed fifteen of their strivings and rated how much conflict they felt between them, along with how ambivalent they felt about each one. The participants then kept diaries and answered experience-sampling prompts over the following weeks. Higher conflict and ambivalence predicted worse psychological and physical outcomes, measured on daily mood and on reported symptoms.
Spend a week inside that finding and the practical form is easy to spot. The hour before work can hold the running goal or the writing goal. It cannot hold both without one of them paying for the other. The half marathon build and the get-stronger goal both ask for the same recovery, so progress in one arrives at the expense of the other. Reading 24 books and finishing the certification both want the 9pm slot, the last hour of useful attention in the day.
Conflict of that kind stays invisible on a list. Nine lines of text look parallel and independent. The hours behind them are neither. Two goals that overlap add their costs plus the interference between them, and a tracker that treats every goal as its own island repeats the error that created the list.
The mid-goal slump shows what happens when the overlap is not resolved. Motivation fades around the sixty percent mark, which is the point where a person starts comparing the remaining distance against the remaining time. A short list reaches that comparison with room to finish. A long list reaches it holding goals that were never funded in the first place.
The number is smaller than the list
The arithmetic points at a smaller number than the list suggests, and the size of that number depends on which goals are competing rather than on how much discipline you have. Capacity comes from the calendar and the overlap pattern. Discipline does not enter the arithmetic.
The process starts with an audit of the hours instead of the intentions. That audit needs a way to convert a goal into weekly hours, and a way to read a list once the hours are on it. Both run against real lists below, followed by what to do with the goals that do not fit this season.
What a goal costs in hours
Any article quoting a single ideal number of goals has skipped the part that decides it. Capacity sits in the hours, and the hours a goal needs change with the goal. Two goals drawing on the same resource behave like more than two, which is why the count of lines on a list is the wrong unit of measurement.
Converting a goal into hours takes one step. Work out the sessions the goal needs per week, then multiply by the length of a session. A running goal at three runs a week takes about two hours. Twenty pages of reading a day takes three and a half. A language goal at twenty minutes a day takes a little over two. Three strength sessions at fifty minutes each take two and a half. Add those four together and they want close to ten hours a week, before the week has contained a single unforeseen thing.
For most people holding a job and a household, ten hours a week of discretionary time is the entire budget, and the budget is usually smaller than it feels because the timetable fills with commitments that arrived without asking. The number of goals a person can carry equals the number of goals whose weekly hours fit inside that budget. In practice the total lands between two and four active goals, and the ceiling moves with the season. A quiet stretch with no travel supports four. A month with a move, a launch, or a sick child supports one.
Resource type matters as much as volume. A reading goal spends evening attention. A running goal spends mornings and legs. Those two coexist comfortably. A half marathon build and a strength program compete for the same recovery, so running them together costs more than their hours suggest. Before cutting a goal, check what it draws on, because two goals using different resources often fit where one of them plus a lookalike would not.
What the numbers look like in practice
The arithmetic gets easier to trust with real lists attached to it.
A seven-goal list that carries three
Start with a list that looks moderate: run 500 km, read 24 books, learn guitar, save $6,000, finish a certification, cook 50 new recipes, call family every week. Weekly hours come out at two for running, three and a half for reading, two for guitar, four for the certification, two for cooking, one for calls, plus an hour of admin on the savings goal. That totals about fifteen and a half hours against a ten hour budget.
The first pass does not cut anything. It reclassifies. The savings goal runs on a scheduled transfer, so it stops being a time goal and becomes a monthly check of the balance, which returns an hour. The weekly calls fit inside an existing commute, so they cost nothing extra. Home cooking overlaps with eating, which means only the difference between cooking and not cooking belongs in the budget, and that difference is smaller than the two hours it was charged. The list now sits at twelve and a half hours with nothing removed.
The second pass cuts two things. Guitar has no deadline attached and loses nothing by waiting a season, so it moves to the parking lot. Cooking at fifty new recipes was a stretch version of a goal that works at twenty, so the target drops and the hours with it. The list lands at nine and a half hours: running, reading, and the certification active, savings and calls running on autopilot, guitar parked. Seven lines became three funded goals plus two maintenance items, and nobody had to find more willpower.
A two-goal list that carries five
A short list can hold a long list wearing fewer names. Take two goals that look modest: get fit, and write a book. Unpacked, get fit means three gym sessions, two runs, seven hours of sleep a night, and less drinking. Write a book means an outline, 500 words a day, and the research reading that feeds it. Two lines of text contain nine commitments and somewhere around eighteen hours a week.
The list is already short, so shortening it further changes nothing. The fix is to name one countable target per goal and let the rest go. A 500 km running target replaces get fit. A 60,000 word draft replaces write a book. Sleep and drinking are conditions the goal runs on rather than separate goals, which means they belong in the calendar as constraints instead of entries in a tracker. The packed list becomes two goals with two targets and a much smaller weekly bill.
A list drawing on different resources
Some lists carry more than their length suggests. A reading goal spends evenings. A language goal spends the commute. A savings goal spends money rather than time and asks for one look a month. Those three coexist because they draw on separate resources, and the interference between them is near zero.
Compare that with a list of three goals that all want the same 6am hour. The same count of goals produces a different amount of strain. Reading the list tells you nothing until you know which resource each goal spends.
The parking lot
Parking is how a goal leaves the active list without leaving your life. It takes one extra document, and the document has two fields: the goal with its target, and the season you intend to start it. That is the whole method.
A few rules keep the parking lot from becoming a graveyard. The lot has a review date, so parked goals get read once a season rather than forgotten. A parked goal keeps its name and its number, because an intention that loses its target stops being a goal. Nothing moves out of the lot without something moving in, which keeps the active list at the size the calendar can fund.
Parking a goal is a scheduling decision. The ambition behind it survives the delay, the target survives the delay, and the only thing that changes is when the hours get spent.
What the tracker should do with a parked goal
This is where the two tracking models part company, and the difference decides whether parking feels safe. A streak app stores its record in the streak. Stop working on the goal and the streak ends, which means the record dies with the pause. The app has nothing left to show you about the four months you spent on it, and the natural response is to avoid opening the app at all.
A milestone tracker stores the record in the entries. Stop working and the entries stay where they were, holding whatever distance you covered. Notch keeps the goal with its target and its logged dots, so a parked goal reads as a goal with a total rather than a failure with a date on it. A finished goal can be archived with its record intact. Nothing expires, and nothing resets to zero because a month went quiet.
That property is what makes a short list possible. Parking a goal only works if the progress already logged survives the wait, and a tracker that measures completed volume rather than consecutive days is the version that allows it. The distinction between measuring attendance and measuring distance is the whole argument behind the milestone tracker, and the ultimate guide to milestone goal tracking covers it across every goal type.
The objections that come up
Pressure tolerance comes up in every conversation about this, and it is the least useful variable. Capacity is measured in hours. Discipline changes how reliably you convert the hours you have into work; it does not create hours. A person with flawless follow-through carrying nine goals still holds nine goals against the same budget, and the follow-through raises the fraction of the budget that gets used rather than the size of it. The useful question is which few things deserve the hours.
Goals that appear to cost no time deserve a separate look. Sleeping more, drinking more water, standing up straighter: none of these ask for a block on the calendar, which makes them feel free. A goal that asks nothing of your week is a condition your week runs on rather than a goal with a finish line. Tracking it as a goal adds an entry to a list without adding capacity, which is how lists grow past what anyone can fund. Put the condition in the calendar and keep the tracker for goals that have a target.
Anyone whose weeks are larger can scale the arithmetic without changing it. Double the budget and more goals clear the bar. The audit runs the same way, and the number of active goals rises with the hours rather than with the enthusiasm.
Parking reads like quitting to a lot of people, and the reading is worth correcting because it costs a season. A parked goal keeps its name, its target, and its record. A deleted goal loses all three, and that loss is what people fear when they resist the shorter list.
Common Questions
Is there an ideal number of goals? Three funded goals covers most people with a full week, and the number moves with the season rather than with your ambition. Count the goals whose hours fit the budget, then count everything else as parked.
Does the number change across the year? Yes. December holds fewer usable hours than a quiet stretch in spring, and the goal set should follow the calendar. A goal that waits for a lighter month is a goal that gets a real chance.
How is this different from prioritization? Prioritization ranks goals by importance. This ranks them by cost. Two goals can both matter enormously and still not both fit inside the same ten hours, which is the case a ranking exercise misses.
What about a goal I cannot put hours on? Count the sessions instead of the hours. A readable unit like twenty sessions or one finished draft works, and it holds the goal to something countable while the calendar stays flexible.
Do I have to delete a parked goal? No. Deleting throws away the target and everything logged against it. Parking keeps both and schedules the work for a season that can hold it.
What happens if I keep all nine anyway? The hours get divided further, every goal moves slower, and the one with the nearest deadline takes the hit. The list does not fail loudly. It fails as nine things moving at four hours a month each, which is slow enough that none of them reaches a finish line before you stop caring.
The list was never funded, and the fix is arithmetic rather than effort: count the hours, name the targets, park what cannot run this season, and let the tracker hold the record so the wait costs you nothing.
Notch is free to download. The full app unlocks with a one-time $9.99 purchase. Every goal carries a target number and a finish line, progress accumulates, and gaps do not erase what you have already done.
Try Notch
Every notch counts.
A milestone tracker without streaks, guilt, or subscriptions.
Download on App StoreFree · $9.99 Pro · No subscription