Cross-Functional Influence: Moving Things With No Authority
Topic: Cross-Functional Influence·4 Principles
"If you want to go fast, go alone. If you want to go far, go together." — African proverb
This week's premise: The hardest kind of leadership is the kind with no authority behind it. As a tech lead manager at a large company, more than half your dependencies sit with teams that don't report to you—platform, security, data, product. Positional power runs out at the edge of your team; beyond that edge, only influence works. This week, four tools: trade in "currencies" (how to move people when you can't command them), map your stakeholders before you push, line up your key people one-on-one before the big meeting (pre-wiring), and make the win theirs. The honest part: influence without authority is slower, and you'll incur favors you may never collect—we mark the cost at every step.
PRINCIPLE 01
Currencies of Exchange: With No Authority, You Trade
Currencies of Exchange
ReciprocityCurrency tradeGive first
The Principle in One Line
Beyond your team's edge, commands fail; only exchange remains. Everyone has a currency they care about—visibility, resources, favors, information, status. Influence = figure out which currency they want, then trade what you have for it. Give first, then ask.
In Their Own Words
"The cornerstone of our model is the law of reciprocity: the almost universal belief that people should be paid back for what they do—that one good turn deserves another."The foundation of cross-functional influence: people expect to be paid back for what they give—budget your favors as an account, not a one-off.— Allan Cohen & David Bradford, Influence Without Authority, Ch.2
The Five Currencies of Influence (Cohen & Bradford)
Scene
Situation: You need the platform team to change an API to unblock your project, but their backlog runs three months deep—and you have zero authority over them.
✗ Common move
"This is really critical for us—any chance you can rush it this week?" You only voiced your urgency, never why they should care. They default to no: your emergency isn't theirs.
✓ Better move
First research their currency: this quarter's OKR is "retire special-case platform APIs." So you open with: "I saw you want to cut special-case APIs. Our need actually kills off one common special case for you—my engineers will write the design doc and tests, you just review; and I'll credit your team by name as the unblocker in the VP review." You just spent three currencies: relief (task), saved effort (resources), visibility (position).
Checklist: Before You Ask
Do I know what their team cares about this quarter (OKRs, promo season, their boss's focus)?
What currency can I offer—information, hands, visibility, a future favor?
Am I giving first, or asking first?
How and when do I plan to repay this favor? (Track the debt.)
Common Mistakes
Leading with your own urgency. Your P0 isn't theirs; untranslated into their benefit, they have no reason to move.
Writing IOUs you never repay. A favor you can't return hurts more than not borrowing; an overdrawn lateral account is hard to recover.
Pressuring with "this is a company priority." Unless you really have VP backing, that's just dressing up no-power as power—and they see through it.
Female Leader's Note
Female Leader's Note
Research (Babcock, Grant, et al.) shows women are more often asked to do "office housework" (notes, organizing events, firefighting), and such effort is less often counted as currency or repaid. Countermoves: (1) make help visible and on the books—add a line like "I'll cover this; next sprint I'll need your team on X"; (2) learn to say no to pure-sink chores: "I can't take this on, but I can help you find someone." Steer goodwill toward currencies that pay back, not bottomless pits.
PRINCIPLE 02
Stakeholder Map: See Who Can Make You and Who Can Block You
Stakeholder Mapping — Power × Interest
Power × InterestReal influence netSupporters vs blockers
The Principle in One Line
Before you push a cross-team effort, don't rush to broadcast. Plot stakeholders on two axes—power and interest—then mark who's a supporter, a blocker, a fence-sitter. Apply different force per quadrant: spread evenly and you waste effort on the unimportant and miss the one who can actually block you.
In Their Own Words
"Know the other and know yourself: a hundred battles without peril. Know yourself but not the other: one win for one loss. Know neither: every battle in danger."Driving an initiative is like marching an army: identify the players first, then commit your forces.— Sun Tzu, The Art of War, "Attack by Stratagem"
The Power × Interest Grid
Scene
Situation: You're driving a company-wide migration to a new auth framework spanning six teams—you own only one of them.
✗ Common move
You send a company-wide email plus an RFC and call a 30-person meeting to announce it all at once. Result: a security director you never spoke to privately challenges you in front of everyone, the meeting derails; and the engineers who'd actually do the work were never recruited—they quietly resist.
✓ Better move
Map first. Security director = high power, high interest → a private 1:1 beforehand to make him a co-author. The neighboring platform team = high power, low interest → a one-page summary so they're "informed and not opposed," no long meeting. The frontline owners = low power, high interest → recruit them early as "migration champions" to persuade their own teams. The big meeting only ratifies; it doesn't persuade.
Checklist
Did I list every stakeholder—including the quiet one who can veto?
Which quadrant does each fall into? Is my strategy genuinely different per quadrant?
Is the blocker against the proposal, or against "not being consulted first"?
Am I mapping the real influence network or the org chart? (The real decider often isn't in the boxes.)
Common Mistakes
Broadcasting to everyone equally. High-power people who aren't handled individually feel slighted.
Cultivating only supporters, avoiding blockers. A blocker doesn't disappear because you look away.
Drawing from the org chart. The real veto often sits with a staff engineer or a senior PM, not the nominal director.
PRINCIPLE 03
Pre-Wiring: The Real Decision Is Made Before the Meeting
Pre-Wiring — The Meeting Only Ratifies
Pre-wiringCoalition buildingBlocker inside the tent
The Principle in One Line
An important decision shouldn't be heard for the first time in the meeting. A meeting ratifies consensus; it doesn't form it. Beforehand, win over key people one-on-one, collect objections, adjust the proposal, lock in support. Above all: bring the most likely opponent inside the tent early—make him a co-builder, not a sniper in the audience.
In Their Own Words
"It's probably better to have him inside the tent pissing out, than outside the tent pissing in."Rather than let a potential opponent tear you down from outside, bring him in early so he has a stake.— Lyndon B. Johnson (c. 1971, on whether to keep J. Edgar Hoover)
Scene
Situation: You're proposing a contentious technical design at an architecture review. The board has five people, one of them a senior engineer known for nitpicking and guarding his turf.
✗ Common move
You prep perfect slides and unveil the proposal for the first time in the meeting, expecting logic to win the room. The senior engineer fires off a chain of questions, the others waver, and the proposal is bounced to "let's discuss further."
✓ Better move
Three days before, you meet that senior engineer one-on-one: "I want to push a proposal, but I know you got burned on X—I'd like to hear your concerns first, so I don't miss something." You did two things: surfaced his real objection (often "not feeling respected," not the tech itself) and absorbed it into the design. In the meeting he becomes your endorser, not your sniper; you've also pinged the other supporters in advance. The meeting clears in 15 minutes.
Checklist
Are key people hearing this for the first time in the meeting, or have I pre-warmed each?
Have I brought the most likely opponent into the tent, or left him out in the audience?
Are the objections I collected absorbed into the proposal, or am I planning to fight them live?
Have I activated supporters—will someone speak for me, or am I alone?
Common Mistakes
Saving the proposal for a "grand reveal." Surprise is almost always a liability in politics.
Pre-warming only supporters, dodging the hard case. The opponent is exactly who you should consult first.
Hearing objections but not actually changing the plan. Going-through-the-motions "fake consulting" angers people more than not consulting at all.
PRINCIPLE 04
Lateral Leadership: Make It "Their" Win
Lateral Leadership — Make It Their Win
Shared goalGive away creditDon't chase the byline
The Principle in One Line
With no command authority, momentum comes from making the other person feel it's their idea, their win. The more you want the byline, the less it moves; the more you let others win, the more gets done. Translate your goal into theirs, give away the spotlight—and the influence settles on you anyway.
In Their Own Words
"Let the other person feel that the idea is his or hers."Influence without authority lives on this line: when people own the idea, they drive it for you.— Dale Carnegie, How to Win Friends and Influence People, Part 3, Principle 7
Scene
Situation: You've designed a better service-monitoring standard and want three other teams to adopt it—but you can't mandate it.
✗ Common move
You ship a doc: "Follow our team's standard—this is best practice." "Our standard," "you comply" triggers turf defense. Even if they agree, they stall: adopting = admitting you're better than them.
✓ Better move
Reframe: "I've collected the monitoring pitfalls several teams have hit; I'd like to define one standard everyone buys into—your team does alert noise-reduction better than us, can that part go in, authored by you?" You turn "my standard" into "our co-built standard," leaving the other side a byline and home turf. Once it lands, all three teams call it "the one we helped define"—which is exactly the outcome you wanted.
Checklist
Am I saying "my plan, you comply," or "the standard we defined together"?
Did I give the other side real home turf—a section they author and sign?
After it works, do I grab the credit or publicly share it out?
Do I actually want "to be seen as right," or "to get it done"? (Often you can't have both.)
Common Mistakes
Clinging to the byline. Who gets credit and whether it gets done are often two separate things.
Treating adoption as the other side "conceding." Once it feels zero-sum, they're motivated to let it fail.
Giving away credit but keeping score and grumbling later. Give for real—half-hearted is worse than not giving.
Female Leader's Note
Female Leader's Note
"Give away the credit" is double-edged for women: research (e.g., Heilman) shows women's contributions are more readily overlooked or reattributed to male colleagues (a man repeats the idea and suddenly it's his). Give away credit on top of that and you can vanish entirely. The fix isn't to stop giving, but to give on the record: (1) use written/async trails (docs, email, PRs) to timestamp your original contribution; (2) borrow the Obama-staffer "amplification" tactic—ally up and name each other: "as XX just proposed…", pointing credit back to its real source. Giving credit is a tactic, not self-erasure.
Further Reading
Allan Cohen & David Bradford · Influence Without Authority — currencies of exchange and the law of reciprocity; the source for Card 1.
Tanya Reilly · The Staff Engineer's Path — cross-team leadership without authority, glue work, driving big projects.
Will Larson · Staff Engineer / An Elegant Puzzle — how staff engineers manage stakeholders and influence.
Robert Cialdini · Influence — reciprocity, commitment-consistency, social proof, and the other principles of persuasion.
Adam Grant · Give and Take — how givers avoid being drained while accruing long-term influence.
Dale Carnegie · How to Win Friends and Influence People — let the idea be theirs.
Sun Tzu · The Art of War, "Attack by Stratagem" — know the other and yourself; supreme victory without battle.
Open Questions
Is influence bought through exchange inherently fragile—the moment you have no currency left, do you instantly lose power?
Yes and no. Purely transactional relationships are fragile: empty the account and the bond breaks. But Cohen & Bradford's point is that repeated good-faith exchange deposits into relationship currency—trust itself becomes the most durable currency, so future requests no longer need to be settled transaction by transaction. Short term you run on currency; long term on reputation: the former is fragile, the latter antifragile.
Where's the line between "wiring it up beforehand" and "back-room dealing that hollows out the formal process"?
The line is transparency and reversibility. Healthy pre-wiring makes the formal meeting more efficient—every objection has been heard and absorbed, and it can still be overturned in the room. The corrupted version: it's privately locked before the meeting, the formal session is a rubber stamp, and dissenters have no real voice. Self-test: if someone raises a strong new objection in the room, can your "consensus" still be overturned? If yes, it's pre-wiring; if no, it's manipulation.
Does giving away credit and staying invisible long-term hurt your own promotion—since promotion rewards "visible individual impact"?
A real tension, especially in orgs that prize the individual-hero narrative. The fix isn't to grab credit, but to distinguish two visibilities: grabbing the "I did this" credit, versus accruing the reputation that "things he touches succeed." The latter is slower but higher-order—staff/director promotions look precisely for "makes things happen across teams." But be honest: in short-term, individual-KPI-driven environments, excessive selflessness gets exploited—which is when the earlier "give on the record" matters.
In high-context, steep-hierarchy orgs (East Asia, parts of India), how should "lateral influence" and "pre-wiring" be adjusted?
In steep-hierarchy cultures, pure peer-to-peer persuasion often isn't enough—many things ultimately need "borrowing power upward": persuade the shared boss first, then push top-down. Pre-wiring weighs even more (public dissent is very costly). Western "influence without authority" assumes a relatively flat structure; when transplanting it, thicken the "upward" line.
Your Day 8 Action
Do one concrete thing this week—not reflection, not reading:
Pick one cross-team dependency you're genuinely stuck on right now (a team with no incentive to help you).
(1) Use Card 2's grid to plot the stakeholders into four quadrants; circle the one who is "high power but you haven't spoken to one-on-one yet." (2) Use Card 1 to write down one "currency" their team cares about this quarter, and one you can offer in trade. (3) This week, book a 15-minute 1:1 with that key person (Card 3's pre-wiring)—ask their concerns first, bring no proposal to persuade, just listen.
Reflection: Look back at your most recent "couldn't move it" cross-team effort. Did it stall because your proposal wasn't good enough, or because you skipped "figure out their currency first / bring them into the tent first"?