When two people give you contradictory instructions

The advice to “just go and clarify” skips the hard part

The standard suggestion, offered by almost everyone, is to go back and ask which instruction stands. That is roughly the right destination, but it ignores the reason people hesitate, which is that asking appears to require telling one senior person that another senior person has contradicted them. Nobody enjoys being the messenger in that exchange, and a new joiner in particular tends to conclude that silence is cheaper.

So the common move is to pick one instruction quietly, usually the one from whoever seems more powerful or more recently annoyed, and hope the discrepancy never surfaces. It surfaces. It surfaces at the point where the work is delivered, at which stage you own the choice you made in private, and the person whose instruction you dropped has a legitimate complaint that they were never told.

Most contradictions are inherited rather than personal

It helps enormously to understand where conflicting direction comes from, because it is rarely carelessness. Two people give you incompatible instructions when they are being measured on incompatible things, when they hold different information, or when a decision was made somewhere above them and only one of them has heard about it. In each case the contradiction existed before you arrived and would exist if you left.

This matters because it changes the shape of the conversation you need to have. You are not adjudicating between two people. You are reporting that a decision has not actually been made, which is a normal thing to happen in any organisation with more than a handful of people in it, and which somebody with the authority to settle it needs to know about.

Put the conflict in writing before you put it in a room

The lowest-friction route is usually a short written note to both people at once, stating both positions plainly and without adjectives. Something close to: I have been asked for the report on Tuesday with the full breakdown, and separately asked to keep it to a summary for Thursday. I can do either. Which would you prefer?

That format does several things at once. It removes any suggestion that somebody made an error, because it does not say so. It makes the incompatibility visible to both parties simultaneously, so neither hears about it secondhand. And it presents the question as a choice between two workable outcomes rather than as an obstacle you are handing back. Most of the time somebody replies within the hour and the matter is closed.

Keep it factual and keep it short. The temptation is to explain how the confusion arose, or to signal how reasonable you are being about it, and both make the note read as a grievance. The version that works is almost boring.

If one of them is your manager, they are still the route

Where a direct manager and someone else disagree, your manager is normally the person who resolves it, because deciding what their team spends time on is a substantial part of what they are there for. Going around them to comply with a more senior request is a common early mistake, and it is one that damages trust in a way that is slow to repair.

That does not mean refusing the senior person. It means saying, without drama, that you will check with your manager on sequencing and come back — which is a normal sentence that almost nobody objects to, and which quietly relocates the conflict to the level where it belongs. If your manager consistently fails to resolve these, that itself is information about how the place is run.

When it happens every week, the structure is the cause

One contradiction is an event. A pattern of them usually means you sit underneath two lines of authority that were never reconciled, which happens routinely in matrix arrangements, in teams shared between departments, and wherever a project lead and a line manager both believe they set your priorities. No amount of individual clarification fixes a structure, though it will keep you functional inside one.

The realistic response is to make the trade-off visible on a repeating basis rather than case by case. A regular note listing what you are working on, in order, sent to both parties, converts a series of private collisions into a standing question about priority that they can argue out between themselves. Some organisations will sort this properly and give you a single point of direction. Others will leave it unresolved for years, and if that is where you are, it is worth knowing that the exhaustion you feel is a design fault rather than a personal shortcoming.