<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Headcount Cuts on Seunghoon Choi</title><link>https://seunghoonchoi.com/tags/headcount-cuts/</link><description>Recent content in Headcount Cuts on Seunghoon Choi</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 21 Jun 2026 17:56:30 +0900</lastBuildDate><atom:link href="https://seunghoonchoi.com/tags/headcount-cuts/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Cutting Staff After Adopting AI Can Make a Company Slower</title><link>https://seunghoonchoi.com/column/ai-headcount-mistake/</link><pubDate>Sun, 21 Jun 2026 17:56:30 +0900</pubDate><guid>https://seunghoonchoi.com/column/ai-headcount-mistake/</guid><description>&lt;p&gt;&lt;img src="https://seunghoonchoi.com/images/col-ai-headcount-mistake.jpg" alt="Empty chairs lined up at desks in an office lit by morning sun"&gt;&lt;/p&gt;
&lt;p class="inline-image-caption"&gt;When a desk becomes empty, payroll costs fall, but the company may also lose the work context that person knew.&lt;/p&gt;
&lt;p&gt;When a company adopts AI tools, one sentence almost always appears: &amp;ldquo;So how many people can we cut now?&amp;rdquo; On the surface, it sounds reasonable. AI writes reports, organizes minutes, researches material, writes code, and drafts plans. Some work is genuinely faster than humans.&lt;/p&gt;</description></item></channel></rss>