Influence Without Authority¶

Theme: Leadership & Influence | Seniority: Senior → Staff

Why This Question Gets Asked¶

Past a certain level, your ability to ship depends on people who don't report to you and never will. This question checks whether you can move a decision without a title to lean on:

• Do you understand why another team wants what they want, before asking them to change?
• Can you build a case that survives without you in the room advocating for it?
• Do you know the difference between influence and just being persistent or loud?
• Do you leave behind something (a doc, a tool, a metric) that keeps the decision durable after the conversation ends?

STAR + Reflection Framework¶

flowchart LR
    S[Situation\ncross-team decision,\nno authority] --> T[Task\nwhat you were trying\nto change and why]
    T --> A[Action\nwho you talked to, what\nevidence, what forum]
    A --> R[Result\ndecision changed + adoption]
    R --> Ref[Reflection\nwhat made it stick]
    style A fill:#1b5e20,color:#fff
    style R fill:#e65100,color:#fff
    style Ref fill:#37474f,color:#fff

Use the influence ladder from the framework page to pick the right rung before telling this story — jumping straight to an all-hands memo on a decision two teams could resolve in a 1:1 is itself a red flag.

Seniority Differentiation¶

When It Got Overridden¶

Not every influence attempt lands. I once tried to drive a cross-team decision on a shared retry/timeout convention — three teams were each hand-rolling their own retry logic against a common downstream service, causing correlated thundering-herd load during that service's incidents. I wrote a doc, got two of the three teams on board in 1:1s, and brought it to a shared architecture review expecting a straightforward adoption. The third team's lead pushed back hard in the room — not on the technical merits, but because I'd approached it as "let's standardize" without first checking whether their service had different latency requirements that made the standard timeout wrong for them. I hadn't done the 1:1 with the team that actually had the most to lose; I'd gone to the two easiest allies first and treated the review as a rubber stamp. The proposal got tabled, and it took another two months and an actual 1:1 with that team — where I learned their downstream dependency had a legitimately different SLA — to get a revised version adopted with a per-team override. I learned that "most burned" isn't always the right team to start with; sometimes the team most likely to object has information you need before you write the doc, not after.

Choosing the Right Forum¶

The most common mistake candidates describe (without realizing it's a mistake) is picking the wrong forum for the disagreement's actual size.

The Escalation Path¶

flowchart TD
    A[Cross-team decision\nyou don't own] --> B{Do you understand\ntheir real constraint\nyet?}
    B -->|No| C[1:1 with the owner —\nask before proposing]
    C --> B
    B -->|Yes| D{Is this the first\ntime you've seen\nthis conflict?}
    D -->|Yes, one-off| E[Solve bilaterally:\na proposal that serves both sides]
    D -->|No — recurring\nacross teams| F[Frame it as a\nsystemic gap, not an incident]
    F --> G[Convene working group —\nmost-burned team first]
    G --> H[Build a shared artifact:\nRFC, registry, lint rule]
    H --> I[Hand ownership to a\nteam rep, not yourself]

Building the Constituency¶

Staff-level influence stories have a constituency — people who will vouch for the decision when you're not in the room. Concretely, that means:

1. Talk to the people most affected first, before you have a fully-formed proposal — they become co-authors, not an audience being pitched to.
2. Use the most-burned team's story as your evidence, not your own opinion — "team X hit this twice last quarter" lands harder than "I think this is risky."
3. Leave a written artifact (RFC, doc, registry, lint rule) so the decision survives you moving teams or the conversation being forgotten.

Common Interview Questions¶

1. "Tell me about a time you influenced a decision outside your team."
2. "How do you get buy-in from people who don't report to you?"
3. "Describe a cross-team disagreement you resolved."
4. "Tell me about a time your proposal was initially rejected — what did you do?"
5. "How do you drive a decision when you have no formal authority?"

Staff-Level Extensions¶

Red Flags in Answers¶

Self-Assessment¶

• [ ] Can I name the specific forum I chose and why (1:1, doc, working group)?
• [ ] Did I describe the other side's real constraint, not just my own position?
• [ ] Do I have a story where the decision stuck after I stopped personally advocating for it?
• [ ] For Staff roles: can I point to a reusable artifact and an org-level metric that moved?