Influencing Without Authority

A product manager wants the flashy feature: an LLM assistant on the checkout page, demoed to the board next month. The engineer knows what the demo will not show — every request adding two seconds of latency to the one page where seconds are money. Here is the trap: the engineer is right, and rightness is not the game. She cannot veto the feature; she can only persuade someone who does not report to her, does not share her vocabulary, and is measured on things she has never had to care about. Her first instinct — explain the architecture, louder — has failed everywhere it has ever been tried, from engineering floors to school staff rooms to translation agencies negotiating deadlines with sales teams. What works is a different craft entirely: making your concern land inside the other person's world, arriving with evidence instead of opinion, and doing the real persuading before the meeting where the decision gets made.

Nothing in the loop requires an org chart or a codebase. Teachers move heads, interpreters move agencies, and junior engineers move roadmaps with exactly these four moves — because influence without authority is not a workaround for lacking power; it is what most professional persuasion has been all along.