<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Business-Process on lgovea</title>
    <link>https://lgovea.com/tags/business-process/</link>
    <description>Recent content in Business-Process on lgovea</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>2026 lgovea</copyright>
    <lastBuildDate>Fri, 11 Sep 2026 18:36:37 -0600</lastBuildDate>
    <atom:link href="https://lgovea.com/tags/business-process/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Knowing When Not to Use AI</title>
      <link>https://lgovea.com/posts/knowing-when-not-to-use-ai/</link>
      <pubDate>Fri, 11 Sep 2026 18:36:37 -0600</pubDate>
      <guid>https://lgovea.com/posts/knowing-when-not-to-use-ai/</guid>
      <description>&lt;p&gt;There’s a growing pressure to turn every process into an AI agent. Probably because the technology is new and hot—but that is not the right approach for everything. Using AI should be strategic. It should not be treated as a silver bullet that can be thrown at every organizational problem.&lt;/p&gt;
&lt;p&gt;We already have different solutions for different problems:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Humans — for high-stakes decisions&lt;/li&gt;
&lt;li&gt;Rule-based systems — when the logic is known and explicit&lt;/li&gt;
&lt;li&gt;Machine learning — for predictions&lt;/li&gt;
&lt;li&gt;GenAI — for unstructured inputs that need interpretation&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Each comes with its own trade-offs in accuracy, cost, complexity, and risk.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
