influence

Coordinate stakeholder influence to secure buy-in for engineering initiatives.

104|7|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/manager-dot-dev/manager-skills --skill influence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: influence
Source: https://github.com/manager-dot-dev/manager-skills/tree/main/skills/influence
Command: npx skills add https://github.com/manager-dot-dev/manager-skills --skill influence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Engineering managers often face resistance when pursuing initiatives without direct authority. This skill provides a structured approach to influence, align stakeholders, and secure buy-in more reliably.

Core Features & Use Cases

  • Stakeholder mapping: identify who needs to agree, who can block, and who should be informed.
  • Positioning and messaging: tailor messages to each stakeholder's values and concerns.
  • Actionable playbooks: practical methods (Nemawashi, Decoy Pricing, Reverse Psychology, LMDTFY, Engineered Serendipity) with concrete steps for common scenarios like headcount requests or cross-team initiatives.
  • Risk awareness: anticipate political and relational risks and plan mitigations.

Quick Start

Create a concise stakeholder plan for securing buy-in on an engineering initiative, including a stakeholder map, the preferred influence method, a talking script, and identified risks.

Frequently Asked Questions about influence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I secure stakeholder buy-in for engineering initiatives without direct authority?

Stakeholder mapping for engineering initiatives involves identifying who needs to agree, who can block, and who should be informed. This structured approach ensures you address key decision-makers and potential blockers effectively during buy-in efforts.

What is the best way to get headcount approvals or cross-team initiative buy-in?

To plan a stakeholder strategy for roadmap changes, identify the preferred influence method, tailor your message to stakeholder concerns, create a talking script for the next discussion, and outline relational or political risks with planned mitigations.

How do I map stakeholders for an engineering organization's policy decisions?

Stakeholder mapping for policy decisions involves identifying who needs to agree, who can block, and who should be informed. This structured approach ensures you address key decision-makers and potential blockers effectively during buy-in efforts.

What influence methods work for getting engineering roadmap changes approved?

Influence methods for roadmap changes include Nemawashi, Decoy Pricing, Reverse Psychology, LMDTFY, and Engineered Serendipity. These playbooks provide concrete steps to position your message and align stakeholders across the engineering organization.

How do I prepare for political and relational risks when proposing engineering initiatives?

To prepare for political and relational risks, identify potential blockers during stakeholder mapping and plan mitigations. This risk awareness is built into the influence strategy to anticipate resistance and secure reliable buy-in.