<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Digital Transformation on Ivaldo de Oliveira Batista Júnior</title><link>https://ivaldo.eti.br/tags/digital-transformation/</link><description>Recent content in Digital Transformation on Ivaldo de Oliveira Batista Júnior</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Ivaldo de Oliveira Batista Júnior</copyright><lastBuildDate>Mon, 26 Oct 2026 16:20:00 -0300</lastBuildDate><atom:link href="https://ivaldo.eti.br/tags/digital-transformation/index.xml" rel="self" type="application/rss+xml"/><item><title>Modernize or Replace a Legacy System? How to Decide Without Disrupting Operations</title><link>https://ivaldo.eti.br/blog/modernize-or-replace-a-legacy-system/</link><pubDate>Mon, 26 Oct 2026 16:20:00 -0300</pubDate><guid>https://ivaldo.eti.br/blog/modernize-or-replace-a-legacy-system/</guid><description>&lt;p&gt;Some systems look obsolete to the people who manage them, yet remain indispensable for billing customers, processing orders, maintaining inventory, or meeting regulatory obligations. They are hard to change, require exceptional care, and often contain business rules that were never documented anywhere else.&lt;/p&gt;
&lt;p&gt;As pressure to change increases, an apparently straightforward proposal emerges: &lt;strong&gt;replace everything with a new solution&lt;/strong&gt;. Elsewhere, the opposite happens: nobody wants to touch the system, so every new business requirement is handled with another spreadsheet, a manual workaround, or an improvised integration.&lt;/p&gt;</description></item></channel></rss>