Influence Without Authority

Influence Without Authority

Step 1 of 9

"I introduced code review standards" proves nothing. You could have written a document nobody opened.

The Idea

Influence stories are about the gap between having an idea and having it adopted. Without authority you have only three levers: make the change small, make the benefit visible to the people who must do the work, and let someone else carry it once it works.

Real-World Example

"I introduced code review standards." Rewritten: "Reviews were taking days. I wrote a six-line checklist and used it only on my own pull requests. Two colleagues copied it within a fortnight; the platform team put it in the template, and I was not in that conversation."

The Tradeoff

Going small means your first version is deliberately incomplete, and someone will point that out. It also means credit spreads — which is the price of adoption and worth naming out loud. Be ready to say what you would do differently with a mandate, because the follow-up question is usually exactly that.

Your turn

Put the steps in the right order.

1. 1Prove it on your own work first, where you need nobody's permission↑↓
2. 2Find the cost the people doing the work already feel↑↓
3. 3Hand it to an owner so it survives without you↑↓
4. 4Make the smallest version that removes some of that cost↑↓

Check order

Mini quiz

1 / 3

The most convincing evidence of influence is:

• AA document you wrote
• BOther people adopting the change without being asked
• CA title change
• DAttending more meetings