Influence Without Authority

---
name: influence-without-authority
description: Use when moving outcomes without authority. Trigger phrases include "how do I get [team] to do X without going to their manager", "I need to convince [person] to support this", "I have to push back on [exec] without burning the relationship", "build the coalition", "I'm a TPM/staff eng/IC and I need [team] to prioritize this". Distinct from feedback-frameworks and coaching-mode.
---

# Influence Without Authority

Most senior leadership work happens without authority — TPMs, staff engineers, senior ICs, PMs move outcomes through people they can't tell what to do. **Opinionated about legitimacy:** most "influence" literature shades into manipulation — works short-term, costs trust long-term. This skill refuses to teach that.

## When to apply

Trigger when the user needs to: drive a cross-team architecture change, win a skeptical principal engineer, mobilize a coalition, push back on an exec without burning the relationship, get a sister team to prioritize a dependency, or turn "no" into "not now."

Skip when: the user *does* have authority and is avoiding it; they're conflating influence with manipulation; or the need is one-shot and the relationship disposable.

## First: diagnose what you actually need

1. **What outcome do you need?** Concretely — what, by whom, by when?
2. **Whose decision is this?** If theirs, make a strong case and accept the call.
3. **What's their position, and why?** *Position* is what they've said; *interest* is what they need. Addressing position alone produces fake yeses.
4. **Their BATNA — and yours?** Who loses more from inaction?
5. **Your relationship's account balance?** If overdrawn, no tactic compensates.

Half of failed attempts skip this.

## The currencies model

Cohen and Bradford: people respond to currencies they value. Five families:

- **Inspiration/vision:** strategic narrative; mission; craft.
- **Task:** resources; information; help on something hard.
- **Position:** recognition; reputation; contacts.
- **Relationship:** personal support; inclusion; trust you have their back.
- **Personal:** gratitude; ownership; self-image.

Designing an ask: *what currency matters to this person, and which can I credibly offer?* Currencies aren't chits — what you offer must be real and valued as *they* value it.

## The legitimacy line

Each Cialdini principle has a legitimate and a manipulative use:

| Principle | Legitimate | Manipulative |
|---|---|---|
| **Reciprocity** | Genuine giving, no strings | Favors with implicit IOUs |
| **Scarcity** | Naming real constraints | Manufacturing urgency |
| **Authority** | Citing relevant expertise honestly | Borrowed authority; titles |
| **Social proof** | Honest peer signal | Staged "everyone agrees" |
| **Liking** | Genuine relationship-building | Performative warmth, flattery |
| **Consistency** | Acting on stated values | Trapping via small commitments |

In the right column? Stop — the relationship cost exceeds the gain.

## Designing the move

1. **The frame.** Ask in *their* terms: *"This API change reduces the support load your team's been complaining about"* beats *"prioritize my change."*
2. **The stakeholder map.** Decider, influencers, blockers, amplifiers — sequenced. The decider often shouldn't be the first conversation.
3. **The opening.** Usually *listening*. For senior people, bring context, not asks.
4. **The ask.** Smallest specific ask; honest stakes; offer the currency; leave room for pushback.
5. **The follow-through.** Acknowledge help, send credit upward, reciprocate unasked.

## Pushing back on authority

One addition: **disagree privately, commit publicly** once the call is made. Acknowledge the decision; offer missing context; propose an alternative, not just "no"; name the cost of being wrong; reopen only on new information.

## Mobilizing a coalition

1. Find early believers first — don't pitch the room before 1–2 quiet allies.
2. One champion per affected team beats five passive supporters in one team.
3. Address the strongest objector openly *before* the room meets.
4. Make joining costless: soft commitments first, converted to public ones at the right moment.

## Operating principles

- **Trust is the substrate.** Every tactic scales with it.
- **Over-invest in relationships before you need them.**
- **Ask less than you could; deliver more than you said.** Influence accounts compound.
- **Be honest about what you want.** Hidden agendas leak.
- **Optimize for the iterated game.** The move that wins this round but damages the relationship costs more than the next three rounds.
- **Respect the right to say no.** People who can't decline comply, then slow-walk.

## Anti-patterns to flag

- **Going to their manager too fast.** If you escalate, tell them first.
- **Triangulating.** Third-party pressure erodes the relationship.
- **Manufactured urgency.** Trains people to discount you.
- **Strategic gratitude.** Extractive thanks reads transactional.
- **Vague IOUs.** "I'll owe you one" is worth nothing.
- **Influence as the answer to everything.** Sometimes use authority; sometimes accept the no.
- **Skipping the listening conversation.** Costs more later.

## Composition with other skills

- **`feedback-frameworks`** — COIN when the move needs honest feedback, especially upward.
- **`one-on-one-prep`** — when the listening conversation happens in a 1:1.
- **`coaching-mode`** — sometimes asking beats persuading.
- **`leadership-os`** — the conversational layer; this is the discipline.
- **`stakeholder-reflect`** — evidence base; read before, capture after.
- **`read-the-room`** — read the response before declaring victory or defeat.
- **`decision-log`** — log the decisions influence produced, especially talked-into ones.