Boss Keeps Changing Expectations? Get Priorities Agreed

1. What Should You Do When Your Boss Keeps Changing Expectations?

If your boss keeps changing expectations, clarify what the new request replaces and ask your manager to choose a workable priority, scope and deadline.

The difficult part is often the unfinished work left behind. A request that sounds small in a meeting can displace an afternoon of analysis or depend on someone who is unavailable. Make that consequence visible before promising delivery.

You might say: “I can move this ahead of the report. Should I move the report deadline to Thursday, or reduce its scope?” That gives your manager a decision they can act on. “I’ll try to do everything” leaves the conflict unresolved.

Changing instructions alone cannot tell you whether your boss wants you gone, wants you to quit your job, or is testing you. Address the observable problem first: what work is now expected, and what will make it achievable?

My recommendation is to keep the process modest: one shared assignment record and a short conversation when a change affects delivery. The record should help both people make decisions, without becoming another substantial task.

2. What Is an Example of Unrealistic Expectations at Work?

An unrealistic expectation is substantially expanding an assignment while keeping the original deadline when the available time, resources or dependencies cannot support the extra work.

Picture it: in this hypothetical example, an employee is preparing a short report due Friday. On Wednesday, their manager adds customer interviews and a presentation. The report is partly drafted, but the interviewees have not been contacted. Finishing now depends on other people’s availability as well as the employee’s effort.

The employee checks the remaining work and discovers that the earliest suitable interview slot is Monday. Instead of offering a vague objection, they explain the constraint: “The existing data can support a short report Friday. The interviews can inform a presentation Tuesday. If the interviews must be in the report, its deadline needs to move.”

The manager chooses the short Friday report and Tuesday presentation. That decision changes the assignment from an impossible bundle into two deliverables with different purposes. Friday’s report must clearly identify the questions the interviews have yet to answer.

A stretch assignment can still be demanding. What makes it workable is room to learn, access to necessary support and a shared definition of acceptable completion. Requiring exhaustive analysis and an immediate answer leaves a conflict that effort alone cannot resolve.

3. Why Your Boss Keeps Changing Expectations

Expectations may change because new information arrives, stakeholders disagree or planning is poor. The useful distinction is how your manager handles the consequences.

• Changing priorities: Your manager explains the new need and accepts that other work may move. Focus on sequencing and dependencies.
• Poor management: Requests remain vague, different stakeholders issue conflicting instructions, or every task stays urgent. Ask who has authority to settle priorities and approve the finished work.
• Harmful conduct or possible retaliation: Clarification brings threats, humiliation or adverse treatment. Seek appropriate support rather than relying on a better planning document to solve the problem.

Treat apparent signs your boss is testing you as a reason to ask whether the assignment has a development goal. A suspicion that your boss is testing you for a promotion needs a more specific conversation: what skills should the assignment demonstrate, what support is available, and how would the outcome inform advancement? A supposed opportunity needs criteria you can actually work toward.

For everyday communication friction, agree on a useful update format. “Would you prefer one consolidated update?” is easier to answer than a broad discussion about whether you annoy them. The site's advice on getting better at talking to people may help with choosing clear wording and a calm tone for that conversation.

4. Keep the Brief, Changes and Decisions in One Place

Use the existing shared project document or task system to show the current agreement and any decision still needed. Keep enough history to explain a change without making someone reconstruct the assignment from scattered messages.

Start with a brief that answers these practical questions:

• What outcome is needed, and what must the finished deliverable contain?
• What is outside the scope?
• When is it due, and where does it sit among current priorities?
• Who approves it, and who resolves conflicting stakeholder requests?
• What information, access or help does delivery depend on?

Separate confirmed requirements from assumptions. For the hypothetical report, “short summary using existing data” could be confirmed, while “customer interviews included” remains a proposed addition until the timing is settled.

When a material request changes, add a brief dated entry: the previous instruction, the new request and requester, the affected work, the likely impact and the decision status. Link the relevant message where useful. Summarize verbal decisions promptly within approved workplace systems, and retain earlier versions where the system allows.

Wednesday update: Customer interviews and a presentation added. Interviews depend on Monday availability. Decision confirmed: short report using existing data due Friday; interview findings and presentation due Tuesday.

One entry now does the work of a baseline, change log and recap. Minor wording edits rarely need this treatment; changes to scope, timing or acceptance criteria do.

Handle silence and reversals explicitly

A proposed plan is not an approved commitment. Ask for a response by a concrete time tied to the work: “Please confirm by 2 p.m. so I can arrange the interviews.” If the manager does not reply and work cannot wait, follow up through the usual channel or seek a decision from the designated alternate.

Continue already authorized work where practical, and identify anything blocked by the missing decision. Avoid treating silence as permission to make a consequential change outside your authority.

If the decision reverses, refer to the current brief without turning the exchange into an argument: “Friday was agreed for the existing-data report. Adding interviews changes that scope. Which delivery option should I now use?” A short recurring checkpoint may help when changes are frequent; a stable assignment may need no additional meeting.

5. Turn New Requests Into Agreed Priorities and Deadlines

Give your manager feasible choices that expose the tradeoff. A useful option explains what they will receive and what it costs in time, scope or other work.

For the report, those choices might be a shorter version Friday or the full version Tuesday. Extra help is an option only if someone with the necessary skills and access is actually available. Handing work over also takes time.

If “everything is urgent,” ask which outcome matters first and what happens if each item waits. An approaching customer meeting may outrank an internal update, but your manager needs to make that call when the priorities conflict.

Be specific about capacity: “Preparing the presentation uses the time allocated to checking the report figures.” This is more useful than “I’m too busy,” because it shows the quality or timing consequence of the request.

Also agree which decisions you can make independently. If every small adjustment requires approval, the approval process itself can delay delivery. Necessary quality checks should have a named reviewer and enough time in the schedule.

6. Protect Your Confidence While Evaluating Feedback

When your boss makes you feel incompetent, examine the criticism against the agreed brief. Ask for a specific example and what an acceptable correction would look like.

In the report scenario, a wrong calculation is a genuine defect to correct. The absence of interviews from Friday’s version is different: the manager agreed that those findings would follow Tuesday. Separating the two lets the employee take responsibility for accuracy without accepting an unagreed requirement as a personal failure.

“You should have known” is among the things your boss should never say to you as a substitute for explaining an unstated requirement. A useful response is: “Which criterion was missing from my understanding, and where should it be included for the next assignment?”

Direct feedback gives you something you can improve. Personal insults and humiliating comparisons do not. Lists titled “10 signs of a toxic boss” can supply discussion prompts, but frequency, severity and the response to reasonable questions matter more than a score.

7. Recognize When Documentation Is Not Enough

Seek support when your boss repeatedly denies agreed decisions, punishes clarification, humiliates you or refuses workable tradeoffs after you explain the constraints.

What look like signs your boss wants you to leave may also reflect a reorganization or shifting priorities. Where responsibilities have been removed, ask why, whether the change is temporary and what you are now accountable for. The answer gives you something concrete to respond to; guessing at intent does not.

Repeated blame for following approved instructions can be one of the signs of a toxic boss. At that point, another recap is unlikely to be the whole solution. Bring selected examples to an appropriate manager, HR contact or employee representative. Explain the effect on delivery, the resolutions you attempted and the remedy you need—perhaps one decision-maker for conflicting requests.

For example, the employee in the hypothetical report scenario could bring the Wednesday agreement and any later criticism that contradicts it. The useful question for the support conversation is who can resolve the conflicting standards and establish which requirements apply.

If you are concerned about possible retaliation, describe the sequence of events and specific actions when seeking support. You do not need to settle the label before asking for help. Keep records within workplace information rules.

Where conditions remain unworkable, considering a transfer or planning a departure can be reasonable. A clearer process is worth trying; it is not an obligation to keep absorbing impossible demands indefinitely.

8. Make the Next Change an Explicit Decision

The employee in the hypothetical example still has a demanding week. What changes is that Friday’s report and Tuesday’s presentation now have agreed purposes, and the missing interviews are an understood dependency rather than a surprise failure.

Use that standard for your next assignment: can both you and your manager describe what will be delivered, when, and what has been deferred? If not, the next useful step is a decision. The question worth keeping is simple: “If this moves up, what moves back?”