influencing-without-authority
Influencing Without Authority
Get people to move in your direction when you can't simply tell them to.
How to use
/influencing-without-authorityApply 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
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1