Reading Between the Lines with Continuous System Modernization

Reading Between the Lines with Continuous System Modernization

Modernization is never a one-time event—it’s a continuous process. According to Joe Szodfridt, every system is legacy the day you build it, which means organizations need a sustainable, iterative approach to modernizing software.

At Prodacity, Szodfridt outlined the hidden pitfalls of modernization efforts, the human-machine balance needed for innovation, and why domain-driven design (DDD) isn’t always the right answer.

The Hidden Gap: Why Modernization Efforts Stall

Hundreds of engineers, years of documentation, countless meetings—and yet, modernization often feels stuck. Why?

The challenge lies in hidden gaps within systems. Every large system consists of:

  • Shadow IT – Workarounds created outside official IT structures.
  • Paper Checklists – Processes still reliant on manual documentation.
  • Tribal Knowledge – Conversations and undocumented insights that never make it into design documents.

While tools can help visualize existing architecture, humans are needed to envision how a system should behave. The disconnect between what exists and what should exist often slows modernization.

The Pitfalls of Over-Engineering Modernization

One of the biggest mistakes in modernization? Over-reliance on rigid processes at the expense of human intuition.

While domain-driven design (DDD) is a powerful approach, it has steep learning curves and excludes non-technical stakeholders from the conversation. According to Szodfridt:

  • DDD is not always a living, adaptable system. It can be difficult to iterate quickly when it’s too rigid.
  • It takes months to learn and years to master. How can organizations expect non-technical people to contribute effectively?
  • Language barriers create silos. The terminology of DDD prevents cross-functional collaboration with business and operational teams.

Instead of over-engineering modernization efforts, the focus should be on building a common, inclusive framework that both technical and non-technical people can contribute to.

Thin Slices: Narrowing Focus for Meaningful Progress

To cut through the noise, Szodfridt recommends a “thin slice” approach—breaking modernization down into small, manageable segments that focus on clear outcomes.

A thin slice has:

  1. A clear start and end – Think of ordering food (start) and receiving it (end).
  2. Only one path over the bridge – The process should be streamlined with no unnecessary complexity.
  3. Outcome-based thinking – Instead of focusing on architecture, map legacy models on top of future-state models to determine where to start.

Analyst Takeaway: Rethinking Continuous Modernization

For developers and engineering leaders, modernization isn’t just about replacing legacy systems—it’s about making them more adaptive and user-centric.

Key Implications:

  • Prioritize usability over rigid structure. If modernization removes the human element, it’s failing its purpose.
  • DDD is not a one-size-fits-all approach. Organizations should reduce complexity and remove barriers to participation.
  • Small, outcome-driven improvements accelerate modernization. Thin slices help validate assumptions before implementation, reducing failure rates.

Final Thought

Continuous modernization means rethinking how we capture intent, reduce complexity, and build systems that work for people—not just machines. By simplifying processes and focusing on practical, testable slices of improvement, developers can modernize iteratively without getting stuck in endless documentation and decision paralysis.

The future of modernization isn’t just about updating systems—it’s about ensuring systems evolve alongside human needs.

Authors

  • Bringing more than a decade of varying experience crossing multiple sectors such as legal, financial, and tech, Sam Weston is an accomplished professional that excels in ensuring success across various industries. Currently, Sam serves as an Industry Analyst at Efficiently Connected where she collaborates closely in the areas of application modernization, DevOps, storage, and infrastructure. With a keen eye for research, Sam produces valuable insights and custom content to support strategic initiatives and enhance market understanding. Rooted in the fields of tech, law, finance operations and marketing, Sam provides a unique viewpoint to her position, fostering innovation and delivering impactful solutions within the industry. Sam holds a Bachelor of Science degree in Management Information Systems and Business Analytics from Colorado State University and is passionate about leveraging her diverse skill set to drive growth and empower clients to succeed.

    View all posts
  • Paul Nashawaty, Practice Leader and Lead Principal Analyst, specializes in application modernization across build, release and operations. With a wealth of expertise in digital transformation initiatives spanning front-end and back-end systems, he also possesses comprehensive knowledge of the underlying infrastructure ecosystem crucial for supporting modernization endeavors. With over 25 years of experience, Paul has a proven track record in implementing effective go-to-market strategies, including the identification of new market channels, the growth and cultivation of partner ecosystems, and the successful execution of strategic plans resulting in positive business outcomes for his clients.

    View all posts