The best prioritisation framework for multiple projects ranks whole projects against each other before it ranks any tasks. In practice, you cap your active projects at around three, choose them against your goals for the quarter, park the rest on a Someday/Maybe list, and only then use a task-level tool such as the Eisenhower Matrix to run each day.
You probably know the feeling. You have a website rebuild, a new hire to onboard, a pricing change, a partnership proposal and two client projects with deadlines. Every one of them matters. Each morning you pick the loudest one, make some progress, and by Friday all six have moved a little while none of them has finished.
That pattern usually comes from using a tool built for sorting tasks to settle a question about projects. You are working hard and making sensible choices with the wrong tool. In this piece you will see how the common frameworks compare on this specific job, where each one fits, and a five-step way to stack them so your projects stop competing for the same hours.
Why task frameworks struggle with competing projects
Most well-known frameworks were designed to sort a list of items of roughly similar size. The Eisenhower Matrix asks whether each item is urgent and important. MoSCoW sorts features for one release. RICE scores ideas for one product team.
When you drop six projects into any of these, every project comes out as important. Most come out as urgent too, because a project that has sat untouched for a fortnight starts to feel urgent whether it is or not. You end up with one quadrant holding everything, which is exactly where you started.
The question you need answered first is a different one: which of these projects get your time this quarter, and which wait? Once you have settled that, task frameworks work well again, because they are sorting work inside a smaller set you chose on purpose. With that in mind, here is how each option handles the job.
The main prioritisation frameworks compared
Eisenhower Matrix
The matrix is excellent for daily and weekly task decisions. It is weak at choosing between projects, since nearly every live project scores as important. Use it once your project list is short. The guide to the Eisenhower Matrix for business owners shows how to run it on a single week.
MoSCoW
Must have, Should have, Could have, Won't have. MoSCoW was built for scoping one project or release, and it is very good at cutting scope inside a project. Between projects, the most useful part is the Won't column, because it makes you name what you are leaving alone.
RICE and ICE scoring
RICE scores Reach, Impact, Confidence and Effort, and ICE drops Reach. Both give each option a number, which helps when you have many similar ideas, such as a backlog of marketing experiments. The scores look precise while resting on guesses, and you will find it awkward to compare a hiring project with a sales campaign on one scale. Use them to rank like with like.
Big Rocks (Rocks and MITs)
You choose a small number of priorities first and fit the smaller work around them. This works at project level, which makes it the closest fit for someone juggling too many projects. It says less about how to pick the rocks themselves. You can read more in how Rocks or MITs can transform your productivity.
The 3-3-3 rule
This is a daily structure: three hours on one important project, three shorter tasks and three maintenance jobs. It protects your focus on one project per day. It assumes you already know which project deserves those three hours. The 3-3-3 rule for productivity explains how to fill each part.
GTD Horizons of Focus
The Horizons link your daily actions to projects, areas of responsibility, goals and vision. It is the most complete option for checking whether a project serves a real goal, and it can feel heavy when you are already stretched. GTD Horizons of Focus walks through each level.
Side by side
| Framework | What it ranks | Best used for | Main limit |
|---|---|---|---|
| Eisenhower Matrix | Tasks | Daily and weekly decisions | Most projects score as important |
| MoSCoW | Features or scope | Cutting scope inside one project | Built for a single release |
| RICE / ICE | Similar ideas | Ranking a backlog of experiments | Scores rest on guesses |
| Big Rocks | Projects and priorities | Choosing what gets protected time | Light on how to choose |
| 3-3-3 rule | One day | Protecting focus on one project | Needs the project chosen already |
| Horizons of Focus | Projects against goals | Checking a project serves a goal | Takes time to set up |
If you want a wider set of methods for spotting valuable work, the guide on how to identify high-leverage work covers more of them. No single tool here decides which projects get your time, so the method below combines two or three of them.
How to prioritise competing projects: a five-step stack
- Write every open project on one list, including the ones you have only promised yourself.
- Ask two questions of each project: does it move a goal for this quarter, and what actually happens if it waits three months?
- Choose a maximum of three active projects and move every other project to your Someday/Maybe list with a date to look at it again.
- For each active project, write the single next action and schedule that work each day with the Eisenhower Matrix or the 3-3-3 rule.
- Review the list every week and bring a new project in only when an active one finishes or you consciously drop it.
Step one matters more than it looks. A GTD projects list often reveals a few commitments you had forgotten were still taking up your attention.
You will probably find step three the hardest. Moving a project you care about to the GTD Someday/Maybe list can feel like giving up on it. When I had too many projects running, the parked ones were the reason the active ones finally finished, because they stopped taking a slice of every day. A parked project with a review date is a decision you can revisit, and you lose nothing by writing it down.
Step five is how you keep the list current. The GTD weekly review is where you check whether your three active projects are still the right three, and where a finished project frees a slot for the next one.
Frequently asked questions
What is the best prioritisation framework for multiple projects?
Use a project-level method such as Big Rocks to choose a maximum of three active projects against your quarterly goals. Park the rest on a Someday/Maybe list with a review date. Then use a task-level tool such as the Eisenhower Matrix or the 3-3-3 rule to decide what you do each day on those chosen projects.
Is the Eisenhower Matrix good for prioritising projects?
It works well for tasks and less well for whole projects. Most live projects score as both important and urgent, so they all land in the same quadrant. Choose your active projects first with a project-level method, then use the matrix to sort the tasks inside them during your daily and weekly planning.
How many projects should I work on at once?
Many business owners find that around three active projects is a workable limit, though the right number depends on the size of each project and your other responsibilities. The useful habit is setting a cap at all, so a new project only starts when an active one finishes or is consciously dropped.
What is the difference between RICE and MoSCoW?
RICE gives each idea a score based on reach, impact, confidence and effort, which helps you rank a long list of similar ideas. MoSCoW sorts items into must, should, could and won't, which helps you cut scope inside one project. Neither was designed to rank very different projects against each other.
Choosing the framework that fits your week
The core idea is simple to state and harder to practise: rank your projects before you rank your tasks. Task frameworks such as Eisenhower, MoSCoW and RICE are useful, and they work best once you have chosen a short list of projects to apply them to. Big Rocks and the Horizons of Focus help you make that choice, and a weekly review keeps it current.
Once you work this way, you can see at a glance which three projects get your time, and the rest wait on a list where you can find them again.
The NP System covers the project and daily layers of this stack, including weekly rocks and regular reviews. It does not include a scoring model like RICE, so if you need to rank a long backlog of similar ideas, use RICE for that part. If you want to see how the whole system fits together, the free NP System course walks you through it from capture to weekly planning.
