<story><title>Leverage Points: Places to Intervene in a System</title><url>http://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/</url></story><parent_chain></parent_chain><comment><author>rpeden</author><text>This is long, and it&amp;#x27;s a lot to digest, but I find it pretty applicable to software systems.&lt;p&gt;And it&amp;#x27;s funny how often we see software teams twiddling at the edges of a system, spending a ton of time on things than don&amp;#x27;t meaningfully impact the system&amp;#x27;s overall success. To give a concrete example, I&amp;#x27;ve seen teams with crappy, slow, and unnecessarily expensive system architectures spend a &lt;i&gt;huge&lt;/i&gt; amount of time on decisions like &amp;quot;should we use Vue, or React?&amp;quot;.&lt;p&gt;Granted, there will be occasional times when your front-end framework &lt;i&gt;is&lt;/i&gt; a make-or-break leverage point. But usually it&amp;#x27;s not. Maybe the problem is that the teams who are doing this yak shaving aren&amp;#x27;t authorized to alter the overall system. And so they spend their time arguing about the things they &lt;i&gt;can&lt;/i&gt; change. :)</text></comment>
<story><title>Leverage Points: Places to Intervene in a System</title><url>http://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/</url></story><parent_chain></parent_chain><comment><author>plainOldText</author><text>Worth nothing Donella H. Meadows has authored a highly rated book on systems, &lt;i&gt;Thinking in Systems: A Primer&lt;/i&gt;.</text></comment>