Power and Influence Mapping: Finding Who Really Decides the Deal

An org chart tells you who reports to whom. It does not tell you who can sign, who can stop a deal with one sentence in a meeting you are not invited to, or whose opinion the signer quietly trusts. Power structure and influence mapping is the skill of drawing that second, invisible chart, and a Solution Engineer is often better placed to draw it than anyone else on the deal team.

Two maps, not one

The SE Ignite skills inventory describes this skill as two parallel tasks: identifying and gaining access to the true economic buyer who holds the budget, and mapping the informal network of technical influencers who can veto the deal. Both matter, and they rarely overlap.

• The formal map shows budget ownership, approval levels and reporting lines. It answers: who can say yes?
• The informal map shows trust, expertise and history. It answers: who can say no, and who do the decision-makers listen to?

Why SEs see the informal map first

Account Executives usually spend time with buyers and sponsors. SEs spend time with architects, engineers, security reviewers and administrators: the people whose technical judgement the buyer relies on. In workshops and evaluations you see who others defer to, who asks the hardest questions, and whose doubts make the room go quiet. That is influence, and it is visible to whoever is paying attention.

Roles to identify on every deal

Role	What they control	Question to ask yourself
Economic buyer	Budget and final approval	Have we heard their priorities directly, not second-hand?
Technical decision-maker	The architecture recommendation	What would make them recommend us, and what would make them object?
Technical influencer	Credibility with decision-makers	Whose opinion is quoted when we are not in the room?
Potential blocker	A veto through risk, security or preference	What do they lose if this project succeeds?
Champion	Internal advocacy	Do they actually have political capital, or only enthusiasm?

Questions that reveal power without asking for it directly

Asking “Who is the decision-maker?” usually gets a polite but incomplete answer. Process questions work better:

• “When your team chose its last major platform, how did that decision actually get made?”
• “Who will need to be comfortable with the architecture before this goes for approval?”
• “If security or infrastructure had concerns, at what point would they raise them?”
• “Whose budget does this come out of, and does that person need to see the business case?”
• “Is there anyone who preferred a different approach last time we discussed this?”

Gaining access to the economic buyer

Many SEs assume the economic buyer is the Account Executive’s job. In practice, the SE often holds the best reason for a meeting: a technical finding that has business consequences. Offer something worth the buyer’s time, such as a short summary of what discovery uncovered and what it means for cost, risk or speed. Ask your champion to sponsor the introduction, and coordinate with your Account Executive so the request comes from the deal team, not from you alone.

Handling the informal veto

An influential architect who prefers another approach can quietly end a deal. Treat potential blockers as experts, not obstacles: involve them early, ask for their criteria, and invite them to challenge the design. Influencers who helped shape a solution are much less likely to veto it. If their concern is legitimate, it is better to learn it in a working session than in a rejection email.

Keep the map alive

Influence changes as deals progress. People join, leave, change role or lose interest. Review the map at each stage gate with your Account Executive and update it after every meeting where you learned something new about how decisions are made.

Common mistakes

• Single-threading. Relying on one contact, however enthusiastic, leaves the deal exposed if they move on or lack authority.
• Confusing title with power. Seniority does not always mean influence over a technical choice.
• Going around people. Bypassing a contact to reach their boss damages trust. Ask to be brought along instead.

Mapping power and influence is one of the deep discovery and qualification skills in the SE Ignite curriculum: a vendor-neutral capability that works in any technology market. The curriculum is free to access for SEs who want to practise it with structure.