Conflicting priorities at work: ask what moves first

A priority conflict is information, not a character test

Two tasks can both be important and still compete for the same hour, reviewer, system access, or piece of equipment. Quietly accepting both does not create more capacity. It makes the tradeoff appear later as delay, reduced scope, skipped checking, or work outside the agreed plan.

Adults with ADHD may experience difficulty with planning, organization, time management, or completing large projects. But conflicting requests can also result from workload, unclear authority, changing conditions, poor communication, or several managers optimizing different outcomes. A collision between priorities is not evidence of ADHD or a personal failure.

The useful move is to make the conflict specific enough that the person with authority can decide what should change.

Check whether the work truly conflicts

1. Name the two requested outputs, not just the project names.
2. Confirm the real due dates, timezones, recipients, and meaning of complete or received.
3. Identify shared dependencies such as one reviewer, approval, data source, or tool.
4. Estimate the remaining work from the closest completed example, including review and handoff.
5. Check whether scope, sequence, owner, due date, or quality control can change under the applicable process.

Sometimes the conflict disappears when one request is only a ten-minute confirmation or when a due date was assumed rather than stated. Sometimes the check proves that both outcomes cannot be delivered safely or accurately under the current conditions. Both findings are useful.

Use a four-part priority question

• Current commitment: what you are already delivering and by when.
• New request: the additional outcome, owner, and requested timing.
• Visible consequence: what is likely to move, shrink, wait, or lose a check if both remain unchanged.
• Decision needed: who should choose the sequence, scope, owner, or date.

Keep the question about work and consequences rather than motivation. “I do not want to do both” invites a different conversation from “Both require the same reviewer Wednesday; which draft should reach them first?”

Short scripts for common collisions

• Two requests, one deadline: “I am scheduled to deliver A by Thursday. B is also requested for Thursday and uses the same review time. Which should I complete first, and what date should I confirm for the other?”
• New urgent work: “I can switch to B now. That would move the A review from Tuesday to Wednesday. Should I make that change?”
• Scope conflict: “Within the available block I can deliver the full analysis Friday, or the two confirmed figures Wednesday. Which outcome is more useful?”
• Different managers: “I have A from Priya and B from Marco for the same block. Who should make the cross-project priority decision, or should I bring both requests to the shared planning channel?”
• Unclear urgency: “What happens if this is completed tomorrow rather than today, and who needs the result?”

Adapt the wording to the organization's culture and authority structure. Do not promise a reduced control, unsafe shortcut, or rule violation as one of the options.

Offer options without taking the decision away

A useful option states the tradeoff plainly: sequence A before B; narrow an approved scope; move an agreed date; add a qualified owner; or use a different review path. The person presenting options should not imply that every option is permitted.

For legal, clinical, financial, security, regulatory, safety-critical, or formal service-level work, required deadlines and controls may not be negotiable. Escalate through the defined process rather than improvising a compromise.

If the decision belongs to someone else, label your recommendation as a recommendation. For example: “My recommendation is A first because the external filing closes Thursday; please confirm.”

Confirm the decision where work is tracked

1. Record what moves first and what happens to the other request.
2. Update the owner, scope, start date, check date, and due date affected by the choice.
3. Place the decision in the authorized project, ticket, email, or planning system.
4. Tell the people whose delivery or review expectation changed.
5. Add the next check, especially when the decision is temporary or depends on new information.

A verbal priority decision can disappear when the next urgent request arrives. A short written confirmation protects shared understanding; it is not a substitute for required approvals or formal change control.

When nobody answers

Do not invent authority you do not have. Use the established escalation route, include the decision deadline, and state the current default if a default has already been authorized. If no default exists, say that the sequence remains unconfirmed.

A concise status update can help: done—what is still on plan; next—the action you can take without the missing decision; blocked—the priority choice, owner, or approval required and when delay begins to affect delivery.

If conflicting requests are chronic rather than exceptional, collect examples of the requested outputs, available hours or resources, changed dates, skipped reviews, and escalation results. That evidence is more useful for workload planning than a general statement that everything feels urgent.

Make recurring collisions a system discussion

Work-health guidance from the US National Institute for Occupational Safety and Health identifies heavy workload, poor communication, and conflicting or uncertain expectations as working conditions that can contribute to job stress. UK Health and Safety Executive guidance similarly treats workload and work patterns as organizational demands and calls for adequate, achievable demands in relation to agreed hours.

A personal script cannot repair staffing, authority, scheduling, or resource design by itself. Repeated conflicts may need shared intake rules, one cross-project priority owner, capacity limits, review calendars, or regular workload planning. Use the organization's appropriate management, worker-representation, occupational health, HR, safety, or accommodation process for the situation.

Start with one visible collision

Choose two current commitments that compete for the same time or dependency. Write four lines: current commitment, new request, likely consequence, decision needed. Send or raise it through the normal work channel before the collision becomes a missed promise.

If planning and priority difficulties remain persistent across important areas and cause meaningful impairment, consider discussing the concrete pattern with a qualified professional. Bring examples of the decisions, workload, reminders, and support already tried rather than treating one difficult week as a diagnosis.