<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Process Optimization on Pfisterer Consulting</title><link>https://pfisterer.xyz/en/tags/process-optimization/</link><description>Recent content in Process Optimization on Pfisterer Consulting</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 24 Mar 2026 18:15:00 +0100</lastBuildDate><atom:link href="https://pfisterer.xyz/en/tags/process-optimization/index.xml" rel="self" type="application/rss+xml"/><item><title>5 Modules That Don't Belong in Your ERP: Why Suite Thinking Ruins Your Procurement</title><link>https://pfisterer.xyz/en/news/erp-module-die-nicht-ins-erp-gehoeren-suite-vs-best-of-breed/</link><pubDate>Tue, 24 Mar 2026 18:15:00 +0100</pubDate><guid>https://pfisterer.xyz/en/news/erp-module-die-nicht-ins-erp-gehoeren-suite-vs-best-of-breed/</guid><description>&lt;p&gt;Five departments sit at the table. Each one has a wish list. HR wants skill management. Sales needs lead scoring. Administration demands compliant document archiving. The project manager insists on Kanban boards. The quality manager wants audit management with CAPA tracking. All five wishes end up in the same document: the ERP requirements catalogue. All classified as knockout criteria.&lt;/p&gt;
&lt;p&gt;The result is something I see in &lt;a href="https://pfisterer.xyz/en/news/erp-auswahl-mittelstand-lastenheft-teuerster-fehler/"&gt;tender after tender&lt;/a&gt;: a catalogue with 177 criteria, 131 of them classified as A-criteria — mandatory knockout requirements. That&amp;rsquo;s &lt;a href="https://pfisterer.xyz/en/news/erp-ausschreibung-74-prozent-a-kriterien-zu-viele/"&gt;74 percent&lt;/a&gt;, far above any reasonable benchmark. What starts as structured procurement ends as a wish concert that no single system can serve.&lt;/p&gt;</description></item><item><title>ERP Frustration in Mid-Sized Companies: Why a New System Won't Fix the Old Problem</title><link>https://pfisterer.xyz/en/news/erp-frust-mittelstand-neues-system-loest-altes-problem-nicht/</link><pubDate>Thu, 05 Mar 2026 10:00:00 +0100</pubDate><guid>https://pfisterer.xyz/en/news/erp-frust-mittelstand-neues-system-loest-altes-problem-nicht/</guid><description>&lt;p&gt;&amp;ldquo;Our ERP is the problem.&amp;rdquo; I hear this sentence in almost every initial meeting. Too slow. Too complicated. Can&amp;rsquo;t do this. Does that wrong. The solution seems obvious: a new system. More modern, more powerful, better.&lt;/p&gt;
&lt;p&gt;In 8 out of 10 cases, the truth is different &amp;ndash; and this aligns with findings from the &lt;a href="https://www.standishgroup.com/"&gt;Standish Group&lt;/a&gt;, which has analyzed IT project failures for decades: &lt;strong&gt;The ERP isn&amp;rsquo;t the problem. The processes are.&lt;/strong&gt; And a new system with the same processes delivers exactly the same result — just at a higher cost. This is a core focus of my &lt;a href="https://pfisterer.xyz/en/leistungen/projekte-systeme/"&gt;ERP consulting for SMEs&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>