Skip to content

afeezadebayo/communication-presentations-skills / persuasion-influence

persuasion-influence

Verified

Influence decisions ethically, especially without authority: the ask and smallest version, stakeholder maps and power-interest grids, interests behind positions, framing around shared goals, evidence and credibility, pre-wiring, messengers and channels, Cialdini principles used ethically, objection handling, principled negotiation and follow-through. Use whenever someone needs to get a proposal approved, influence senior leaders or peers, manage up, win support across teams, handle objections, negotiate resources or build buy-in for change.

Persuasion and Influence

Most important work needs other people to agree: a budget approved, a priority changed, a process adopted, a partner convinced. Many capable people lose these moments not because their idea is weak but because they argue from their own view, approach the wrong person at the wrong time, ignore what the other side cares about or rely on one meeting to change minds. Research and practice point to a few reliable foundations. Aristotle described credibility (ethos), emotion (pathos) and logic (logos). Robert Cialdini's research on influence identified principles such as reciprocity, commitment and consistency, social proof, authority, liking, scarcity and unity. [Reference, Cialdini, Influence] Roger Fisher and William Ury's principled negotiation separates interests from positions and stresses knowing your best alternative. [Reference, Getting to Yes]

This skill helps people influence decisions ethically, especially without formal authority: mapping stakeholders, understanding their interests and objections, framing proposals around shared goals, building evidence and credibility, choosing the right channel and sequence, handling resistance, negotiating trade-offs and securing commitment that lasts.

Operating principles

  1. Start from their interests. People agree to what solves their problems, not yours.
  2. Earn credibility before asking. Track record, expertise, preparation and fairness make ideas easier to accept.
  3. Logic, emotion and trust together. Data persuades the head; stories and stakes move people; trust lets both land.
  4. Influence is a process, not a meeting. Pre-wire key people one to one before group decisions.
  5. Ethical only. Never mislead, manipulate, invent urgency or hide downsides; influence that relies on tricks destroys trust.
  6. Make yes easy. Small first steps, clear asks and low-risk pilots.

Stakeholder map

StakeholderRole in decisionCurrent viewWhat they care aboutConcernsBest messengerNext step
CFOApproverScepticalCost, payback, riskBudget overrunFinance partnerOne-to-one with payback model
Head of salesInfluencerSupportivePipeline, rep timeDisruption in Q4Sales ops leadAsk to co-present
IT leadMust agreeNeutralSecurity, workloadIntegration effortMeShare security review

Use a power and interest grid: manage closely those with high power and high interest, keep satisfied those with high power and low interest, keep informed those with low power and high interest.

Influence principles in practice (ethical use)

PrincipleEthical applicationAvoid
ReciprocityHelp others with their goals first; share useful workFavours given as hidden debts
Commitment and consistencyAsk for small, public steps that match stated goalsTrapping people in commitments
Social proofShow what similar teams or companies did and their resultsInventing or exaggerating adoption
AuthorityBring expert evidence or credible sponsorsName-dropping without substance
LikingBuild real relationships and common groundFlattery
ScarcityExplain real deadlines or opportunity costsFalse urgency
UnityFrame the shared identity and goal ("our customers", "our team")Us-versus-them pressure

When to use, and when not to

Use it for getting proposals approved, changing priorities, influencing peers and senior leaders, cross-team projects, managing up, negotiating resources and winning support for change.

Don't use it to pressure people into decisions against their interests, to manipulate, or where formal processes (procurement, HR, legal) must decide on merit.

Inputs

  • What you want decided or changed, and by when.
  • Who decides, who influences and who must agree.
  • What you know about each person's goals, pressures and views.
  • Evidence: data, examples, pilots, expert input.
  • Your credibility and relationships with each stakeholder.
  • Alternatives if the answer is no.

Workflow

Step 1. Define the ask precisely

What decision, from whom, by when, and the smallest acceptable version (for example a pilot instead of a full rollout).

Step 2. Map stakeholders

Roles in the decision, current views, interests, concerns and relationships between them.

Step 3. Understand interests behind positions

For each key person, ask: what are they measured on, what are they worried about, what would make this a win for them?

Step 4. Frame around shared goals

Connect the proposal to their priorities: "This cuts onboarding time, which helps the retention target you own."

Step 5. Build the case

Evidence (data, examples, pilot results), a clear story of the problem and the better future, risks with mitigations and the cost of doing nothing.

Step 6. Pre-wire one to one

Talk to key people before the group meeting; listen to concerns; adapt the proposal; ask for their support or at least no surprises.

Step 7. Choose messenger and channel

Sometimes a trusted peer, customer or expert is more persuasive than you. Pick written proposals for analytical audiences and conversations for relationship-driven ones.

Step 8. Handle objections

Acknowledge, ask questions to understand, address the underlying concern, offer options or a smaller first step.

Step 9. Ask clearly and secure commitment

State the ask, confirm the decision and next steps in writing, and give people a role in success.

Step 10. Follow through

Deliver early results, credit supporters publicly and report progress; trust built now makes the next ask easier.

Framing examples

Your viewTheir interestReframed
"We need a new analytics tool"CFO: cost control"Consolidating three tools into one saves £18,000 a year and cuts reporting time"
"Engineering should fix onboarding bugs"CTO: roadmap focus"Two fixes remove 30% of support tickets, freeing engineers from interruptions"
"Marketing needs more budget"CEO: growth target"£20,000 more in paid search adds about 60 qualified meetings toward the Q4 target"

Handling common objections

ObjectionResponse approach
"We don't have budget"Show payback, cost of waiting, or a smaller funded pilot
"Now isn't the right time"Ask what would make it the right time; agree a date or trigger
"We tried this before"Ask what happened; show what is different now
"It's too risky"Name risks, show mitigations, propose a reversible test
"Not my priority"Link to their goals or find who it is a priority for
"I need to think about it"Ask what information would help; agree when to reconnect

Negotiating trade-offs

  • Know your best alternative if no agreement is reached, and theirs.
  • Separate the person from the problem; stay respectful under pressure.
  • Trade things that are cheap for you and valuable for them.
  • Use objective criteria (benchmarks, data, policies) rather than will.
  • Write down agreements and owners.

Edge cases and judgement calls

SituationWhat to do
No formal authorityBuild coalitions; borrow authority from sponsors; show results first
Senior leader opposesUnderstand their concern privately; adapt; escalate only with respect and data
Group decision with competing interestsPre-wire, find shared goals, offer options, let the decider decide
Repeated rejectionAsk for feedback; reconsider the idea or timing; build evidence with a small test
Cultural differencesAdjust directness, hierarchy and pace; learn local norms
Ethical doubtStop; influence that requires hiding information is the wrong path

Handoffs to related skills

  • Presentations to persuade: presentation-storyline and pitch-presentations
  • Data as evidence: data-storytelling
  • Hard conversations: difficult-conversations
  • Decision meetings: the Meetings and Calendar decision-meetings skill
  • Written proposals: the Workplace Writing proposals and memos-one-pagers skills

Worked example

A product operations manager wanted leadership to fund a customer onboarding redesign. Her first attempt, a 20-slide deck in the quarterly review, was deferred. Using this skill she mapped stakeholders: the CFO cared about payback, the head of customer success about churn, the CTO about engineering time. She reframed the proposal as a retention lever with a payback estimate, ran a two-week pilot with ten new customers that cut setup time by half, and pre-wired each leader one to one, adjusting the plan to use a contractor so engineering time was protected. The head of customer success co-presented the results. The proposal was approved in the next meeting with a phased budget and a review after one quarter.

Common mistakes

  • Arguing from your own interests.
  • Relying on one big meeting.
  • Ignoring the quiet blocker with veto power.
  • Overstating benefits or hiding risks.
  • Not following through after a yes.

Output format

1. The ask and smallest acceptable version
2. Stakeholder map with interests and concerns
3. Framing for each key stakeholder
4. Evidence and case summary
5. Pre-wiring plan (who, when, what)
6. Objections and responses
7. Commitment and follow-through plan

Self-check before you answer

  • Is the proposal framed around the decision makers' interests?
  • Are key people pre-wired before the group decision?
  • Are evidence and risks presented openly?
  • Are all tactics ethical, with no false urgency or hidden downsides?

Created by Afeez Adebayo, Marketing, SEO & Growth Expert Website: https://afeezadebayo.com LinkedIn: https://www.linkedin.com/in/afeez-adebayo/ X: https://x.com/za_icon Source: https://afeezadebayo.com/skills-md/productivity/communication-presentations/persuasion-influence/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall