Influence Without Authority: The Core Skill of Every Chief of Staff

Takeaway: Influence without authority starts with understanding another person's constraints, making a request they can evaluate, and building enough credibility that cooperation doesn't depend on borrowing the executive's power.

Chiefs of staff often coordinate leaders whose budgets, teams, and performance reviews they don't control. They may need a product leader to revise a deadline, a finance leader to review an investment, or a sales leader to correct a forecast. The title alone can't produce those outcomes.

Influence is the work of making progress across those reporting lines. It isn't a substitute for clear authority, and it doesn't mean persuading someone to accept a bad trade. It gives an operator a disciplined way to understand resistance, improve a request, and recognize when the decision belongs with someone else.

Start with the other person's operating context

Suppose the CEO asks you to accelerate a hiring plan. The finance lead resists. Repeating the CEO's urgency won't answer the finance lead's concern about cash, approved headcount, or the forecast. Before asking again, find out which constraint is driving the response.

Useful questions include:

• What is this leader accountable for?
• Which deadline, metric, or risk are they protecting?
• What information would change their view?
• What can you adjust without weakening the original goal?
• Who owns the decision if the conflict remains?

This step prevents a common mistake: framing every request around the principal's needs. The department leader still has responsibilities to their own function and to the company. A workable proposal has to acknowledge them.

Use exchange as a diagnostic

Allan Cohen and David Bradford's Influence Model treats colleagues as potential allies and asks what each person values. Their "currencies" aren't money. They include resources, information, recognition, relationships, access, and help with work (Currencies of Exchange).

For an operator, a fair exchange might mean:

• providing a cleaner decision brief so a leader doesn't have to reconstruct the context;
• adjusting the sequence of two initiatives to protect a critical deadline;
• giving a functional team visible credit for work it led;
• bringing the right decision to the principal instead of sending a department through another round of meetings; or
• sharing information that lets the other leader plan with fewer surprises.

The exchange has to be legitimate. Access to the principal isn't a personal favor to trade, confidential information isn't currency, and recognition shouldn't be withheld until someone cooperates. Use the model to find mutual value, not to manipulate a colleague.

In the hiring example, the operator might ask finance to review two paced options rather than approve the full acceleration on the spot. In return, the operator can bring a complete headcount sequence, identify which roles affect a committed milestone, and make sure the principal decides the remaining cash tradeoff. The request becomes easier to assess because the constraints and decision owner are visible.

Build credibility before the difficult request

Robert Cialdini's principles of persuasion offer useful lenses for how people respond to requests. Several apply directly to cross-functional work:

Reciprocity: People are more willing to help someone who has been useful to them. Build this through real contribution, not favors held for later collection.

Authority: Relevant expertise and trustworthiness make a recommendation easier to accept. Know the business context, distinguish fact from assumption, and say when you need to check something.

Consistency: Prior commitments help clarify what has already been decided. A decision log or written recap can prevent a team from reopening settled ground while still allowing new evidence to change the call.

Social proof: Knowing how peers are approaching a problem can reduce uncertainty. It shouldn't be used to silence the two leaders who disagree with the other three. Their objections may reveal a risk the majority missed.

Unity: A shared goal can change the tone of a disagreement. "We need an answer that protects the launch and the cash plan" is more useful than "the CEO wants this."

These principles don't cover every influence problem. Incentives can conflict, authority may be unclear, and a colleague can reasonably say no. The operator's job is to improve the conditions for a sound decision, not to manufacture agreement.

Make requests easy to evaluate

A strong request is specific enough that the other person can answer it. Include:

1. The outcome: What needs to happen?
2. The reason: Why does it matter now?
3. The evidence: What facts and assumptions support it?
4. The tradeoff: What will change if the request is accepted?
5. The role: What do you need this person to decide or do?
6. The deadline: When is the answer needed, and why?

Compare "Can you prioritize this?" with "Can your team review the revised launch dependency by Thursday? If that timing displaces the reporting work due Friday, I'll take the conflict to the leadership team." The second request gives the leader a decision, a consequence, and an escalation path.

Don't spend borrowed authority

Proximity to the principal can produce a quick yes. It can also create resentment if the operator implies that every request is an executive directive.

Use the principal's authority when the principal has made the decision. State the decision accurately, record it, and clarify what remains open. When the issue is still a recommendation, let the reasoning stand on its own.

Over time, influence rests on ordinary behavior:

• close the loops you own;
• keep confidential information confidential;
• give credit to the people who did the work;
• take responsibility for your own commitments and errors;
• explain tradeoffs without overselling; and
• listen closely enough to revise a weak request.

That record matters more than a clever persuasion tactic.

Know when to escalate

Some disagreements should remain disagreements until the right owner decides. Escalate when the tradeoff crosses functions, the decision exceeds either person's authority, or delay creates a material consequence.

Escalate the decision, not the colleague. A useful escalation says: "Product can meet the requested date only if finance approves the additional contractor spend. Both leaders agree on the dependency and differ on the tradeoff. We need your decision by Tuesday." It doesn't accuse either person of blocking the work.

Is influence without authority manipulation?

It can become manipulative if information is hidden, pressure is disguised, or the other person's interests are treated as obstacles. A fair influence attempt can withstand disclosure: the reasoning, tradeoff, and decision process remain acceptable when everyone can see them.

What if the other person still says no?

Find out whether the no reflects missing information, a competing obligation, or a decision they don't own. Revise the request if the concern is valid. Escalate if the remaining tradeoff belongs with the principal or leadership team.

How do I build influence when I'm new?

Learn how decisions move, deliver the commitments you make, and help with small problems before taking on a major cross-functional push. Credibility grows from a visible record, not from claiming the principal's backing.

For another way to assess the credibility behind your requests, read The Trust Equation.