<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Organizational-Dynamics on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/organizational-dynamics/</link><description>Recent content in Organizational-Dynamics on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 30 Apr 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/organizational-dynamics/index.xml" rel="self" type="application/rss+xml"/><item><title>Influence Without the Org Chart</title><link>https://drlongnecker.com/blog/2026/04/product-influence-without-authority-senior-leadership/</link><pubDate>Thu, 30 Apr 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/04/product-influence-without-authority-senior-leadership/</guid><description>&lt;p&gt;Somewhere out there, a product team just shipped a roadmap that engineering will build to spec and no further. The PM had the authority to mandate it, so they did. The features will exist. Nobody will volunteer creative problem-solving on top of them.&lt;/p&gt;
&lt;p&gt;Coming into product leadership from a technical background, the structural misalignment takes a while to register. You&amp;rsquo;re accountable for outcomes that depend on engineering, design, legal, and marketing — almost none of which report to you. You can request and occasionally mandate. What you can&amp;rsquo;t do is mandate your way to good outcomes in work that depends on judgment and discretionary effort from people who had no input in shaping what they&amp;rsquo;re building.&lt;/p&gt;</description></item></channel></rss>