Task Prioritization Prompt

What this prompt does

When your task list has 30 items and everything feels urgent, the list itself isn't helping you. This prompt takes your raw task list, applies an impact/effort framework (or whichever you specify), and returns a prioritized order with brief reasoning for each grouping — so you can start the day with clarity instead of anxiety.

Works best as a morning or weekly planning ritual.

The prompt

[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

How to use it

1. Be honest about your #1 goal — if you write "close 3 deals" but your list is full of admin tasks, the AI will flag that gap. That's useful information.
2. Include deadlines — they're the clearest signal for the "urgent" quadrant. "Due Friday" changes the ranking more than almost anything else.
3. Include dependencies — tasks that are blocking others or that others need from you should rank higher than their individual impact suggests.
4. Review the "drop or delegate" suggestions — you might not agree with all of them, but forcing yourself to see which tasks might be cuttable is often the most valuable part.

Example output

Goal: Ship the product update by Friday
Hard deadline: Client demo Thursday 3pm
Time available: 5 focused hours

Q1 — Do First (Urgent + Important):

1. Fix the pagination bug in the demo environment — blocks everything else before Thursday [DEMO DEPENDENCY]
2. Write the demo script outline — needed by EOD for team review
3. QA the new export feature — must be done before client sees it

Q2 — Schedule (Not Urgent + Important): 4. Write up post-demo follow-up template — important for conversion, not urgent today 5. Update the product roadmap doc — strategic, do after demo

Q3 — Delegate or batch (Urgent + Not Important): 6. Respond to 3 low-priority support tickets — consider delegating; Marcus can handle support today 7. Schedule the content review meeting — 2 minutes, do between tasks, not as a task

Q4 — Drop or defer: 8. Research competitor pricing — you said "ship by Friday" is the goal; this can wait until next week

Suggested start: Task 1 (bug fix) → Task 3 (QA) → Task 2 (demo script). Block 2 hours for the bug, 1 hour for QA, 45 minutes for the script.

Variations

Weekly planning (not daily)

"Prioritize my tasks for the week. Give me: a 'Monday must-do' list (max 3), what to schedule for Tuesday–Thursday, and what to park until next week."

For project management

"I'm managing 3 projects simultaneously. Here are the active tasks across all three: [list]. Which project needs the most attention this week, and in what order should I work across them?"

For decision-making (not task lists)

See the decision matrix prompt for comparing options rather than ordering tasks.

Common pitfalls

• Don't: Run this and then ignore the Q4 list. If something is in "drop or defer," don't let it sit on your list — actively decide to park it somewhere or delete it.

• Try instead: Move deferred tasks to a someday/maybe list rather than letting them pollute your active task list.

• Don't: Re-prioritize every hour when new tasks come in. Run this once per day (morning or night for the next day), then work the list. Adding tasks as you go is fine — reprioritizing every time kills momentum.

Who uses this prompt

• Small business owners: Daily and weekly planning when wearing multiple hats
• Managers: Team task allocation and priority calls
• Freelancers: Balancing multiple client projects at once
• Teachers: Managing prep, grading, communication, and admin tasks in limited planning time