Prioritization starts with a constraint
Prioritization means choosing the order of work and what not to do yet. Without limits on time, resources or attention, ranking tasks changes little.
In our illustrative example, a studio manager has four things to do today: reply to a client, fix a problem with an inquiry form, explore a new visual theme and prepare an upcoming proposal. All four may be useful, but a polished matrix cannot turn two free hours into eight. First, understand the consequences of delay and the capacity available.
Do not start with your favorite method. Planning a personal day calls for different questions from selecting a product initiative. The tool should support the decision at hand, rather than force every task through the same scoring system.
- Constraint
How much time and which resources are actually available?
- Consequences
What changes if each item is postponed?
- Choice
What will we take on now, what will wait, and what needs agreement?
Which method fits the situation?
| Situation | Useful approach | Limitation |
|---|---|---|
| Planning a personal day | Urgency and importance | Does not replace checking available time |
| Comparing several similar initiatives | Impact versus effort | Estimates need a basis |
| Selecting product candidates | RICE, when suitable data is available | A formula does not make a score true |
| An external commitment exists | Check the deadline and consequences of missing it | A low score does not silently cancel a promise |
The Eisenhower matrix helps distinguish importance from urgency; the blog already covers it in detail. Here, the question is broader: how should you compare the work? RICE can help when you can make meaningful estimates of reach, impact, confidence and effort. If the data is missing, first state your assumptions.
Avoid comparing incompatible estimates with excessive precision. A hypothetical difference between 7.2 and 7.3 should not decide an initiative's fate when the inputs are based on intuition.
Working through an illustrative list
- Inquiry form error
Disrupts a current inquiry. Establish the scope and make the necessary fix or hand it to someone who can.
- New visual theme
May be useful later, but does not resolve the observed problem now. Keep it as a candidate.
Replying to the client may take little time and unblock someone else. That is a reason to consider it separately, even if it is not the largest item. Preparing the proposal may have an external deadline: reserve capacity before it or agree on a postponement in advance.
The priorities become a concrete plan: investigate the error, send the necessary reply and reserve a manageable block for the proposal. The visual theme stays in the queue. This is not a universal order for every studio; it follows from the conditions in the example.
Accounting for uncertainty and dependencies
Sometimes testing an assumption is more useful than choosing a large piece of work on the basis of a doubtful estimate. A short conversation may reveal that the expected benefit does not exist or that the solution is much harder. That investigation also competes for time and needs a clear output.
- Separate commitments from optional candidates.
- Clarify the consequences of delay and dependencies on other work.
- State the assumptions behind the estimated benefit.
- Choose a comparison method sufficient for the situation.
- Agree on postponements when the choice affects other people.
A dependency can make a small step a priority because it unblocks several people. But do not treat every request as urgent just because a colleague sent it. Find out exactly what has stopped and when the answer is needed.
RICE with two candidates: calculate and test the assumptions
RICE compares reach, impact, confidence and effort: reach × impact × confidence / effort. Use the same reach period and effort units for every candidate. Confidence in the calculation below is a fraction: 80% is 0.8, not 80.
Illustrative initiative A improves the explanation of a session format. Reach is 300 people per month, impact is 1, confidence is 0.8 and effort is 2 person-weeks. Score: 300 × 1 × 0.8 / 2 = 120. Initiative B is a new report: reach 80, impact 2, confidence 0.5 and effort 1. Score: 80 × 2 × 0.5 / 1 = 80. These figures are invented to explain the formula; they are not Sinqly measurements.
| Candidate | Initial score | After refining effort |
|---|---|---|
| A: format explanation | 120 with effort of 2 | 60 with effort of 4 |
| B: report | 80 with effort of 1 | 80, unchanged |
Under the initial assumptions, A ranks higher. But if its effort turns out to be 4 person-weeks, its score falls to 60 and the order reverses. Discussing the basis of an estimate matters more than a neatly sorted list. Investigating an expensive unknown may be more useful than debating decimal points of impact.
Checking commitments remains a separate responsibility. Fixing a serious defect, addressing safety or meeting an agreed deadline cannot automatically be postponed because of a low score. RICE supports discussion of comparable initiatives; it does not remove accountability.
What to do when the formula has no data
For a small personal list, first identify external commitments and the consequences of delay, then compare each item's contribution to an important outcome and its realistic cost. Do not turn vague impressions into precise numbers simply because a spreadsheet makes it possible.
If two options are hard to compare, identify the decisive uncertainty. For example, you may not know whether people struggle to choose a session format. The next step is to examine inquiries or talk to users, rather than start development immediately. Research also competes for time, so bound it with a specific question and output.
Finish prioritizing by explicitly leaving some work out of the current period. If everything remains “important and urgent,” the method has not helped you choose. State when you will return to deferred work and what new evidence could change the decision.
Reserve time for the chosen priority
Start with one task: “Clarify how the form error affects current inquiries.” Record the expected output in its description: which scenario is broken, who it affects and what immediate action is needed. You do not have to copy the whole article into the application; keep what will help you do the work.
After investigating, review the available time. If the fix displaces promised work, agree on the change instead of simply moving dates in your own list.
- Create a task with a specific action in its title.
- Add the completion conditions and necessary context to the description.
- Choose a day and check whether the work fits alongside your other commitments.
Signing up for Sinqly is free. You can also work through the article's example in an ordinary document; the app helps you return to the actions you chose.
Reviewing priorities without constant churn
Change the order when significant new facts appear: an external commitment, a confirmed problem or a change in resources. You do not need to recalculate the entire list after every notification. Separately agree on how incoming requests enter the plan.
At the end of the period, compare your choices with the results. What proved useful? Which estimates were weak? Which postponement had consequences you missed? These observations improve future decisions more than the search for a perfect universal formula.
A priority combines an action with the cost of leaving an alternative undone. The order of a list matters when it changes real commitments and the use of time.
More questions to clarify
Can we prioritize without scores?
Yes. For a small list, comparing consequences, deadlines and available resources is often enough. A formula is useful only when it supports a reasoned choice.
What if everything is urgent?
Clarify actual deadlines and consequences, then show the resource constraint. Incompatible promises require a decision or renegotiation.
Do we need to use the same matrix every day?
No. Choose an approach that fits the decision. Clear reasoning matters more than loyalty to one tool.
Was this helpful?
Rate the article and tell us what was missing. Your feedback goes to the Sinqly team and will not be published on the site.
Sources and notes
- Atlassian: how to prioritize tasks
- Intercom: RICE, explained by its creators
- The suggested process reflects editorial practice; it does not promise identical results for everyone.



