<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Leadership on Andrew Healey</title><link>https://healey.io/categories/leadership/</link><description>Recent content in Leadership on Andrew Healey</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>© 2026 Andrew Healey</copyright><lastBuildDate>Tue, 29 Sep 2026 08:06:18 -0500</lastBuildDate><atom:link href="https://healey.io/categories/leadership/index.xml" rel="self" type="application/rss+xml"/><item><title>Kanter's Law: everything can look like a failure in the middle</title><link>https://healey.io/writing/kanters-law-everything-can-look-like-a-failure-in-the/</link><pubDate>Tue, 29 Sep 2026 08:06:18 -0500</pubDate><guid>https://healey.io/writing/kanters-law-everything-can-look-like-a-failure-in-the/</guid><description>&lt;p&gt;Kanter&amp;rsquo;s Law: everything can look like a failure in the middle. Starship launching, reaching orbit, and coming home yesterday was a good reminder that the middle is where we make our money. It never looks like progress while you&amp;rsquo;re standing in it. Too many of us skip it now, because a polished product page, a quick dashboard, or kneejerking to Claude or ChatGPT takes a few minutes before we ask if anyone actually needs the thing. Meanwhile an HVAC tech who bet everything on her own shop is spending another night away from her family to get somebody&amp;rsquo;s air back on, and she doesn&amp;rsquo;t need one more tool in her inbox. Before you chase the next one, ask what problem you&amp;rsquo;re actually trying to solve.&lt;/p&gt;</description></item><item><title>This week is the anniversary of a boring sounding document that rewrote the map of American infrastructure</title><link>https://healey.io/writing/today-is-the-anniversary-of-a-boring-sounding-document-that/</link><pubDate>Sun, 17 May 2026 11:26:19 -0500</pubDate><guid>https://healey.io/writing/today-is-the-anniversary-of-a-boring-sounding-document-that/</guid><description>&lt;p&gt;This week is the anniversary of a boring sounding document that rewrote the map of American infrastructure. On May 19, 1857, a chemist named Lammot du Pont was granted U.S. Patent No. 17,321 for an &amp;ldquo;Improvement in Gunpowder.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;Before that patent, the American industrial machine had a single point of failure. Gunpowder needed potassium nitrate, and the global supply was controlled by the British Empire, sourced from India. Want to blast a tunnel through a mountain or mine the coal that fed your factory? You were at the mercy of a foreign supply chain and whatever geopolitical wind was blowing that month.&lt;/p&gt;</description></item><item><title>Building in isolation doesn't fail dramatically, but quietly drifts</title><link>https://healey.io/writing/building-in-isolation-doesnt-fail-dramatically-but-quietly-drifts/</link><pubDate>Fri, 15 May 2026 07:44:04 -0500</pubDate><guid>https://healey.io/writing/building-in-isolation-doesnt-fail-dramatically-but-quietly-drifts/</guid><description>&lt;p&gt;Building in isolation doesn&amp;rsquo;t fail dramatically, but quietly drifts.&lt;/p&gt;&#10;&lt;p&gt;You stop seeing what&amp;rsquo;s obvious to people outside your building or corporate bubble. Your assumptions get set in concrete and our blind spots become strategy.&lt;/p&gt;&#10;&lt;p&gt;My go-to sources:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&#10;&lt;p&gt;Private operator communities and industry Slack groups. The conversations are different when there&amp;rsquo;s no sales pitch attached.&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;&#10;&lt;p&gt;Practitioner podcasts. Not the polished keynote, large org, or marketing fluff. The ones where someone walks through what broke and what it cost them.&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;&#10;&lt;p&gt;Public competitor research. Not the thought leader, gatekept reports. LinkedIn job posts, tech stack trackers, review sites, hacker news, curated twitter feeds. What a company is hiring for tells you where they think they&amp;rsquo;re going.&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;/ol&gt;</description></item><item><title>We have one shot</title><link>https://healey.io/writing/we-have-one-shot/</link><pubDate>Tue, 31 Mar 2026 06:42:03 -0500</pubDate><guid>https://healey.io/writing/we-have-one-shot/</guid><description>&lt;p&gt;We have one shot. Don&amp;rsquo;t squander it.&lt;/p&gt;&#10;&lt;p&gt;I remember spending summers at the town library digging in Popular Science magazines for the latest cool thing. Then the internet put the world&amp;rsquo;s knowledge at our fingertips. It seemed everything was available on IRC. Now, we&amp;rsquo;ve moved from searching for information to natural language conversations with it. What a time to be alive.&lt;/p&gt;&#10;&lt;p&gt;AI has in it the ability to be the ultimate 24/7 professor, handyman, critical feedback loop, or jester. While some focus on doomerism or cryptobro hype cycles, I’m using it to solve automation riddles, pick new shrubs for the garden, write that c++ program I never finished 25 years ago, and deep research on topics impactful to my life and community. Many times, they&amp;rsquo;re things I wouldn&amp;rsquo;t have attempted two years ago.&lt;/p&gt;</description></item><item><title>The context trap</title><link>https://healey.io/writing/the-context-trap/</link><pubDate>Tue, 20 Jan 2026 08:27:42 -0600</pubDate><guid>https://healey.io/writing/the-context-trap/</guid><description>&lt;p&gt;The context trap. Netflix popularized microservices. Google invented Kubernetes. Amazon built their own everything. Spotify gave us the squad model.&lt;/p&gt;&#10;&lt;p&gt;These are real innovations from smart people solving real problems. They&amp;rsquo;re also almost certainly wrong for your organization.&lt;/p&gt;&#10;&lt;p&gt;I know that sounds harsh. Let me explain.&lt;/p&gt;&#10;&lt;p&gt;Netflix runs a global streaming platform serving hundreds of millions of users. Their engineering team is measured in thousands. When a monolithic architecture became a bottleneck to their ability to deploy independently and scale specific components, microservices made sense. For them.&lt;/p&gt;</description></item><item><title>The cargo cult of "Enterprise"</title><link>https://healey.io/writing/the-cargo-cult-of-enterprise/</link><pubDate>Sat, 17 Jan 2026 07:24:38 -0600</pubDate><guid>https://healey.io/writing/the-cargo-cult-of-enterprise/</guid><description>&lt;p&gt;The cargo cult of &amp;ldquo;Enterprise&amp;rdquo;. From Seattle to Bentonville, I keep hearing this phrase in meetings: &amp;ldquo;That&amp;rsquo;s how they do it at [insert Fortune 500 company].&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;It gets used like a trump card. Like the name itself is evidence. Like having worked somewhere successful means you understand why it was successful.&lt;/p&gt;&#10;&lt;p&gt;Here&amp;rsquo;s the problem. During and after World War II, some Pacific Island communities observed military planes landing with supplies. After the war ended and the planes stopped coming, they built wooden control towers and runways out of straw. They mimicked the forms they had seen, believing these structures would summon more planes. They didn&amp;rsquo;t understand logistics, manufacturing, or global supply chains. They just knew what it looked like when planes showed up.&lt;/p&gt;</description></item><item><title>Stop chasing tools, start measuring maturity</title><link>https://healey.io/writing/stop-chasing-tools-start-measuring-maturity/</link><pubDate>Thu, 15 Jan 2026 08:31:28 -0600</pubDate><guid>https://healey.io/writing/stop-chasing-tools-start-measuring-maturity/</guid><description>&lt;p&gt;Stop chasing tools, start measuring maturity. Here&amp;rsquo;s a pattern I see constantly.&lt;/p&gt;&#10;&lt;p&gt;Team identifies a problem. Team sees a demo of a shiny tool. Team convinces leadership the tool will solve the problem. Tool gets purchased. Tool gets partially implemented. Tool gets blamed when problems persist. Cycle repeats.&lt;/p&gt;&#10;&lt;p&gt;Gartner estimates that 90% of organizations invest in ITSM tools without first assessing their maturity. We buy solutions before we understand where we actually are.&lt;/p&gt;</description></item><item><title>Invest in your own judgement</title><link>https://healey.io/writing/invest-in-your-own-judgement/</link><pubDate>Mon, 12 Jan 2026 10:40:11 -0600</pubDate><guid>https://healey.io/writing/invest-in-your-own-judgement/</guid><description>&lt;p&gt;I&amp;rsquo;ve spent the vast majority of my career in manufacturing. They haven&amp;rsquo;t all been the companies that show up in Harvard Business Review case studies, something I&amp;rsquo;ve come to see that as an advantage.&lt;/p&gt;&#10;&lt;p&gt;When you&amp;rsquo;re not at a company with infinite resources and a thousand engineers, you learn to be deliberate. You accept constraints while still delivering results. No excuses. You can&amp;rsquo;t buy your way out of problems. You can&amp;rsquo;t throw headcount at complexity. You have to understand what actually matters and focus there.&lt;/p&gt;</description></item><item><title>Escaping the hype cycle</title><link>https://healey.io/writing/escaping-the-hype-cycle/</link><pubDate>Fri, 09 Jan 2026 09:34:12 -0600</pubDate><guid>https://healey.io/writing/escaping-the-hype-cycle/</guid><description>&lt;p&gt;Escaping the hype cycle (and the vendor noise). Your vendors want you to buy. Your peers want you to succeed. These are not the same thing.&lt;/p&gt;&#10;&lt;p&gt;I don&amp;rsquo;t say that to be cynical. Vendor relationships matter. Good vendors genuinely want to help you succeed because your success is their success. But their incentive structure is optimized for sales. The information they share is filtered through that lens. The case studies they present are their best outcomes, not their typical ones.&lt;/p&gt;</description></item><item><title>Don't rush to tear down a fence</title><link>https://healey.io/writing/don-t-rush-to-tear-down-a-fence/</link><pubDate>Mon, 30 Jun 2025 15:21:30 -0600</pubDate><guid>https://healey.io/writing/don-t-rush-to-tear-down-a-fence/</guid><description>&lt;p&gt;Don&amp;rsquo;t rush to tear down a fence just because you don&amp;rsquo;t see its purpose.&lt;/p&gt;&#10;&lt;p&gt;As G.K. Chesterton said: &amp;lsquo;There exists a certain institution or law; let us say a fence across a road. The modern reformer says, &amp;ldquo;I don&amp;rsquo;t see the use of this; let us clear it away.&amp;rdquo; To which the wise reformer replies, &amp;ldquo;If you don&amp;rsquo;t see the use of it, I won&amp;rsquo;t let you clear it away. Go and think. Only when you understand its purpose may you touch it.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Complexity Kills</title><link>https://healey.io/writing/complexity-kills/</link><pubDate>Tue, 12 Sep 2023 15:14:24 -0600</pubDate><guid>https://healey.io/writing/complexity-kills/</guid><description>&lt;p&gt;Complexity kills.&lt;/p&gt;&#10;&lt;blockquote&gt;&lt;p&gt;… the startups we audited that are now doing the best usually had an almost brazenly ‘Keep It Simple’ approach to engineering. Cleverness for cleverness sake was abhorred. On the flip side, the companies where we were like ”woah, these folks are smart as hell” for the most part kind of faded.&lt;/p&gt;&#10;&lt;/blockquote&gt;&lt;p&gt;&lt;a href="https://renegadeotter.com/2023/09/10/death-by-a-thousand-microservices.html" target="_blank" rel="noreferrer"&gt;https://renegadeotter.com/2023/09/10/death-by-a-thousand-microservices.html&lt;/a&gt;*&lt;/p&gt;</description></item></channel></rss>