A practical way to compare consequences, deadlines, dependencies and capacity, with a real Cue walkthrough
Compare consequences, deadlines, dependencies and capacity when every task feels urgent. Includes reusable prompts and a real Cue walkthrough with saved-task evidence, refusals and a text-only ranking.
The four questions that create an order
Write the consequence beside each task rather than relying on the word "urgent". Then work through these questions: what happens if it slips, when is the last useful moment to finish it, what depends on it, and how much time can you actually give it?
- What happens if I do not do this? Name the concrete cost: lost money, blocked work, a missed commitment, a delayed decision or an awkward follow-up.
- When is the last useful time to finish it? "Before Friday" means earlier than Friday if Friday is when the consequence arrives. A due date can be a hard stop, a useful target or a guess.
- What depends on it? A task can move up when another person, decision or piece of work is waiting on it. A task can move down when the dependency is unclear.
- What fits the time I have? A priority list that cannot fit into the available hours is a wish list. Keep the first task specific, then choose a defer list with dates for revisiting it.
The order can change after one clarification. "Renew the insurance" may be first if work stops at expiry. "Book the flights" may be first if early-bird pricing closes tonight. "Finish the proposal" may be first if it is the only item someone is waiting on tomorrow morning. The point is to make those consequences visible.
A simple method for a crowded day
1. Put every open loop in one place
Capture the tasks without ranking them. Include the deadline as you currently understand it, the consequence of missing it and any constraint that makes it different from ordinary work. Add your available hours. Four hours of focused work is a different constraint from four hours between appointments.
2. Separate hard stops from loud requests
- Hard stop: the cost arrives at a fixed time or the opportunity closes.
- Dependency: another task or person cannot move until this is done.
- Capacity fit: work that can be completed in the time available.
- Request: something someone wants soon, with no stated consequence yet.
The labels are a way to ask better questions. A request can become a hard stop when you learn what is at stake. A hard stop can move down when there is a safe fallback. Keep the uncertainty visible.
3. Choose one first action
Choose the smallest action that reduces the largest consequence. "Renew the insurance" may mean opening the renewal link, checking the premium or submitting the form. "Finish the proposal" may mean writing the missing pricing section. A first action should fit in the next available block and leave a clear stopping point.
4. Make a defer list
For each task you are moving out, write when you will revisit it and what would make it move up. "Reply to recruiter — Friday after the proposal; move up if the role closes today" is more useful than "later". Deferral is a decision with a review point.
5. Ask for the missing facts
If two tasks could reasonably come first, ask one question that separates them. Useful questions include: "Does work stop at expiry, or can I operate while the renewal is processing?", "What time does the early-bird price close?", and "What is the consequence if the proposal goes out tomorrow morning instead of today?"
Prompts you can reuse
For a crowded list, give the assistant the constraints that shape the decision:
Here are my open tasks: [paste the list]. I have [number] hours available tomorrow. For each item, compare the consequence of missing it, the last useful time to finish it, what depends on it and how certain the deadline is. Give me one first action, a defer list with review dates and the questions that would change the order. Do not create or reschedule anything without asking me first.
For a list that contains vague urgency:
For each task below, replace "urgent" with the concrete consequence of waiting. If the consequence is unknown, say what I need to clarify. Keep the deadline and consequence separate.
Before accepting a proposed order:
What assumptions are driving this order? Show me the item that would move first if each assumption changed. Keep this as advice until I confirm any task changes.
A worked example, run in Cue
The example uses six deliberately competing fictional tasks. The scenario gives the assistant real trade-offs: a next-day deliverable, a work dependency, a financial deadline and three requests with different levels of consequence. The names and details are fictional. The screenshots show real Cue screens from this example.
- Client proposal final draft, due tomorrow at 5 PM.
- Professional insurance renewal, expiring Saturday and described as blocking work.
- Performance review self-assessment, due Monday.
- Reply to a recruiter who has emailed twice.
- Book conference flights before an early-bird deadline on Friday.
- Chase a vendor about an invoice they queried.
Cue's proposal card showed all six items. Auto was off, so the card still required an explicit confirmation.
What the first run showed
In an earlier run, Cue saved the six tasks with the same priority. Cue had accepted the list, but accepting a list is not the same as deciding what matters most.
The proposed times made that visible. Cue put the recruiter reply at 10:00, the flights at 11:00 and the vendor chase at 12:00, ahead of the client proposal at 3:00 PM even though the proposal was due the next day. It scheduled the insurance renewal at 10:00 AM on Saturday, the day it was described as expiring. Those times were a useful draft to question, and a consequence-based order needed another pass.
That result suggests a practical check: compare the proposed times with the consequence you supplied. If everything still carries the same weight, ask for a ranking before you accept the plan.
The prioritization request
All six feel urgent and I have about four hours tomorrow. Rank them by what actually happens if I do not do it, not by how loud it is. Tell me what to do first, what to defer, and anything I should clarify before I start.
The request asks for an order, a defer list and clarifications while keeping actions behind the confirmation step.
In a later attempt, task creation failed in this test, so the ranking below is advice for the six-item scenario rather than a rewrite of saved tasks. Cue returned the same message after each creation attempt: "I couldn't complete that response safely. Please try again."
What Cue returned
Here’s a consequence‑based ranking for tomorrow: 1. Professional insurance renewal – Without it you can’t legally work, so it’s the highest priority. 2. Conference flights – Early‑bird pricing ends Friday; missing it costs money and may delay travel plans. 3. Client proposal final draft – Due tomorrow 5 PM; a late submission could hurt the deal and your reputation. 4. Performance review self‑assessment – Due Monday; a late review delays your feedback cycle and potential raises. 5. Reply to recruiter – They’ve emailed twice; a quick reply keeps the conversation alive and shows professionalism. 6. Vendor invoice chase – Important, but can wait until after the more time‑critical items. What to do first: renew the insurance, book the flights, then finish the proposal draft. What to defer: the self‑assessment, recruiter reply, and vendor chase until after the top three. Clarifications needed: • Do you have the insurance renewal link or need help finding it? • Is the flight booking link already open, or should I locate the early‑bird offer? • For the proposal, do you need a draft review or just the final send‑out? • Any specific vendor details (contact, invoice number) that could speed the chase? Let me know if you’d like me to create these tasks or adjust the order.
Cue then said to renew the insurance, book the flights and finish the proposal first. It deferred the self-assessment, recruiter reply and vendor chase until after those three. It asked four questions: whether the insurance renewal link was available, whether the flight booking link was already open, whether the proposal needed a review or only a final send-out, and which vendor details could speed the chase.
The response is a readable ranking draft. It has not changed a task list.
The lower part asks for the facts that could change the order.
The answer is useful as a starting point because it states why each item moved and asks for missing facts. One sentence needs correction: the prompt said the insurance was a work dependency, while Cue strengthened that into "you can’t legally work". The capture does not establish a legal requirement. Keep the user's wording — work may be blocked until the renewal is handled — until the legal or operational detail is verified.
The three suggested first tasks may also exceed four hours. The prioritization prompt supplied available time but no task durations, and the response did not estimate them. Ask for durations and the latest useful time for each item before treating the order as a workable plan.
What the method gets right, and where to be careful
The method keeps four decisions separate: consequence, deadline, dependency and capacity. That prevents "tomorrow" from becoming the only signal. It also turns deferral into a visible choice and uses clarifying questions when the order depends on a fact you do not know.
Research provides useful background without proving that an AI assistant will make the decision for you. Macan's time-management process model tested goals and priorities, planning mechanics and perceived control as related parts of time management. Gollwitzer and Sheeran's review examined implementation intentions, the practice of linking an action to a situation or trigger. Those findings support writing a specific next action and time; they do not validate Cue's particular ranking or prove that a task app improves follow-through.
Advice and task changes are separate steps. A written answer does not show that a task or schedule changed. When an action card appears, review it, confirm it explicitly and check the resulting task list.
Limitations worth knowing
- This is one synthetic scenario. It demonstrates a six-item trade-off with fictional details. It does not show how Cue handles your deadlines, calendar permissions, connected services or real work.
- Proposed changes need review. Keep confirmation on and check the task list after any proposed change.
- The order is conditional. Insurance first makes sense if work truly stops at expiry. Flights first makes sense if the price closes before the next available booking window. The three first tasks may exceed four hours without durations, so confirm the consequence and capacity before acting.
Troubleshooting
- Everything still has the same priority. Ask for the consequence and deadline beside each item, then ask for one first action and a defer list. Do not assume the task creator has ranked the list.
- It chose the wrong first task. Ask which assumption drives the order and give the missing fact. For example, state when the early-bird price closes or whether work can continue while an insurance renewal is processing.
- It says it will create tasks, but I cannot find them. Look for a proposal card and the explicit confirmation action, then check the task list. A promise to create is not proof that anything changed.
The takeaway
Prioritization is a consequence decision under a capacity constraint. Put the consequence, useful deadline, dependency and available time beside each task. Choose one small first action, defer the rest to named review points, and ask for facts that could change the order. Cue can turn that structure into a readable draft, while the proposal card and task list give you two places to check what actually changed.
If you want to try the method, open Cue in your browser or get the app , then use the prompt above with your own list. Keep task creation behind your confirmation and check the saved result.