# Orientation Before Persuasion Outperforms a Sharper Argument ## Claim I get further trying to influence someone once I've named my own position and genuinely listened for theirs than I ever do by sharpening the argument itself. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds for non-urgent, relationship-preserving asks where there's time to orient before acting. - Breaks down under real time pressure (incident response, launch-day calls) where there may be no room for the outward-listening step before a decision is needed. - Does not claim that a sharper argument is worthless — only that orientation (inward, then outward) does more of the persuasive work than argument quality alone. ## Evidence The source piece traces most "bad influence moves" — anxious follow-up messages, premature escalation to a manager — directly to skipping self-orientation before attempting to persuade. It frames resistance as diagnostic information (a busy colleague, an undisclosed constraint, missing context) rather than a signal the requester is wrong, and argues the fix is sequencing (orient, then map current state to destination, then ask) rather than a better-argued case. > "The best first step in influence is not logic. It's understanding the current state." ## Links - [[Agent Tooling Earns Adoption by Augmenting Existing Workflows]] — because extends; both claims say the surrounding approach (sequencing, packaging) moves outcomes more than the core content/argument itself - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — because applies-in; influence-without-authority as an operator skill - [[3. Resources/MOCs/DevRel MOC]] — applies-in: Joins the communication and influence cluster; fit is loose. ## Tests / falsifiers - Compare response time and follow-up count on requests where the sender wrote down their own position first vs. requests sent without that step, holding request content constant. - Test under real time pressure specifically: does skipping the outward-listening step in an incident-response context produce worse outcomes than skipping it in routine work — if not, the "breaks under pressure" scope condition is wrong. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/The engineering leadership skill no title can give you]] — LeadDev article on influence-without-authority as engineering organizations flatten.