<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Supreeth — writing</title>
  <link>https://supreeth.in/posts/</link>
  <atom:link href="https://supreeth.in/posts/feed.xml" rel="self" type="application/rss+xml" />
  <description>Occasional essays on product, process, and the unglamorous details.</description>
  <language>en</language>
  <item>
    <title>The emails nobody designed</title>
    <link>https://supreeth.in/posts/the-emails-nobody-designed.html</link>
    <guid isPermaLink="true">https://supreeth.in/posts/the-emails-nobody-designed.html</guid>
    <description>What happened when we mapped every automated message a traveller could receive — and why the map fixed more than the emails did.</description>
  </item>
  <item>
    <title>Fleet-on-Street: designing a field app from zero</title>
    <link>https://supreeth.in/posts/fleet-on-street.html</link>
    <guid isPermaLink="true">https://supreeth.in/posts/fleet-on-street.html</guid>
    <description>Designing Fleet-on-Street, Amazon&#x27;s field-agent onboarding app, from a blank canvas — and what each trade-off underneath the screens actually cost.</description>
  </item>
  <item>
    <title>The customer journey map that turned into a to-do list</title>
    <link>https://supreeth.in/posts/customer-journey-map.html</link>
    <guid isPermaLink="true">https://supreeth.in/posts/customer-journey-map.html</guid>
    <description>How mapping one traveller&#x27;s journey — from idle daydreaming to becoming &quot;the expert&quot; at dinner parties — stopped being a diagram and started telling us what to build.</description>
  </item>
</channel>
</rss>
