<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Design decisions — Superflow</title>
    <link>https://www.superflow.design/decisions</link>
    <description>Short proof cases of single product design decisions from real SaaS work: the context, the options, what I chose, why, and what happened.</description>
    <language>en</language>
    <atom:link href="https://www.superflow.design/decisions/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why I made a flowchart canvas the main journey editor instead of a step list</title>
      <link>https://www.superflow.design/decisions/flowchart-canvas-over-step-list</link>
      <guid isPermaLink="true">https://www.superflow.design/decisions/flowchart-canvas-over-step-list</guid>
      <description>In NxtForm I made a vertical flowchart the default way to build candidate journeys, with the old step list kept as a second view, because a list hides who goes where.</description>
      <pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate>
      <category>UX patterns</category>
      <category>Forms</category>
      <category>Data-heavy UI</category>
    </item>
    <item>
      <title>Why I made editing a separate workspace instead of a tab</title>
      <link>https://www.superflow.design/decisions/editing-as-workspace-not-tab</link>
      <guid isPermaLink="true">https://www.superflow.design/decisions/editing-as-workspace-not-tab</guid>
      <description>In NxtForm I moved journey editing out of the tab bar into its own workspace with a clear entry and exit, because a tab hides that you are changing something candidates use.</description>
      <pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate>
      <category>UX patterns</category>
      <category>Navigation</category>
    </item>
  </channel>
</rss>
