Deciding which projects to drop is a strategic skill that helps you focus your time, energy, and resources on what truly matters. This guide gives you a practical, repeatable process to evaluate your current projects, compare them fairly, and make a confident decision—without the guilt. You’ll end up with a clear list of what to keep, what to pause, and what to stop entirely.
What You’ll Need
- A list of all your current projects (even the vague ones)
- A notebook or digital document for notes
- A timer or stopwatch (optional)
- Access to your calendar or task manager to see how you actually spend time
- Honesty—this is the most important tool
Step-by-Step
- List every project you’re involved in. Write down everything from work tasks to side hustles to personal hobbies. Don’t filter yet—include the ones you’ve been ignoring and the ones that are almost done. If you have more than a dozen, group them by category (work, family, creative, etc.) to make the list manageable.
- For each project, write down why you started it. Was it to earn money, learn a skill, help someone, or because it sounded fun? Note the original purpose next to each project. This helps you see if the reason still holds.
- Track your actual time for one week. Use a timer or your calendar to record how much time you really spend on each project. Don’t rely on memory—it’s often wrong. At the end of the week, add up the hours per project. You might be surprised which ones are eating your days.
- Score each project on two scales: value and energy. Value means: does this project contribute to your goals, income, relationships, or well-being? Energy means: does it give you energy or drain you? Rate each from one (low) to five (high) for both. Write the scores next to each project.
- Identify the obvious drops. Look for projects that score low on both value and energy. These are the clear candidates. Also flag any project that has been stalled for more than a few months and that you don’t feel excited to restart—that’s a sign it’s not a priority.
- Check for sunk cost bias. Ask yourself: “If I were starting from scratch today, would I begin this project?” If the answer is no, the time you’ve already invested is a reason to stop, not to continue. Sunk costs are gone; only future value matters.
- Consider opportunity cost. For each project you’re thinking of keeping, ask: “What could I do with this time instead?” If the alternative (rest, a different project, family time) is more valuable to you, that’s a strong reason to drop the project.
- Make a keep/pause/drop list. Sort all projects into three categories: Keep (continue as is), Pause (set aside for a defined period, like three months), and Drop (end completely). Be specific about what “pause” means—write down the date you’ll revisit it.
- Set a limit on active projects. Decide how many projects you can realistically handle at once. For most people, that’s between two and five. If your “keep” list is longer, you need to move some to pause or drop.
- Communicate your decision. If other people are involved (a team, a client, a family member), tell them clearly which projects you’re dropping and why. Give them a chance to ask questions, but be firm about your final decision.
- Take action to stop. Dropping a project isn’t just mental—you need to physically stop. Cancel recurring meetings, archive the files, return borrowed items, and write a short note to yourself about why you dropped it (so you don’t restart it out of guilt).
- Review your decision after a month. Set a reminder to check in. Did you feel relief? Did you miss the project? If you feel a strong pull back, you can restart it—but only if it fits your active limit. If you don’t miss it, you know you made the right call.
Common Mistakes
- Keeping a project because you’ve already put in a lot of work. That’s sunk cost fallacy. Past effort doesn’t justify future effort if the project no longer serves you.
- Dropping projects too quickly because they’re hard. Difficulty isn’t a reason to quit—lack of value or energy is. Make sure you’re not just avoiding a challenging but important task.
- Not considering the impact on others. If you drop a project that a colleague or family member depends on, you need to communicate and give them time to adjust. Silently quitting can damage trust.
- Pausing too many projects. Pausing is a way to avoid a decision. If you pause more than half your list, you’re probably not being honest about what you really want to stop.
- Ignoring the emotional side. Dropping a project can feel like failure, especially if it was a dream or a public commitment. Acknowledge that feeling, but don’t let it override your rational analysis.
Tips
- Do this review on a regular schedule. Every quarter is a good rhythm. Projects change, and so do your goals.
- Use a simple scoring system. You don’t need a complex spreadsheet. A one-to-five scale for value and energy is enough to see patterns.
- Get an outside perspective. Ask a trusted friend, mentor, or colleague to look at your list. They can spot biases you can’t see.
- Think about your future self. Picture yourself in six months. Which projects would you be glad you dropped? Which would you regret losing? That mental image can guide you.
- Celebrate the drops. Ending a project frees up time and mental space. Acknowledge that as a win, not a loss.
Troubleshooting
- You can’t decide between two similar projects. Compare them directly on value and energy. If they’re still tied, pick the one that aligns better with your long-term goals, or the one that has a clearer end date. You can always revisit the other later.
- You feel guilty about dropping a project that others expect you to do. Remind yourself that you’re not responsible for everyone’s expectations. Communicate your decision clearly, and offer alternatives if possible (like handing it off to someone else). Guilt is a feeling, not a directive.
- You keep restarting a project you’ve dropped. This is a sign you haven’t fully accepted the decision. Write down the reasons you dropped it and read them when you feel the urge to restart. If you still want to restart after a month, you can—but only if it fits your active limit.
- You realize you’ve dropped something you actually need. That’s okay—you can pick it back up. The process isn’t permanent. If it’s important, it will come back. Just be honest about why you dropped it and what you’ll do differently this time.
- You’re overwhelmed by the number of projects. Start by dropping the easiest ones—the ones with no real value and no energy. That will reduce your list quickly. Then tackle the harder decisions one by one.
Frequently Asked Questions
- How many projects should I keep at once? It depends on your time and energy, but for most people, keeping more than five active projects leads to burnout. A good range is two to five, depending on how big they are.
- What if a project is almost finished? Should I still drop it? If it’s truly close to done (like a few days of work), it might be worth finishing to get the payoff. But if “almost done” has been true for months, that’s a sign it’s not a priority. You can drop it and come back later if needed.
- How do I deal with a project that’s required by my job? You can’t always drop work projects. But you can still use this process to prioritize—maybe you can delegate, simplify, or negotiate a deadline. If you can’t drop it, focus on the ones you can control.
- Is it better to pause or drop? Pausing is useful when you think you’ll want to return, but it’s not a permanent solution. If you pause something, set a specific date to review it. If you never want to return, drop it completely.
- What if I’m afraid of missing out on an opportunity? That fear is normal, but remember that every “yes” to one project is a “no” to another. Dropping a project frees you to pursue better opportunities later. You’re not losing—you’re making space.
- How often should I do this review? A quarterly review is a good habit, but you can do it whenever you feel overwhelmed or notice that your energy is scattered. The process works anytime.
How to Decide Which Projects to Drop