Is Doing Less Giving Up? How to Reprioritize a Project List
Doing less can mean giving up on a project, but it can also mean making a deliberate choice about where limited time and effort should go now. Review each item against your current priorities, likely value, effort, deadlines, and dependencies. Then give it one clear status: continue, postpone, or stop. A decision is more useful when it names what will happen next and when you will reconsider it.
Start with the priority that matters now
Before ranking projects, write down one or two priorities that reflect your current circumstances. Make them specific enough to guide a choice: finish a course by a certain month, prepare for a planned move, or complete a particular work deliverable. A vague ambition such as “be more productive” cannot help distinguish between competing projects.
This is a practical decision aid, not a formula that can prove which project is best. Project-prioritization guides commonly compare work by impact, urgency, effort, and fit with broader goals; Atlassian also recommends recording expected outcomes, effort, risks, and dependencies when comparing items. Use those factors to make your own trade-offs visible, rather than treating a score as an objective verdict. Atlassian’s prioritization matrix
Make the list comparable before judging it
Write one line for each project and describe the next meaningful result, not every small task. For example, “choose a weekend route” is a next step; “learn photography” is an open-ended project unless you define what progress would look like. Keep the entries at roughly the same level: comparing an entire home renovation with one email will distort the discussion.
For each item, note:
Current fit: How directly does this help with the priority you just named?
Value: What practical result would finishing it produce, and for whom?
Effort: What time, materials, coordination, or attention does the next stage require?
Timing: Is there a real deadline or a reason the opportunity changes if you wait?
Dependencies: Does another person, decision, or project need this first?
Evidence: What has changed since you first added it—progress, costs, interest, constraints, or circumstances?
This inventory is more useful than a long list of titles because it reveals what you are actually choosing between. Asana’s resource-allocation guide similarly starts with objectives, available resources, scope, and dependencies, and notes that priorities and resource availability can change during a project. Asana on resource allocation
Choose continue when the case still holds
Continue a project when its expected result still supports a current priority, the next step is clear, and the required effort fits alongside other commitments. “Continue” does not have to mean the original full version. You might reduce the scope, set a smaller milestone, or work on it at a slower pace while still making deliberate progress.
Check that the project has a next action you can schedule. If a project is important but has no available time, calling it “continue” without changing anything may simply leave it competing silently with the rest of the list. Decide what it will displace, how much time it gets, and what a useful next checkpoint will be.
For example, if learning a language still matters but daily study no longer fits, you could continue with two planned sessions a week and review the arrangement in a month. That example is an illustration, not evidence that a particular schedule works for everyone. Its point is to turn an abstract commitment into a bounded choice.
Choose postpone when timing, not value, is the problem
Postpone a project when its purpose still makes sense but the present moment is a poor fit: a key dependency is missing, a busy period is temporary, or another priority needs the available time first. Name the condition for resuming it. “Revisit after the move” gives you a trigger; “later” does not.
A postponement should include three details: where the project will wait, when or under what condition you will review it, and what—if anything—must be preserved in the meantime. Save a document, record the next step, or tell someone affected by the delay. If the project depends on a date or another person, check whether waiting changes its feasibility before putting it aside.
Research on goal disengagement distinguishes temporary shelving from ending a goal: both can reduce competition for limited resources, while shelving leaves open the possibility of returning. That finding does not mean postponement is always the right move; it supports treating “not now” as a distinct choice with its own terms. Research review on goal disengagement
Choose stop when the project no longer earns its place
Stop a project when its intended outcome no longer matters enough to justify the effort, its premise has changed, or the resources it needs are better used elsewhere. A project does not become a failure simply because the reason for doing it has changed. What matters for the decision is the current case for continuing, not the amount of effort already spent.
Ask: If this project appeared on my list today for the first time, knowing what I know now, would I choose it? If not, identify what would make you reconsider—if anything. Then close the loop: cancel a recurring task, tell collaborators, return borrowed materials, or save useful work before removing it from active plans. These are practical steps, not requirements for every project.
A published study of conflicting goals under time limits found that prioritizing one task over another did not automatically make participants feel less conflict or more control; the authors note that being instructed to complete both tasks may have affected the results. The useful caution is modest: choosing a priority may still involve a real trade-off. Make the choice explicit and, where possible, change expectations around the work you are setting aside. Study of prioritization under goal conflict
Check capacity before calling everything a priority
A list can contain several worthwhile projects, but your available time and other resources still constrain what can proceed at once. Estimate the effort for the next stage, not only the attractive final result. Include routine commitments and known interruptions in your capacity estimate. If a new project moves up, decide which existing item moves down; otherwise the plan quietly assumes extra capacity that may not exist.
A simple comparison grid can help organize the decision: put current fit or impact on one axis and effort on the other, then add deadlines and dependencies as notes. A high-impact, low-effort item may be an easy next step; a high-impact, high-effort project may need a smaller first milestone. A low-impact, high-effort item deserves a closer look before it takes time from work more closely tied to your priorities. Atlassian’s matrix play makes a similar distinction between must-haves, nice-to-haves, and work likely to be pushed out, while emphasizing capacity. Atlassian’s prioritization matrix
Treat the grid as a conversation with yourself, not a calculator. If two items seem equally important, compare the consequences of delay, the people who are waiting, whether the work unlocks something else, and whether the estimate is based on facts or guesswork. You can also run a short information-gathering step before committing: ask for a missing estimate, test a small version, or clarify a dependency.
Turn each choice into a visible next step
Finish the review by writing one sentence for every project:
Continue: “I will do [next action] by [date or session], then check [milestone].”
Postpone: “I will pause this until [specific date or condition], and preserve [useful next step or material].”
Stop: “I am ending this because [current reason], and I will [close any loose end].”
These statements make different decisions legible. They also help prevent a paused project from remaining mentally active as if it were still underway. If another person is affected, explain what changes and when you will update them. If circumstances shift, repeat the review; a priority list describes a current choice, not a permanent ranking.
A short worked example
Suppose your list includes finishing a photo album, refreshing a room, and preparing for a weekend trip. Your current priority is to prepare for the trip, and the available weekend time is limited. If the album matters but has no deadline, you might postpone it until a named weekend next month. If the room refresh is only a vague idea with no clear benefit or timing, you might stop treating it as an active project and keep the idea in a separate note. Trip preparation continues, with a bounded list of essential tasks.
The point is not that trip preparation should always win. Change the current priority or constraints and the decisions could change. The useful result is that each project has a reasoned status, so “doing less” describes a deliberate allocation of effort rather than an unexplained disappearance from the list.