<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Leadership-Decisions on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/leadership-decisions/</link><description>Recent content in Leadership-Decisions on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 29 Sep 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/leadership-decisions/index.xml" rel="self" type="application/rss+xml"/><item><title>The Workaround Is the Warning</title><link>https://drlongnecker.com/blog/2026/09/workaround-is-the-warning-when-to-part-ways/</link><pubDate>Tue, 29 Sep 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/09/workaround-is-the-warning-when-to-part-ways/</guid><description>&lt;p&gt;Almost every team I&amp;rsquo;ve worked with has quietly built a workaround around &lt;em&gt;someone&lt;/em&gt;. A peer double-checks a certain person&amp;rsquo;s numbers before anyone else sees them. A task that used to go to the whole group now routes around one desk, and nobody ever said so out loud.&lt;/p&gt;
&lt;p&gt;Nobody calls it a workaround, either. It gets a smaller label, like &amp;ldquo;just being careful&amp;rdquo; or &amp;ldquo;that&amp;rsquo;s how we do it now.&amp;rdquo; By the time it has a name, the decision it covers has usually been waiting a while.&lt;/p&gt;</description></item></channel></rss>