<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Workflow Design on Andreas Nissen</title><link>https://andreasnissen.dev/tags/workflow-design/</link><description>Recent content in Workflow Design on Andreas Nissen</description><generator>Hugo</generator><language>en-us</language><copyright>© Andreas Nissen</copyright><lastBuildDate>Sat, 05 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://andreasnissen.dev/tags/workflow-design/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Choose an Enterprise AI Use Case by Its Workflow Bottleneck</title><link>https://andreasnissen.dev/writing/choose-ai-use-case-by-bottleneck/</link><pubDate>Sat, 05 Sep 2026 00:00:00 +0000</pubDate><guid>https://andreasnissen.dev/writing/choose-ai-use-case-by-bottleneck/</guid><description>&lt;p&gt;A team proposes an AI assistant that reads incoming requests in two minutes. A person currently needs ten. The demo looks promising.&lt;/p&gt;&#10;&lt;p&gt;But each request also waits four hours before a reviewer opens it. If that wait stays the same, faster reading removes eight minutes from a process that takes four hours and forty minutes.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Choose an AI use case by the outcome it can improve across the workflow, including waiting and human review.&lt;/strong&gt; Task speed is useful evidence only when it connects to the goal you are trying to achieve.&lt;/p&gt;</description></item></channel></rss>