The “Like-For-Like” Pitfall

One of the most common mistakes in technology modernization projects is the “like-for-like” fallacy – the belief that new systems should exactly replicate the functionality and behavior of legacy systems. While this approach might seem logical at first glance, it often undermines the very benefits that modernization should bring.

Why Organizations Fall for Like-for-Like

The appeal of like-for-like modernization is understandable:

  • It seems less risky than reimagining processes
  • Users are familiar with existing workflows
  • Requirements appear clearly defined
  • It feels easier to manage scope
  • Stakeholders can easily envision the end result

However, this approach often creates more problems than it solves.

The Hidden Costs of Like-for-Like

Replicating Inefficiencies

Legacy systems often evolved around limitations of old technology. Replicating these workflows in modern systems means:

  • Carrying forward inefficient processes
  • Missing opportunities for automation
  • Maintaining unnecessary complexity
  • Underutilizing new technology capabilities

Increased Development Costs

Making modern systems behave like legacy ones often requires:

  • Custom development to replicate obsolete features
  • Complex integrations to maintain old workflows
  • Additional maintenance for unnecessary customizations
  • Extended testing cycles for custom functionality

Missed Opportunities

Like-for-like modernization typically means:

  • Ignoring process improvement opportunities
  • Missing chances to reduce operational costs
  • Failing to leverage new technology capabilities
  • Limiting future flexibility and scalability

A Better Approach: Value-Driven Modernization

Instead of like-for-like replacement, focus on:

1. Understanding Core Business Needs

  •    Identify essential business functions
  •    Question why processes exist
  •    Focus on outcomes rather than methods
  •    Look for improvement opportunities

2. Leveraging Modern Capabilities

  •    Embrace automation opportunities
  •    Utilize built-in features of modern systems
  •    Consider new approaches to old problems
  •    Take advantage of integration capabilities

3. Reimagining Processes

  •    Challenge existing workflows
  •    Look for simplification opportunities
  •    Consider user experience improvements
  •    Think about future scalability

Making the Transition

To avoid the like-for-like fallacy while maintaining project success:

1. Start with Business Objectives

  •    Focus on what the business needs to achieve
  •    Question current processes and workflows
  •    Identify pain points in existing systems
  •    Look for improvement opportunities

2. Engage Stakeholders Differently

  •    Ask “why” instead of “what”
  •    Focus on outcomes rather than features
  •    Discuss pain points and ideal solutions
  •    Encourage innovative thinking

3. Plan for Change Management

  •    Communicate benefits of new approaches
  •    Provide comprehensive training
  •    Support users through the transition
  •    Celebrate improvements and successes