Skip to content
Go Flow
← All articles
Research reportRealization fitness

Endless Modernization: How Infinite Flow Keeps Software Fresh

Jim Johnson, Hans Mulder · The Standish Group · 2021

Large, temporary modernization projects bring long lead times, high costs and risk. Johnson and Mulder propose Infinite Flow instead: a permanent stream of small improvements to processes and software, with better outcomes for cost, value and application lifespan.

Many organizations still renew their business-critical software through large, temporary projects. According to Johnson and Mulder, this approach causes long lead times, high overhead costs and major risks. The environment keeps changing during the project, so the delivered solution may already be partly outdated when it goes live. After completion, technical debt builds up again: overdue maintenance and outdated components accumulate until the next costly modernization becomes necessary.

As an alternative, the authors introduce Infinite Flow: a permanent stream of small improvements to processes and software. Modernization is no longer a separate project with a start and end date, but a fixed part of daily operations. Small, multidisciplinary teams frequently deliver limited, directly usable changes. Users respond quickly, so feedback can be incorporated in the next adjustment right away. Decisions are made close to the work, and waiting times, handovers and meeting load are kept to a minimum.

From the material studied by The Standish Group, Johnson and Mulder conclude that flow-style modernization (carried out with microprojects, microservices and practices from Scrum and DevOps) works out better than large-scale renewal projects. In their view, the approach leads to higher user satisfaction, a better ratio between cost and delivered value, lower risk and a longer lifespan for applications. By continuously improving and restructuring, software stays "fresh" and technical debt is addressed early.

The core of the publication is therefore organizational: Infinite Flow is more than a development method. It requires stable, expert teams, short decision lines, direct user involvement and funding of a continuous value stream instead of separate projects. The organization stops replacing periodically and chooses permanent maintenance, learning and renewal. Modernization thus becomes a continuous capability that lets technology and organization keep moving together.

This publication is mainly relevant for executives, CIOs, information managers and professionals looking for a rationale for the transition from temporary IT projects to continuous product and value streams. The empirical claims should be read within The Standish Group's own research method.

Related publications

Academic paperRealization fitnessCollaborating

COLLABORATING AS A QUINTET: AI AS A TEAMMATE

J.J. (Hans) Schönfeld MCM - Go Flow Network · Go Flow Network: Articles · 2026

Everything is connected. An organization is increasingly unable to solve problems on its own and must learn to collaborate in ecosystems. Today, it is both interesting and important to consider AI as a collaboration partner. This article focuses on three questions: What can AI contribute as a digital collaboration partner? What changes when AI is considered a teammate? What conditions are needed to collaborate responsibly with digital partners such as AI agents?

Discussions about this

Have a question about this topic, or an experience to share? Start a discussion; it stays linked to this page.

Start a discussion

Comments

No comments yet

Be the first to comment.

Want to comment? Log in or join for free.