apply-power-mapping

Apply Power Mapping

Map actual decision authority and influence separately from the formal org chart — because nominal titles and actual power routinely diverge, and engagement strategies built on formal hierarchy systematically fail when real decision-makers are elsewhere.

Why This Is Best Practice

荣枯鉴·制御篇 (~10th century AD, attributed to Feng Dao):

强者为尊，知其所处则可制之。

"The strong are accorded respect. Know where they are positioned, and you can work with them."

Why best: The 荣枯鉴 observes that in every organization, effective power resides with those who actually command resources, loyalty, and decisions — not necessarily with those who hold the titles. The failure to distinguish nominal authority from actual power is one of the most consistent causes of strategic failure: the leader engages the wrong person, misses the real objection, or builds an approach based on a map that doesn't match the territory. Knowing where actual power sits allows you to work with the actual decision-making structure rather than the theoretical one.

Challenger Sale (Adamson & Dixon, CEB, 2011): CEB's research across 1,400+ B2B sales organizations found that average enterprise technology deals now involve multiple stakeholders with different roles: economic buyer (budget authority), technical buyer (evaluates fit), user buyer (operates the solution), champion (advocates internally), and blockers (can veto). Sales teams that focused only on the economic buyer — the formal authority — won significantly fewer deals than teams that mapped and engaged the full stakeholder landscape. The "Challenger" approach includes explicit power-mapping as a core methodology: identify who influences the decision, who has veto power, who the champion is, and what each stakeholder's specific concern is. Standard training at most Fortune 500 enterprise sales organizations.

Gartner B2B Purchase Research (2015–2023): Gartner's ongoing research on enterprise purchasing behavior consistently finds that the average B2B technology deal involves 6–10 stakeholders, and purchase decisions are rarely made by a single economic buyer. Key finding: 77% of B2B buyers describe their purchase process as very complex or difficult, with the primary complexity coming from stakeholder alignment — not vendor selection. Gartner's "Buying Job" framework (sense-making, supplier evaluation, financial assessment, consensus building) explicitly requires mapping the decision-making structure before engaging. Standard in Gartner's advisory practice; taught in their sales effectiveness programs used by thousands of enterprise sales teams.

Organizational Network Analysis (ONA — Deloitte, IBM, CrossLead): ONA is the systematic study of who communicates with whom, who is consulted for decisions, and where informal influence actually flows in an organization. Deloitte and IBM use ONA to help clients identify "hidden influencers" — employees who don't have formal authority but whose opinion is sought widely on decisions. CrossLead (founded by former SEAL Team Six commanders) uses network analysis for military unit effectiveness. The consistent finding: in most organizations, 3–5% of employees account for 20–25% of all information flow and decision influence, and these people are often not in senior positions. Identifying them changes engagement strategy significantly.

Jeffrey Pfeffer — "Power: Why Some People Have It and Others Don't" (Stanford GSB, 2010): Pfeffer's research on organizational power identifies the sources of actual power: control of scarce resources, control of information flow, centrality in networks, building of coalitions, and visibility with key decision-makers. His core finding: formal authority is one source of power, but often not the most important one. The map of actual organizational power differs from the org chart in predictable ways: informal power concentrates with those who control resources, information, and access — regardless of title. Taught at Stanford GSB, Harvard Business School, and embedded in executive leadership programs globally.

PMI PMBOK — Stakeholder Management (standard, 2017+ editions): The Project Management Body of Knowledge dedicates an entire knowledge area to stakeholder identification and management, explicitly including the mapping of influence levels, interest levels, and engagement requirements for each stakeholder independently of their formal position. Standard in project management certification (PMP, PRINCE2) globally; used in every major professional services firm and capital project.

Why distinct from apply-key-person-targeting: apply-key-person-targeting identifies THE single most critical decision-maker in a specific competitive situation and concentrates effort there. apply-power-mapping is a prerequisite that must precede key-person-targeting: before you can identify which person is most critical, you need to understand the full power distribution. Power-mapping also produces a different output — not a single target, but a structured map of multiple actors, their domains of authority, their dependencies on each other, and the optimal engagement sequence.

Adopted by: CEB/Gartner Challenger Sale methodology (standard training at most Fortune 500 enterprise sales organizations); Gartner advisory practice and sales effectiveness programs (used by thousands of enterprise sales teams); Deloitte and IBM Organizational Network Analysis (ONA) practice; CrossLead (military-derived network analysis for unit effectiveness); PMI PMBOK (PMP and PRINCE2 certification globally); Stanford GSB and Harvard Business School (Pfeffer's "Power" framework in executive leadership programs).

Impact: CEB's research across 1,400+ B2B sales organizations found that teams mapping and engaging the full stakeholder landscape — including hidden influencers and blockers — won significantly more enterprise deals than teams engaging only the formal economic buyer; Gartner documents that 77% of B2B buyers describe their purchase process as very complex due to stakeholder alignment, confirming that formal-hierarchy-only engagement systematically fails; ONA research shows 3–5% of employees account for 20–25% of all decision influence, meaning strategies built without identifying these actors miss the majority of actual influence flow.

Steps

1. Map all stakeholders who touch the decision. List every person who has any of the following: budget authority, technical veto, operational input, formal approval requirement, informal opinion-forming role, or direct access to the economic decision-maker. Cast wide initially — it is easier to remove a stakeholder from the map after confirming their non-involvement than to discover a missed stakeholder after your strategy has deployed.

2. Classify each stakeholder on two dimensions: formal authority and actual influence. For each person on the list, assess:

   • Formal authority: what do they formally have the right to approve, reject, or require? (Org chart, procurement rules, sign-off thresholds)
   • Actual influence: who does the actual decision-maker consult? Whose concerns, when raised, reliably change outcomes? Who does the economic buyer defer to on specific topics (technical, operational, financial)?

   These two dimensions produce four types: (1) high authority + high influence = engage first, (2) high authority + low influence = formally required, engage sufficiently, (3) low authority + high influence = hidden influencers, often missed, critically important, (4) low authority + low influence = do not invest.

3. Identify the actual decision-maker, which may not match the nominal one. In many organizations, the person with formal sign-off authority has already delegated the real decision to a trusted subordinate, advisor, or committee — and will sign whatever that person recommends. In others, the nominal committee makes the decision but one member has de facto veto. Signals that identify the actual decision-maker: who is consulted before the decision is made; who changes the outcome when they raise a concern; who the economic buyer defers to under uncertainty.

4. Map the dependencies between stakeholders. Power structures have topology: some stakeholders influence others. If the technical lead's endorsement is required before the CFO will approve, the engagement sequence must win the technical lead first — even if the CFO has formal authority. Draw the influence chain: who influences whom, in what order, on what topics. The engagement sequence must follow the influence chain, not the org chart.

5. Identify blockers and their specific objections. A blocker is any stakeholder with the ability to veto or slow the outcome, even without formal authority. Identify: who has historically killed similar decisions? Who has expressed concern or skepticism? What is each potential blocker's specific concern (technical risk, budget, political territory, workload impact)? Blockers must be addressed before the decision reaches them — not at the point of rejection.

6. Identify champions and activate them. A champion is a stakeholder with actual influence who is genuinely supportive of your objective. Champions should be leveraged to reach stakeholders you cannot access directly, to translate your proposal into the organization's language and priorities, and to pre-address objections before they reach formal decision meetings. A well-briefed internal champion is more effective than any external presentation.

7. Update the map throughout the engagement. Power maps are not static — people change roles, lose influence, gain it, change their position. Track changes: who has been consulted most recently; who's opinion was sought when an obstacle arose; who is now closer to or further from the actual decision-maker. The most critical power-mapping failure is treating the initial map as fixed and missing the dynamic changes that redirect the real decision.

Rules

• Titles are hypotheses, not facts. A VP title is a hypothesis that this person has significant authority. Verify through observed behavior: does their opinion change outcomes? Does the economic buyer consult them? Treat every title as a starting hypothesis to be tested, not confirmed.
• Low-authority, high-influence stakeholders are the most commonly missed. Because power-mapping instinctively starts with the org chart, these people — the technical expert whose word is trusted, the executive assistant who controls access, the board advisor who shapes thinking — are systematically underweighted. Actively hunt for them.
• Map the topic-specific authority, not general authority. Most stakeholders have authority that is specific to domains (technical decisions, financial decisions, operational decisions). A person with high authority on technology decisions has low authority on commercial terms. Build a domain-specific map, not a general seniority ranking.
• Never engage based on the org chart alone. The org chart describes reporting structure, not decision authority. These overlap significantly at the top of organizations and diverge significantly in the middle and operating layers. Every significant engagement requires its own power map.

Examples

Enterprise sales: A sales team has been engaging the Chief Digital Officer of a prospect organization for 8 months. The CDO is interested, the deal seems close, but it keeps stalling. Power mapping reveals: the CDO cannot approve technology purchases above $500K without sign-off from the CFO; the CFO's trusted advisor on technology is the internal audit team, who has concerns about vendor security practices; the internal audit director has never been contacted by the sales team. Revised engagement: direct outreach to internal audit director, address security concerns proactively, provide SOC 2 documentation. Deal closes within 60 days of engaging the actual blocking stakeholder.

M&A: An acquirer is engaging a target company's CEO and CFO. Term sheet agreed in principle; deal stalls in final stage. Power mapping of target's board reveals: two board members (neither on the M&A committee) have informal veto — the CEO will not proceed without their private endorsement. One has concerns about employee retention; one has concerns about integration timeline. Acquirer arranges informal conversations with both board members, addresses concerns specifically. Deal closes.

Internal initiative: An engineering team proposes a new platform architecture that requires approval from the CTO. The CTO is nominally the decision-maker. Power mapping: the CTO defers to her Principal Engineer on all major architecture decisions; the Principal Engineer has not been briefed on the proposal and has concerns about migration complexity. Engaging the Principal Engineer first, addressing migration concerns with a detailed plan, results in the Principal Engineer advocating the proposal to the CTO. Approval granted.

Organizational change: A new HR leader wants to implement a revised performance management system. Nominal approval path: CHRO and CEO. Power mapping reveals: the SVP of Sales has historically killed HR initiatives that affect his team's compensation structure; three of the longest-tenured functional leaders are informal opinion-formers whose public support or opposition signals to the CEO whether to proceed. Revised approach: brief all three informal opinion-formers privately before any announcement; design the sales compensation carve-out to address the SVP's concern; launch to broad positive reception.

Common Mistakes

• Mapping only the formal hierarchy: The org chart is the starting point, not the map. Stopping at formal titles systematically misses the hidden influencers who often determine outcomes.
• Assuming the map is static: People change positions, lose sponsors, gain influence. Power maps built for a deal or initiative 6 months ago may be significantly outdated. Update continuously.
• Engaging the wrong level: Both too-high (engaging the CEO when the real decision is made by a VP) and too-low (engaging a manager when a C-suite champion is needed) produce failure. Match the engagement level to the actual power level.
• Neglecting blockers until they block: Blockers who are identified but not engaged before the decision point produce last-minute rejections that are very difficult to reverse under time pressure. Identify blockers early; address their concerns before the formal decision stage.
• Mapping without acting: A detailed power map that doesn't change the engagement strategy produces no value. The output of power mapping is a revised engagement plan — different people to engage, different sequence, different messages for each stakeholder's specific concerns.