Influence Without Authority — Driving Decisions Without Rank
Staff+ engineers drive decisions through trust, data, and framing — not through org rank or escalation.
When to use
- Cross-team proposals
- Pushing back on product or leadership decisions
- Getting adoption of a new standard or pattern
Tradeoffs
- Consensus is slow; avoiding authority can stall critical decisions
- Some decisions need escalation — influence has limits
Disagreement Framework
| Level | Action | When to use |
|---|---|---|
| 1 | Express concern verbally | First disagreement, low stakes |
| 2 | Write it down (RFC, Slack, email) | Recurring concern, needs a record |
| 3 | Escalate with data | Decision will cause measurable harm; bring numbers |
| 4 | Disagree and commit | Decision is made; you execute and make it succeed |
Techniques
- Anchor in data, not opinion: "Our p99 is 2s" vs "I think it's slow"
- Name tradeoffs explicitly: don't hide the downside of your proposal
- Propose reversible decisions first: lower the stakes for alignment
- Write it down: proposals that aren't written down don't get adopted
Gotcha: Disagree and commit is not silent compliance. You commit to making the decision succeed — and you document that you disagreed, so the record is clear if it fails.