How do you identify stakeholders and their real interests?

Map who is affected, ask questions to surface hidden needs, and document the underlying interests driving each stance.

What if interests cannot be fully aligned?

Look for overlapping goals, frame around shared outcomes, and attempt direct resolution before escalating to leadership.

How do you demonstrate credibility over time?

Deliver on commitments, do thorough homework, share credit publicly, and publicly track your predictions and outcomes.

influencing-without-authority

npx machina-cli add skill Dragoon0x/Product-Skills/influencing-without-authority --openclaw

Files (1)

SKILL.md

2.5 KB

Influencing Without Authority

Get people to move in your direction when you can't simply tell them to.

How to use

/influencing-without-authority Apply influence constraints to this conversation.
/influencing-without-authority <situation> Develop an influence strategy for the described situation.

Constraints

Interest-Based Alignment

MUST frame proposals in terms of what matters to the OTHER person, not yourself
MUST uncover each stakeholder's real interests before arguing your position
SHOULD find where interests overlap and lead with shared ground
NEVER argue positions. Argue interests. Positions are rigid; interests create room.
MUST address conflicting interests explicitly rather than pretending they don't exist

The Pre-Wire

MUST have 1:1 conversations with key stakeholders before the group decision meeting
SHOULD understand their concerns and incorporate feedback before the room
Walk into the meeting with no surprises. If someone objects, you should have known.
NEVER ambush stakeholders with decisions they haven't had time to process

Credibility Building

Consistently deliver on commitments. This is the foundation of influence.
MUST do the homework — people follow PMs who clearly understand the problem space
SHOULD share credit generously and publicly
Track your predictions publicly. Being right builds trust over time.
MUST show you understand the other person's domain before asking them to change course

Disagreement Handling

MUST push back without creating enemies. Disagree with the idea, not the person.
SHOULD anticipate objections and address them before they're raised
MUST know when to disagree and commit vs. when to escalate
NEVER default to escalation when you haven't tried direct resolution first

Anti-Patterns

The Bulldozer: pushing your agenda without listening. Wins battles, loses wars.
The People-Pleaser: agreeing with everyone to avoid conflict. Creates misalignment.
The Escalation Default: running to leadership at the first sign of resistance
Influence Without Substance: trying to persuade without the analysis to back it up
The Ambush: springing decisions in meetings without prior discussion

Source

git clone https://github.com/Dragoon0x/Product-Skills/blob/main/skills/alignment-influence/influencing-without-authority/SKILL.md

View on GitHub

Overview

This skill helps you secure buy-in and align diverse stakeholders when you can't command them. It centers on framing around others' interests, 1:1 pre-wiring, and credibility building to push a direction or unblock proposals.

How This Skill Works

Frame proposals around stakeholders' real interests and surface their concerns. Conduct 1:1 pre-wires with key players before group decisions so meetings start from a place of alignment. Build credibility over time by delivering commitments, doing the homework, sharing credit, and publicly tracking outcomes.

When to Use It

Pushing a direction without executive authority
Navigating conflicting stakeholder interests to find common ground
Unblocking a proposal that keeps getting blocked in group meetings
Pre-wiring decisions with key stakeholders in 1:1s before a group decision
Building credibility over time to influence cross-functional teams

Quick Start

Step 1: Identify stakeholders and map their real interests.
Step 2: Hold 1:1 conversations to pre-wire concerns and gather feedback.
Step 3: In group settings, frame the proposal around shared ground and commit to concrete actions.

Best Practices

Frame proposals around the other person's real interests, not your own
Conduct 1:1 pre-wires with key stakeholders before group decisions
Do the homework and demonstrate domain understanding; track predictions publicly
Disagree on ideas, not people; prepare objections in advance
Avoid anti-patterns like bulldozing, people-pleasing, and ambushes

Example Use Cases

A product manager reframes a feature request in terms of customer value and technical feasibility, aligning sales and engineering around shared goals.
Before a roadmap review, the PM holds 1:1s with operations, security, and legal to surface concerns and incorporate feedback.
A leader publicly tracks forecast accuracy to earn trust while proposing a new cross-functional initiative.
During a docking project dispute, the team focuses on the underlying business objective rather than personal positions.
Instead of ambushing a decision in a meeting, the team pre-discusses options in pre-meetings to surface issues.

Frequently Asked Questions

Add this skill to your agents