<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VDI on Seunghoon Choi</title><link>https://seunghoonchoi.com/tags/vdi/</link><description>Recent content in VDI 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/vdi/index.xml" rel="self" type="application/rss+xml"/><item><title>Why AI Does Not Make Employees Faster: Tools and Permissions Still Matter</title><link>https://seunghoonchoi.com/column/execution-friction/</link><pubDate>Sun, 21 Jun 2026 17:56:30 +0900</pubDate><guid>https://seunghoonchoi.com/column/execution-friction/</guid><description>&lt;p&gt;&lt;img src="https://seunghoonchoi.com/images/col-execution-friction.jpg" alt="A tangled pile of computer cables and cords on a desk"&gt;&lt;/p&gt;
&lt;p class="inline-image-caption"&gt;When work remains slow after AI adoption, the delay may come from input, review, and approval processes rather than the model.&lt;/p&gt;
&lt;p&gt;Companies now tell employees to use AI. Write reports with it. Summarize meetings with it. Research faster with it. Yet the experience can be puzzling. AI responds quickly, but the work itself does not move much faster.&lt;/p&gt;
&lt;p&gt;The reason is simple. The company has blocked the tools and permissions needed to act, then added AI on top. Copying and pasting are restricted. External tools are unavailable. Files will not open without access. Employees cannot install a new program. Meetings and messages interrupt the work, and nothing can leave the company without approval.&lt;/p&gt;</description></item></channel></rss>