Maintenance
Part of When you are the authority: earning deference without a costume
Authority at work: a script for objecting to a senior decision
Authority at work, from the junior seat: which kind of authority is speaking, four moments where objections die, and five moves that make an objection land.
Workplaces run on delegated trust. Nobody can verify everything, so people defer to whoever is supposed to know. In an organization, "supposed to know" and "has power over my review" are frequently the same person, and that overlap is what makes authority at work different from authority anywhere else.
Two things get confused whenever this goes wrong: position authority (this is my call) and earned credibility (I have been right about this kind of thing before). They are separate. The difference between a right to decide and a reason to be believed is the same one philosophers draw between authority and expertise.
Someone can have one without the other in either direction. Most workplace friction comes from a decision being argued as though it were the second when it is really the first. An objection lands when it is aimed at the right one.
What to take away
- Work out which kind of authority is speaking before you object: a right to decide, or a reason to be believed.
- Aim the objection at the reasoning, not at the right to decide.
- Five structural moves do more than tonename the kind of disagreement, offer an alternative, state what would change your mind, separate the call from the reasoning, and write it down first.
- Managers who want real objections have to make dissent cheap.
Which kind of authority is speaking
Each reply to an objection rests on one of two things: a right to decide or a reason to be believed. The table sorts four common replies, with a question that moves each one forward without attacking anyone's right to decide.
| What you hear | What it rests on | A question that moves it |
|---|---|---|
| "This is my call." | Position | "Understood. Can I put the risk on record before you decide?" |
| "I have seen this go well before." | Earned credibility | "Which part of how it works today did that case share?" |
| "I will raise this with the VP." | Position, used as a first move | "Happy for that once the objection has been answered." |
| "That is the policy." | A rule | "What does the policy protect against?" |
A reply that rests on position can still be right, and a reply that rests on credibility can still be out of its field. Whether deference is sound at all comes down to the three checks of field, accountability and independence. The table only shows which kind of claim you are facing.
Four moments where objections go quiet
Each of these is ordinary, and none involves anybody behaving badly, so asking people to behave better will not fix them. What helps is spotting the moment as it happens and having one sentence ready.
The opinion that ends the discussion. A director offers a technical view in passing. The thread goes quiet. Six weeks later the decision turns out badly and three people say privately they had doubts. The director was simply right often enough that checking felt unnecessary, and the cost of being the person who checks kept rising until nobody paid it.
Pay that cost early and cheaply: ask one specific question before the thread closes. If you run the meeting, the fix is procedural: the most senior person in the room speaks last. It feels artificial for about two meetings and then it feels normal.
The escalation used as an argument. Someone answers an objection with "I will raise this with the VP." That is not a response to the objection. It may be a legitimate next step, since some decisions belong upstairs, but it comes after the argument is answered, not instead. The tell is timing: escalation offered as a first move usually stands in for a reason.
The expert who is out of date. This one is uncomfortable because the credential is real. Someone trained deeply ten or fifteen years ago in a field that has moved still has instincts that beat a novice's and trail a current practitioner's. What settles it is not seniority but a specific, checkable claim about how the thing works now.
"Because that is the policy." Policy is sometimes a reason: it encodes a constraint you need not re-derive. Policy is sometimes a placeholder for a reason nobody remembers. To tell the difference, ask what the policy protects against. If someone can answer, it is load-bearing. If nobody in the building can, you have found a fossil.
Five moves that make an objection land
Most advice about disagreeing upward is about tone. Tone matters less than structure. These five moves change what the other person has to answer, which is what actually
Making Upward Disagreement Land
- Say which kind of disagreement it is
- Name the decision you would make
- State the condition that would change your mind
- Separate the call from the reasoning
- Put it in writing before the meeting
- Say which kind of disagreement it is."I think this is wrong" and "I think this is risky and here is the specific way it fails" are different conversations. The second is much easier to answer and much harder to dismiss.
- Name the decision you would make, not just the flaw.Objections without an alternative get filed as friction.
- State the condition that would change your mind.It shows you are reasoning rather than resisting, and it invites the same disclosure back.
- Separate the call from the reasoning."It is your call and I will back it; I want the concern on record" is not a threat, and it lets a manager accept the information without accepting a challenge to their authority.
- Put it in writing before the meeting when you can.Written objections are read without a room watching, which removes most of the social cost from both sides.
Put together, the five fit in four sentences: what kind of problem it is, what you would do instead, what would change your mind, and that the call is theirs. A manager can answer that in the meeting without having to defend their standing.
When you are the one with the authority
If you run a team, your problem is the inverse: you receive a filtered signal
Getting Real Objections as Boss
- Collect views before you give yours
- Ask for strongest opposing case by name
- Rotate who argues the opposing case
- Separate right from can live with it
- State your own confidence level plainly
Five moves keep that from becoming mere compliance. Collect views before you give yours: in writing if the group is large enough that speaking order matters. Ask for the strongest version of the opposing case and give it to someone by name, rotating who gets the job so it never becomes one person's identity.
Distinguish "who thinks this is right" from "who can live with it", because those get merged into a single nod otherwise. Say your own confidence level plainly; a team that cannot tell your hunches from your convictions will treat both as instructions.
None of this is soft. A team that only agrees with you because you are senior has given you compliance, and compliance stops working the moment you are not looking. A room that agrees only to belong is showing normative influence, not conviction.
Position authority needs to be justified, not merely held. The Stanford Encyclopedia entry on political legitimacy treats that as the standing question, and it applies to a team with little loss.
Rank tells people who decides, but says nothing about who is right. A manager who keeps those two claims separate in their own speech will find the team does too. The longer catalogue of how deference fails, from both sides of the table, sits in authority mistakes.
Common questions
How do I disagree with my manager without it becoming a problem?
Disagree about the decision and not about the right to make it. "I think this is wrong, and it is your call" separates the two claims and lets the other person take the objection without also having to defend their standing.
What if I am asked for my view after the senior person has given theirs?
Say so, once. Asking to write views down before discussion is a process request rather than a challenge, and it is much easier to make in advance than in the moment.
Does a manager have to justify every decision?
No, and pretending otherwise wastes everyone's time. What they owe is a clear statement of which kind of decision it is, so that a call made on authority is not presented as a call made on evidence.
How do I tell whether my team actually agrees with me?
Look at whether anyone has disagreed with you recently and what happened to them afterward. That single example sets the price of dissent for months, and your team is reading it more carefully than they read anything you say about openness.
