<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Notes | J Lee</title>
    <link>https://123jlee.xyz/notes/</link>
      <atom:link href="https://123jlee.xyz/notes/index.xml" rel="self" type="application/rss+xml" />
    <description>Notes</description>
    <generator>Hugo Blox Builder (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Tue, 24 Oct 2023 00:00:00 +0000</lastBuildDate>
    <image>
      <url>https://123jlee.xyz/media/logo.svg</url>
      <title>Notes</title>
      <link>https://123jlee.xyz/notes/</link>
    </image>
    
    <item>
      <title>Friction is a signal</title>
      <link>https://123jlee.xyz/notes/first-post/</link>
      <pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
      <guid>https://123jlee.xyz/notes/first-post/</guid>
      <description>&lt;p&gt;I spent a decade watching big teams struggle with the same problems in different clothes.&lt;/p&gt;
&lt;p&gt;At Essence, it was reporting that took five people and three days to produce — and by the time it landed, the data was stale. At Call of Duty, it was growth operations that needed to move at the speed of a live game but were wired for quarterly planning cycles. In trading, it&amp;rsquo;s the same thing: latency, signal loss, system fragility that shows up exactly when you can&amp;rsquo;t afford it.&lt;/p&gt;
&lt;p&gt;The industry changed but the friction never did. It always comes down to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A process that was built for a smaller team&lt;/li&gt;
&lt;li&gt;A tool that was chosen because it was popular, not because it fit&lt;/li&gt;
&lt;li&gt;A decision that gets made six times instead of once because nobody wrote down the answer&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Most people treat friction as a tax you pay. I treat it as a signal — the system telling you exactly where to cut.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Find the friction. Remove it. Build the system.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
