Assistant Work Request Priorities: A Simple Rule for Competing Deadlines

As a founder or executive, your time is your most finite resource. You're constantly bombarded with requests, decisions, and competing demands, often leading to a sense of being perpetually reactive. This challenge intensifies when you bring on an assistant to offload recurring administrative and operational tasks, only to find yourself still spending precious minutes clarifying which task takes precedence.

The core issue isn't a lack of effort but often a lack of a clear, objective framework for prioritization. Without one, an assistant is left to guess, rely on who asked most recently or loudest, or interrupt you for guidance. This article introduces a simple, actionable rule for prioritizing assistant work requests, designed to remove guesswork, reduce interruptions, and empower your assistant to manage their workload effectively.

The Problem with Ad Hoc Prioritization

Many executives operate with an informal prioritization system, or no system at all. A task comes in, it feels important, and it gets assigned. Then another task arrives, perhaps from a different department or a different executive, and suddenly the assistant has two "urgent" items. This common scenario leads to several negative outcomes.

First, it creates mental overhead for you. Every time an assistant asks, "Which one should I do first?", you're pulled away from strategic work to re-evaluate. This constant context switching erodes focus and productivity. Second, it creates inefficiency and stress for your assistant. Without clear guidance, they spend time deliberating, potentially working on lower-priority items while more impactful tasks languish. Third, it can lead to a "squeaky wheel gets the grease" mentality, where the person who follows up most aggressively, rather than the task with the highest objective value, dictates the assistant's workflow. This erodes trust and visibility, making it difficult to understand true progress.

Introducing the Work Request Priority Rule

To combat ad hoc prioritization, we propose a structured approach built around a simple rule and five key fields. This rule empowers your assistant to make informed decisions autonomously, aligning their work with your strategic objectives without constant oversight. The rule is as follows: Prioritize tasks that have the highest business impact, the nearest hard deadline, critical dependencies, and lower effort, unless explicitly overridden by the designated owner.

This rule isn't just a suggestion; it's a decision-making algorithm for your assistant. By evaluating each incoming task against these five fields, they gain a consistent method for sequencing work. This clarity reduces friction, streamlines operations, and frees up your time for executive-level responsibilities, knowing that the most important work is consistently being addressed.

Understanding the Priority Fields

Each of the five fields plays a distinct role in determining a task's true priority. It's essential to define these clearly with your assistant and any other stakeholders who will be requesting work.

Business Impact

This field assesses how the completion of a task directly or indirectly contributes to your organization's core objectives. It's not about how you feel about a task, but its quantifiable or qualitative value to the business.

• High: Directly affects revenue generation, client retention, regulatory compliance, or critical strategic initiatives. Failure to complete this task has severe consequences (e.g., missed sales opportunity, legal penalty, major system downtime).
• Medium: Supports key operational processes, improves efficiency, or contributes to important but not mission-critical projects. Failure has noticeable, but not catastrophic, consequences (e.g., delayed report, minor process bottleneck).
• Low: General administrative tasks, long-term planning support, or internal improvement initiatives with no immediate business impact. Failure has minimal or easily recoverable consequences (e.g., tidying a digital file system, researching a future travel option).

Dependency

This field identifies whether other critical tasks, projects, or people are waiting on the completion of this specific item. A task with a dependency essentially creates a bottleneck if not addressed promptly.

• Yes: One or more critical tasks or stakeholders are blocked until this task is completed. This often means delays propagate through a system.
• No: The task can proceed independently, without holding up other immediate workstreams.

Deadline: This is the firm date or time by which a task must be completed. It's vital to differentiate between a "wish list" date and an actual, hard deadline.

• Hard: A fixed, non-negotiable date (e.g., regulatory filing deadline, client presentation, payroll submission). Missing this has immediate, serious consequences.
• Soft: A target date that, if missed, causes inconvenience but no immediate, severe harm (e.g., internal report, preliminary research for a future project).
• Flexible: No specific deadline; can be completed when time allows around higher priorities.

Effort: This estimates the time and resources required to complete the task. While not a direct priority driver, it's a critical secondary factor, especially for "quick wins" that can clear the deck.

• Short: Less than 1 hour.
• Medium: 1-4 hours.
• Long: More than 4 hours.

Override Owner: This field identifies the specific individual or role with the authority to explicitly re-prioritize a task, even if it goes against the established rule. This is a vital control mechanism, ensuring that genuine emergencies or shifts in strategy can be accommodated without breaking the system. It should be used sparingly and only by the designated owner.

Here's an example of how the rule would apply:

Setting Up Your Priority System

Implementing this system requires clear communication and a little setup. The initial investment will pay dividends in reduced stress and improved efficiency.

1. Define Your Scales: Work with your assistant to clearly define what "High," "Medium," and "Low" mean for your business impact. Do the same for "Hard," "Soft," and "Flexible" deadlines, and what constitutes "Short," "Medium," and "Long" effort. Ensure these definitions are documented and easily accessible.
2. Identify Override Owners: Determine who has the authority to issue an override. Ideally, this should be a very limited group (e.g., the CEO, President, or specific department heads for their immediate team's tasks). Emphasize that overrides should be rare exceptions, not the norm.
3. Choose a Tool: A simple shared spreadsheet can work perfectly to start. Each row is a task, and columns are the five priority fields. More sophisticated task management systems (e.g., Asana, Trello, Monday.com) can also be configured to include these fields. The key is visibility and consistency.
4. Communicate the Rule: Introduce this rule to your assistant and anyone else who regularly delegates tasks to them. Explain why it's being implemented , to empower the assistant, reduce interruptions, and ensure critical work gets done.
5. Training and Practice: Walk through several real-world examples with your assistant, applying the rule. Encourage them to ask questions and challenge initial assumptions. This builds confidence and competence. For more guidance on this, consider reading our article on how to delegate effectively.
6. Regular Review: Periodically review the priority list with your assistant. This helps refine the definitions, addresses any misunderstandings, and reinforces the system. It's also an excellent opportunity to discuss how tasks are flowing and identify any bottlenecks. For insights on optimizing this collaboration, review our advice on managing a virtual assistant.

Common Failure Modes and Tradeoffs

No system is perfect, and this priority rule is not immune to misuse or challenges. Being aware of these can help you mitigate them.

Failure Modes:

• "Everything is High Impact/Hard Deadline": Executives and managers, under pressure, may default to labeling all requests as urgent. This defeats the purpose of the system. It requires discipline from all requesters to be honest about a task's true impact and deadline.
• Bypassing the System: If executives continue to give verbal, ad hoc "urgent" requests outside the system, the assistant will be forced back into guesswork. All requests for work should ideally go through the defined process.
• Lack of Clarity in Definitions: If "High Impact" is too vague, or "Hard Deadline" isn't truly hard, the system breaks down. Regular calibration and concrete examples are essential.
• Fear of Saying "No" or Reprioritizing: An assistant might hesitate to follow the rule if they fear reprisal for not immediately dropping everything for an executive's new request. Empower them to politely refer requesters back to the system.

Tradeoffs:

• Initial Overhead: There is an upfront investment in defining the fields, training, and setting up the system. However, this is quickly recouped through long-term efficiency gains.
• Potential for Rigidity: If the system is too strictly enforced without allowing for legitimate overrides or periodic review, it can become inflexible. The override owner field is designed to manage this, but it must be used judiciously.
• Requires Discipline: For the system to work, everyone involved,from the executive delegating to the assistant receiving,must commit to using it consistently. This system is a powerful tool for maintaining business continuity and operational resilience, allowing critical tasks to be identified and acted upon even in dynamic environments. Learn more about planning for such resilience at official guidance.

A free consultation can help you identify the first responsibility to transfer and define the controls that keep it on track. Book a free consultation.

FAQ

Q: What if everything seems high impact? A: This is a common challenge. It suggests you need to refine your definition of "High Impact" to create clearer distinctions. Work with your assistant to identify what tasks would truly cause significant harm to the business if not completed, and which would merely be inconvenient or delay non-critical progress. Consider a scale of 1-10 if High/Medium/Low isn't granular enough, and assign specific criteria to each number.

Q: How often should we review priorities? A: A daily quick check-in (10-15 minutes) with your assistant can be effective, especially if new requests are frequent. A deeper weekly review (30 minutes) is advisable to assess overall workload, upcoming deadlines, and to address any recurring issues with prioritization. This also serves as a valuable coaching opportunity.

Q: Can different executives have different priority rules? A: Ideally, the core priority rule should be consistent across the organization for any shared assistant. However, individual executives might have specific nuances in how they define "Business Impact" for their specific area. These should be clearly communicated to the assistant and documented, making sure they do not conflict with the overall framework. If an assistant serves multiple executives, the "Override Owner" field becomes even more important.

Q: What if a new request comes in that's more urgent than everything else? A: This is precisely why the "Override Owner" field exists. If a new request genuinely has a higher business impact and an immediate hard deadline that supersedes all other tasks, the designated override owner should explicitly state this. This signals to the assistant that they should reprioritize, and ideally, the override owner understands the downstream impact of their decision on other tasks. The system is designed to handle this, but it requires the override to be explicit and intentional, not a casual request.

Frequently asked questions

Who should maintain the assistant work request priorities?

The assistant who works closest to the process should maintain the working details. The founder or accountable leader should approve authority limits, sensitive access, and exceptions with material business impact.

How much detail belongs in the first version?

Start with one responsibility, the fields in the article's table, and one normal example. Add detail only when a real case exposes an unclear rule or missing input.

How often should the assistant work request priorities be reviewed?

Review it weekly during a new handoff. Once the process is stable, review it when an exception occurs, an owner changes, or the underlying workflow changes.

What should happen when the assistant finds an unlisted case?

The assistant should record the facts, suggest a next action, and use the agreed escalation route. After the decision, add the case as an example if it is likely to happen again.