Day 10 · Phase B

Map the Decision Chain: The Best Pitch to One Person Can Still Be Vetoed by Someone You've Never Met

Topic: Map the decision chain·4 principles
The most dangerous deals are often the "warmest" ones — you and one friendly contact hit it off, you assume it's in the bag, and you never learn that the person who actually signs off has never heard your name. Selling anything complex, you're never facing one person. You're facing a room full of people with different agendas.
Last time we dug out where it hurts. This time: whose pain is it, and who pays to fix it — because inside one organization, the person who feels the pain, the one who signs the check, the one who has to use it, and the one who might block it are often four different people. The rookie mistake is to pour everything into one contact who's warm to you, assuming that winning them wins the deal. But that person may neither pay, nor decide, nor be able to stop the objector — you won a match that doesn't count. Four things this time: seeing that "one contact ≠ one deal," sorting the four roles on a chain and what each is really buying, finding the champion who'll speak for you when you're not there, and reading what the blocker is actually afraid of losing — while holding the line: mapping the chain is about getting the right value to the right ears, not stabbing anyone in the back.
PRINCIPLE 01

A single enthusiastic contact is not a deal Pin it all on one person and the deal dies when they go quiet

the buyer is a groupsingle-threading = top killerconsensus decides
Selling anything complex, the decision is almost never made by one person. A typical B2B purchase hides a group — the one who pays, the one who decides, the one who'll use it, the one who'll resist. Leaning all your weight on one person you click with is "single-threading": the moment they take leave, change roles, or lose their voice, your deal snaps with them. The real work is finding each of these people and learning what each one wants.
"The average buying group for a complex B2B solution involves six to ten decision makers." — Gartner (B2B buying research)
You (the seller) Friendly contact the only one you've met The room you've never seen Pays (decides) Uses it daily Vets (can veto) Objects Finance / Legal / IT / user reps… One thread only? It snaps, the deal snaps
Setup: You're selling a system. Sam, in one department, really clicks with you and keeps saying "we so need this, I'll push it." Three months later, the deal goes silent.
✗ Betting it all on one person (single-threading)

"Sam's this supportive — we're golden!" All your information flows through Sam's single pipe, and you never asked "besides you, who else has to say yes?" Result: Sam does want to push it, but their director thinks "not a priority this year," finance freezes the budget, and Sam has no real say. You won Sam and lost the room you never walked into.

✓ Use the enthusiast to map the whole chain

"Great — having you push this makes me a lot more confident. Let me help you stock up on ammo: who usually signs off on the budget for something like this? And besides your team, who else would care, or might have reservations?"
"How about we loop in finance and IT for a round so we're not redoing work later?"
—— You didn't bypass Sam; you used them as a guide to trace who pays, who vets, who might object. The enthusiast is the entrance, not the finish line.

EN Selling anything complex, the decision is almost never made by one person. A typical B2B purchase hides a group — who pays, who decides, who'll use it, who'll resist. Pinning everything on one friendly contact ("single-threading") means the deal dies the moment they go quiet. Use the enthusiast as a guide to map the rest, not as the finish line.

Why it works

Mechanism: more people means thinner responsibility, and decisions stall. When one person decides, the responsibility is all theirs and the motive is clear; when a group decides together, no one has to own it alone — "let's wait, let's look at it more" becomes the safest option, so the bigger the committee, the harder it is to decide anything. The trouble with a single thread is that the person who actually controls the budget and the veto has never heard your value, while your carefully crafted persuasion landed on someone with no real voice.

  • Industry research · the buyer is a group (large sample, solid direction): Gartner (formerly CEB) research on complex B2B buying repeatedly finds a typical purchase involves 6–10 decision makers (The Challenger Customer, Adamson, Dixon et al., 2015; the ~6.8 average is often cited), and as the group grows, reaching consensus itself becomes the biggest barrier to a deal. Large sample and a stable direction, but it's proprietary institutional research, not a publicly reproducible controlled study — flagged honestly.
  • Social psychology · diffusion of responsibility (hard evidence): Darley & Latané (1968, JPSP) showed with bystander experiments that the more onlookers present, the lower the odds any single person steps in to help, because responsibility gets "spread thin" across the crowd. This diffusion of responsibility is a repeatedly replicated classic — and it's the psychological floor under why committees stall and no one pulls the trigger.
  • Takeaway · single-threading is a quantifiable risk: dealing with only one contact ties the whole deal to one variable you can't control (they quit / transfer / fall from favor). Multi-threading isn't politeness — it's insurance on the deal.

Boundary: multi-threading doesn't mean bypassing your contact and spraying the org at random. Suddenly going over enthusiastic Sam's head to pester their boss makes Sam feel betrayed — the right move is to climb through them, via their introduction (see principles 3 and 4).

Trace the chain through your contact

· "For a decision like this, who usually signs off / owns the budget?" — find who pays and decides.

· "Besides your team, who else would use this, or care about it?" — find the users.

· "As this moves forward, which step or person tends to get stuck?" — find the gatekeeper and the blocker.

· "If this ultimately didn't happen, whose 'no' would most likely be the reason?" — surface the objector early.

· "If it's alright, could we bring X into the next conversation?" — multi-thread naturally.

Idiomatic phrasing

"Who else needs to weigh in on a decision like this?"

"Let's not single-thread this."

An enthusiastic contact is a doorway, not the deal.

PRINCIPLE 02

Four roles, each buying something different The right message to the wrong person is wasted breath

economic buyerusergatekeeperright words, wrong ears
The people on a chain aren't cast from one mold. The classic split has four roles: the one who pays and decides (economic buyer), the one who uses it daily (user), the one who vets and can veto (technical / compliance gatekeeper), and the insider who feeds you intel (coach). They care about completely different things — lecture the boss on how nice the buttons are, or hit a frontline user with three-year ROI, and you're saying the right thing to the wrong person. Wasted effort.
"For every sale there are four buying influences: Economic, User, Technical, and Coach." — Miller & Heiman, Strategic Selling
Economic buyer (pays · decides) Buys: ROI, risk, is it worth the money Cares: total return, budget, their record Tell them: yearly saving, risk control User (uses it daily) Buys: is it easy, does it save hassle Cares: daily feel, learning curve, no mess Tell them: the grind it kills each day Gatekeeper (tech/compliance · veto) Buys: compliant, meets specs, secure Cares: no incidents, no blame, no trouble Tell them: certs/security/compatibility Coach / insider (feeds you intel) Gives you: the inside story, map, timing Cares: this winning helps them too Give them: ammo to carry (next principle) Same product, translated into four different "what's in it for me"s
Setup: You sell collaboration software. You finally land 15 face-to-face minutes with their CFO (the economic buyer).
✗ Telling the CFO what only a user cares about

"Our interface is super friendly, you build tasks by dragging, notifications are instant, employees love using it!"
—— The CFO is stone-faced. This is the user's language, not theirs. What's in their head is "hundreds of thousands a year going out — where's the return, where's the risk?" You spent 15 precious minutes pitching someone who doesn't buy on any of that.

✓ Speaking the economic buyer's language to the CFO

"Straight to it: your cross-team coordination currently burns about X person-hours a month, roughly $XX a year. Clients like you cut that by about 60% with this, so payback runs about two quarters, and it's net savings after. On risk, we have a ready plan for data compliance and migration."
—— Same product, translated into their ledger: return, payback period, risk. "Is it nice to use?" you'll save for the user's demo.

EN The people on a decision chain aren't one type. The classic split: the economic buyer (pays, decides — buys ROI and risk), the user (buys daily ease), the technical/compliance gatekeeper (buys "won't blow up, won't get me blamed"), and the coach (feeds you intel). Pitch daily-usability to the CFO or three-year ROI to a frontline user and you're saying the right thing to the wrong person.

Why it works

Mechanism: each role's "what's in it for me" differs, so value must be translated per person. The economic buyer answers for total return and risk, the user for their own daily experience, the gatekeeper for "nothing blows up, no blame lands on me." The same feature means something completely different to each. People only act on reasons that mean something to them — hand A's reason to B, and all B hears is noise. You map the chain precisely so you can tell each person their own version of the story.

  • Method · four buying influences (field framework, widely used): Miller & Heiman's Strategic Selling (1985) sorts each deal's decision makers into economic, user, technical, and coach — each with different concerns and veto power. It's a field framework the sales world has used for decades, not a controlled experiment, but the direction — segment by role, pitch by role — is solid. Modern methodologies like MEDDIC ("economic buyer / champion") share the same root.
  • Psychology backing · self-relevance drives attention and memory: the more information relates to the "self," the more it's attended to and remembered (self-reference effect, Rogers, Kuiper & Kirker, 1977 — a robust finding). This is why only the "means something to me" version gets through — pitch the wrong person and you've delivered a message unrelated to them, which gets filtered out automatically.
  • Key distinction · the one who pays ≠ the one who uses: many deals die right here — the user is in love, but the economic buyer who never owns the price kills it with one "too expensive"; or the economic buyer wants it, but frontline users find it a hassle and resist en masse. Cover both ends.

Boundary: the four roles are "roles," not headcount. One person can wear two hats (a small-business owner is both economic buyer and user), and one role can be several people (three department heads jointly vetting). Don't map mechanically to headcount — map by "who answers for which concern."

Four roles, one opener each

· To the economic buyer: "In three sentences, here's the return, the payback period, and the risk of this investment."

· To the user: "Which of your most annoying daily chores does this kill? Let's try it live."

· To the gatekeeper: "On hard specs — compliance, security, compatibility — let me walk you through a checklist, line by line."

· To the coach: "What's in this for you if it lands? How can I help you sell it internally?"

Idiomatic phrasing

"Who's the economic buyer here — who signs off on the budget?"

"IT can't say yes, but they can say no."

Sell the ROI upstairs, sell the ease-of-use on the floor.

PRINCIPLE 03

Find your champion: who speaks for you in the room you can't enter The real decision gets made where you aren't

champion vs powerless enthusiastdecisions happen off-stagetest with a small ask
The real close happens in a room you can't get into — so when you're not there, someone has to fight that fight for you. That person is your champion: they have internal influence, genuinely believe you can help them, and are willing to speak up for you and feed you intel in your absence. Note: someone warm to you but with no voice in the company, or who cheers with their mouth and never lifts a finger, is a cheerleader, not a champion.
"A champion sells for you when you are not there." — MEDDIC methodology (originated at PTC, 1990s)
Champion (find this one) ✓ Has internal influence ✓ Truly believes in you ✓ Speaks up when absent ✓ Does real things for you → Wins you the room Coach (useful) ✓ Gives intel and the map ✓ Tells you internal moves ? May lack influence ? May not back you openly → Helps you see, not win Cheerleader (easy to misread) ✓ Warm, really likes you ✗ No voice / no influence ✗ Cheers, never acts ✗ Dodges when asked to act → Feels safe, is hollow
Setup: Sam keeps saying "I'm fully behind you." You want to know whether Sam is a real champion or an enthusiastic cheerleader. Method: give them a "small ask" and watch whether they move.
✗ Judging by verbal warmth alone

"Sam says they fully support it, so I'll just wait for them to move it forward."
—— You've staked the deal on "they said they'd push." But "I'm behind you" is the cheapest promise there is; it costs them nothing. A month later, zero progress, and you don't even know whether they did anything.

✓ Test with a small ask (the champion test)

"Thank you, really. Could I ask a small favor: could you introduce me to Wang, who owns the budget, or set up a 15-minute three-way? I'd like to walk the ROI to them directly and save you relaying it back and forth."
—— Watch the reaction: a real champion arranges it ("I'll set it up"); a cheerleader dodges ("they're really busy," "bad timing," "let me mention it to them" — then nothing). The one willing to spend a little of their own internal credit to get it done is the champion.

EN The real decision gets made in a room you can't enter — so someone has to fight for you when you're not there. That's a champion: internal influence, genuine belief you'll help them, and willingness to advocate for you in your absence. Someone warm but powerless, or all-talk-no-action, is a cheerleader, not a champion. Test the difference with a small ask — will they spend a little internal credit to actually move it?

Why it works

Mechanism: a decision you can't attend needs a present proxy — and an insider vouching for you is more credible than you vouching for yourself. (1) Purchase decisions happen in internal meetings, hallways, group chats — where you're absent 95% of the time. Without a proxy, your value proposition never enters those rooms. (2) The same sentence, said by a self-interested outside seller, is automatically discounted; said by "one of us," it's taken as a neutral, credible endorsement (social proof + source credibility). A champion speaking for you beats you saying it ten times.

  • Method · the champion is a verifiable role (field framework): MEDDIC (originated at PTC / Parametric, 1990s, Jack Napoli et al.) lists "Champion" as one of six elements and stresses the champion must be verifiable — not "likes you," but proven against small asks (willing to introduce, obtain internal documents, arrange meetings). A widely used field method, not a controlled experiment, but the direction is reliable.
  • Psychology · source credibility and social proof (fairly hard): persuasion depends heavily on whether the source is credible and "one of us" (Hovland & Weiss, 1951, the classic on source credibility; and Cialdini's social proof principle). An internal champion's endorsement is your claim spoken through a more credible mouth.
  • Commitment & consistency · have them do one small thing: once a champion does something small for you (an intro, an internal forward), the "act consistently with my actions" pressure makes them more invested in continuing to help — the small ask is both a test and a deeper bond. (See the influence-principles piece on this site.)

Boundary: don't treat a champion as a tool to squeeze. A healthy champion relationship is win-win — if this lands, they gain a result / solve their own pain inside the company. Keep helping them so "backing you" pays off for them, rather than being a one-way extraction.

Light to heavy — watch whether they move

· Light: "Could you forward this one-pager to Wang?" — forwarding is near-zero cost; no move = shaky.

· Medium: "Could you introduce me / set up a 15-minute three-way?" — willingness signals influence and the will to use it.

· Heavy: "Before the internal review, could you get me their evaluation criteria / budget range?" — pulling this off means a real champion.

Rule of thumb: a champion isn't declared — they're proven by doing.

Idiomatic phrasing

"Could you introduce me to whoever owns the budget?"

A champion sells for you when you're not in the room.

Cheerleaders cheer; champions act.

PRINCIPLE 04

The blocker isn't your enemy — read what they fear losing Beat them in an argument and they dig in harder

resistance rarely about the producthand a way out, don't fight head-online: no backstabbing
There's always someone on the chain quietly pushing against you. Key insight: their opposition is usually not because your product is bad — it's that this change makes them lose something: more work, lost turf, personal risk, or the incumbent supplier being their person. Treat them as an enemy to beat head-on and they'll only dig in harder. The real fix is to understand what they're afraid of losing and, wherever you can, hand them a way out.
"People don't resist change. They resist being changed." — widely cited in organizational behavior (on resistance to change)
They say: "This solution won't work" (surface reason, maybe not the real one) Fears more work Migration/learning all lands on them Fears lost turf Owns this area now switch = out of it Fears the blame If go-live breaks it's on them Ties to incumbent Relationship/stake switch = awkward Fix: don't rebut "won't work" — catch what they fear losing, hand a way out
Setup: The tech lead, Zhang, keeps nitpicking and dragging the timeline. You've learned what he actually fears: after go-live, all the maintenance falls on his group, and he's afraid of taking the blame for an outage.
✗ Treating him as an enemy and rebutting him head-on

"Zhang, none of your concerns really hold up — our system is very stable, none of our other clients have issues."
—— You won the debate and lost the person. Publicly rebutted, his face and "technical authority" take a hit, so now he has to prove he wasn't wrong — and blocks even harder. Worse, you never touched what he actually fears: the workload and the blame.

✓ Catch what he fears losing, hand him a way out

"Zhang, you vet the hardest, which is exactly why I want you in on this. I get that maintenance and stability pressure after go-live land mostly on your side — so I want to nail this down with you: we take on migration and first-year on-site support, and if anything breaks our engineers own it first, SLA written into the contract. So if something does go wrong, we carry it together, not you alone."
—— You didn't rebut him once; instead you lifted off the two things he feared — more work and the blame. Once a blocker sees the change no longer costs them, the fuel for opposition drains away — and sometimes they turn into an ally.

EN Someone on the chain is usually pushing against you in the shadows — and it's rarely because your product is bad. It's that the change costs them something: more work, lost turf, personal risk, a relationship with the incumbent. Beat them in an argument and they dig in harder. Instead, figure out what they fear losing and hand them a way out. A blocker who stops losing often stops blocking.

Why it works

Mechanism: a blocker's opposition is loss aversion + status-quo bias + psychological reactance, combined. To them personally, change means a certain loss (more work, shrunken power, carried risk) — losses they feel far more sharply than equal gains — while the status quo is easiest and lowest-blame. And if you rebut head-on and try to "persuade" them out of their position, you trigger reactance: the moment people feel their freedom is being taken, they instinctively grip their original position tighter. So the effective path isn't to beat them — it's to erase the loss they'd carry and hand their autonomy back.

  • Psychology · loss aversion + status-quo bias (hard evidence): Kahneman & Tversky's prospect theory — a loss weighs about twice an equal gain (λ≈2.25); Samuelson & Zeckhauser (1988) on status-quo bias. To a blocker, change = a certain personal loss, and opposition is rational self-protection. (Detailed in the "find & amplify the pain" and "the buyer's brain" pieces on this site.)
  • Psychology · reactance (hard evidence): Brehm's (1966) reactance theory — when people feel their freedom of choice is threatened, they push back and lean harder toward the threatened option. This is why "persuading a blocker to drop their opposition" head-on usually backfires: the more you push, the more they resist. (Cross-ref psychology, on resisting manipulation.)
  • Takeaway · neutralize beats defeat: the goal isn't to out-argue the blocker, it's to make "change" no longer a net loss for them — take on the work they fear, protect their face and turf, leave the decision with them. Remove the loss and the fuel for opposition is gone.

The line: mapping the chain and neutralizing a blocker are both about getting the right value to the right ears — not about going around the blocker to tell tales behind their back, or manipulating internal politics to squeeze them out. Backstabbing may bypass one person short-term, but long-term it destroys the whole org's trust in you, and once discovered, even your champion walks. The clean way: openly get the blocker's legitimate concerns heard and resolved.

  • What is this person opposing me actually afraid of losing? Work, power, face, or a relationship?
  • Is their stated reason ("won't work") the same as their real concern?
  • Can I directly lift off the thing they fear (we take on migration / write it into the SLA / protect their turf)?
  • Am I openly resolving their concern, or trying to go around them and take them out behind their back?
Idiomatic phrasing

"What's at stake for them personally if this changes?"

Don't win the argument and lose the person.

Neutralize the blocker; don't try to defeat them.

Your Day 10 Action

Pick something you're currently pushing where more than one person decides (a B2B deal, a cross-team proposal, even convincing your whole family to make a decision together). Stop staring at the one person you click with, and draw the whole decision chain.

Step 1 · Draw the chain: on paper, list — who pays and decides (economic buyer), who uses it daily (user), who can veto (gatekeeper), who's quietly opposing (blocker), who might speak for you (champion). Which box is empty right now? An empty box is your risk.

Step 2 · Rewrite the pitch per role: write the economic buyer a line on "return / payback / risk," the user a line on "which grind this kills," the gatekeeper a line on "how compliance / security is guaranteed." Same product, three translations.

Step 3 · Test the champion: to the person most behind you, make one concrete small ask (introduce me / forward a one-pager / set up a 15-minute three-way). Watch whether they move — those who act are champions, those who dodge are cheerleaders.

Step 4 · Read the blocker: find the person most likely to oppose, ask yourself "what do they fear losing," then think of one way to lift that loss directly (we take it on / write it into the contract / protect their turf).

Boundary reminder: this is about getting the right value to the right ears, not about backstabbing or playing internal politics. Once you've mapped the chain, the finest move is always to openly get every person's legitimate concern caught — including the one opposing you.
Think It Through
1. I only sell something small / one-on-one — where would I get that many decision makers? Is this only for big B2B?
The roles are universal; sometimes several roles collapse into one person. Sell a used phone to an individual and they're both economic buyer and user, a chain of one — so for you this piece means "don't ignore the invisible third party": will they go ask a savvy friend (gatekeeper)? Does the partner who manages the money have to say yes (economic buyer)? Plenty of "we chatted great but it didn't close" personal deals die on one invisible role you didn't cover. Conversely, the bigger the deal — and the more it's about "selling yourself" (a job needs HR + hiring manager + boss; fundraising needs the partners) — the longer the chain and the more this is a life-or-death line. So: small deals use it as a gap check (any hidden deciders?), big deals use it as a battle map.
2. How do I climb up to the real decider without offending my enthusiastic contact?
The core is leverage, not bypass — use them as a guide and climb through them, not ditch them and stab straight to the boss. Three moves: (1) Give a reason: don't say "I want to go over you to your boss," say "I want to help you stock up on ammo and save you relaying it — could we loop in whoever owns the budget for one round?" You're helping them, not sidelining them. (2) Keep them in the room: when you set the three-way, bring them along, so they feel they made it happen rather than got cut out. (3) Use it to verify they're a champion: if they stall hard the moment you ask for an intro to the boss, that itself says they either lack influence or fear you stealing credit — and that's key intel. A real champion is eager to introduce you upward, because it landing reflects well on them too. Leverage in the open rarely offends; sneaking around behind them is what hurts.
3. Mapping the chain, finding a champion, neutralizing a blocker — isn't this teaching me office politics and manipulation?
The dividing line is whether you want people to see clearly or not. Manipulation is: hiding the truth, sowing discord, telling tales over people's heads, quietly taking the blocker out — making the decision happen under distorted information. This piece teaches the opposite — getting every genuinely relevant person to hear the real value that concerns them, including putting the objector's legitimate worry on the table to be resolved. The economic buyer should see the real ROI, the gatekeeper should confirm real compliance, the blocker's feared workload should really get lifted. What you're doing is routing information to the right people, not distorting it. Simple test: could every step you take be laid on the table and told to everyone, and still hold up? If yes, that's professionalism; if it can't stand daylight and has to be hidden from someone, it's sliding into manipulation. Mapping the chain is letting sunlight into every corner, not scheming in the dark.
4. I found the champion and made the value clear, but the decision just drags. Now what?
"Dragging" is usually not a shortage of reasons — it's a shortage of consensus + process momentum — the very side effect of a bigger chain: with more people, no one wants to own the "decide" alone, so they collectively, silently stall (the diffusion of responsibility from principle 1). Three fixes: (1) Help the champion build consensus: don't expect everyone to agree live in one big meeting; help the champion align the key people (especially gatekeeper and blocker) privately, one by one, so the meeting is just a rubber stamp. (2) Ask about the decision process itself: "From here to signature, which gates are left, and roughly what's the pace?" — forcing a vague "we'll see" into a roadmap with milestones. (3) Give one real reason for timing: not a fake urgency to scare them (that's the red line from the pain-digging piece), but a genuinely existing window (budget cycle, a price-increase date, their own go-live schedule). Delay mostly dies from "no reason it has to be now" — find that real reason, or honestly admit the timing isn't right and agree on a trigger to come back.