Two requests can each be reasonable and still be impossible to complete together. A professional may be asked for a review needed by one team while another project needs their input in the same working period. Agreeing to both without changing anything can turn a priority conflict into hidden overtime, a delayed handoff or reduced attention to work that matters. The people setting the expectations may never see the choice being made on their behalf.
A useful response is to make the conflict specific. Show which commitments compete for the same time or dependency, what changes if one takes precedence and who can decide the trade-off. You may be able to rearrange work within your own authority. Where a deadline, scope or consequence belongs to somebody else's decision, a proposal helps that person choose without leaving you to absorb incompatible instructions indefinitely.
Show where the commitments collide
A priority conversation begins with the work, not a general declaration that you are busy. Identify the outputs requested, the timing each one requires and any dependency that prevents both from proceeding as planned. A conflict might concern the same specialist attention, information that will not be available in time or a decision needed before the next task can start. Naming the constraint lets other people assess it.
Distinguish a true incompatibility from several tasks that are merely demanding. Some work can be sequenced without changing a commitment. Some can be delegated or reduced in scope within existing authority. A genuine trade-off appears when meeting one expectation as stated would make another expectation less likely to be met, less useful or late for someone who depends on it. That consequence should be clear enough for the decision owner to judge.
Consider what is fixed and what is negotiable. A particular review may have an agreed control point or external dependency that cannot be moved by the contributor. Another project may have flexibility in how much analysis it needs this week. The professional should not assume that the more vocal requester has the higher priority, or that the most visible task is the most consequential. Check the reasons behind the dates and the point at which delay would affect other people's work.
Explain the condition early enough for a choice to matter. Raising a conflict after both handoffs have failed gives the manager fewer options. A timely explanation might say that the same person is needed for two outputs during the same period, and that the second output cannot be completed to the agreed scope if the first remains unchanged. This is a description of a work constraint, not a request for sympathy or an attempt to avoid responsibility.
Present options with their consequences
Once the collision is clear, give the person with authority a small set of workable choices. An option should state what would be done, what would move or narrow, and who would need to be told. “I can do both if I work harder” conceals the constraint. “If the review remains first, the project input can be an initial assessment by Thursday, with the full comparison following next week” makes a changed scope and its consequence visible. The actual timing and acceptability depend on the work; the structure of the proposal is what matters.
Imagine a specialist asked to complete an evidence review and contribute an analysis to a cross-functional project in the same window. Both requesters expect a full response before their next meetings. The specialist could explain that the review requires uninterrupted time before its decision point, while the project could either receive a narrower preliminary input or move its decision discussion. The specialist can recommend an option based on known dependencies, but the person who owns the affected commitment must agree to the changed scope or timing.
Consequences should be described honestly, including uncertainty. A shorter analysis may be enough for an early discussion but insufficient for final approval. A delayed review may affect a later decision, even if the immediate request seems small. If you do not know whether a handoff can move, find out from the recipient rather than treating an assumption as permission. Do not imply that every consequence is severe; precision is more helpful than urgency language.
The options may include help from someone else, a smaller deliverable, a changed sequence or explicit acceptance that a lower-priority task will wait. Those possibilities are not interchangeable. Another person may need briefing, a smaller deliverable may support a different decision, and a delay may affect a downstream team. Explain the relevant effect of the proposed option so that the decision is about actual work rather than a label such as “deprioritise”.
Ask the right person to decide what moves
The professional can often decide the order of tasks within agreed commitments. Changing a promise made to another team, reallocating a colleague's time or accepting a material consequence may require authority they do not hold. Clarify where your discretion ends. A proposal is useful because it brings your knowledge of the work to the decision without claiming a right to make it for everyone affected.
Bring the conflict to the person who can rank outcomes or change the relevant commitment. That may be your manager, a project owner or several people who need to agree across functions. If two requesters give incompatible directions and neither can settle the other's commitment, make the shared dependency visible to them through an appropriate route. Repeated private negotiation with each person separately can leave the conflict unresolved while making it appear that you accepted both requests.
Suggested wording might be: “The evidence review and project analysis both need my input before their next decisions. I can complete the review as agreed and provide a preliminary project assessment, or finish the full project analysis if the review date is changed by its owner. Which outcome should take priority, and who will confirm the revised expectation with the other team?” This is sample wording, not a report of an actual conversation. It shows the work, alternatives, authority and communication needed.
A decision may not arrive immediately. State when the choice is needed to protect the downstream work, continue what is safe and already agreed, and follow the legitimate escalation route if the unresolved conflict is material. Do not silently choose a high-consequence change beyond your authority. Equally, do not stop every minor task while waiting for perfect instruction when you can make a bounded, reversible choice within your role.
Carry the decision into the work
A priority decision is useful only if the affected people know what it means for their work. Confirm the agreed order, scope or date in a form suitable for the team. Identify who will tell the recipient of a changed handoff and what they can expect instead. The professional may communicate a change they have been authorised to make, while the owner remains accountable for the decision that changed a wider commitment.
A brief written recap can prevent two different interpretations from surviving the conversation. It might state which output remains on its original path, which one is now preliminary or later, the reason for that choice and when the plan will be reviewed. The record need not be elaborate. It should be clear enough that the next person does not act on the superseded expectation.
As work proceeds, check whether the assumptions behind the choice still hold. New information may reduce the work, increase its consequence or alter a dependency. A priority decision is made from the information available at the time; it does not remove the need to revisit the plan if that information changes. Communicate the change before a revised handoff becomes another missed promise.
Short periods of exceptional effort can sometimes be agreed, with their cost understood. They should not become the unspoken mechanism for making every conflicting instruction appear feasible. If a plan depends repeatedly on extra hours or reduced scrutiny that no one has acknowledged, the stated priorities and actual capacity remain misaligned. Make that pattern visible in work terms.
Address conflicts that keep returning
One collision may be solved by a sensible local choice. Recurring conflicts can indicate that several teams assume access to the same capacity, that decision points are poorly coordinated or that expectations change without earlier commitments being revisited. Keep examples of the work affected and the choices repeatedly required. This gives a manager a basis to reconsider planning, scope or decision rights rather than treating each clash as a fresh personal time-management issue.
The professional may not be able to redesign the arrangement. They can still explain the pattern: which requests repeatedly coincide, what consequence follows and where a decision is delayed because nobody clearly owns the trade-off. A manager or other authorised owner can then decide whether work should be sequenced differently, resourced differently or accepted with an explicit limit. An answer may be constrained by real organisational needs, but the constraint should be recognised.
Conflicting priorities are not resolved by pretending that all expectations can be met in full. Describe the collision early, present options with their work consequences and seek the right decision. Once the trade-off is agreed, carry it through to the people who rely on the affected outputs. That process gives the professional a defensible way to act and gives the organisation a clearer view of the choices its work requires.
