Keep IT Simple

Keep IT Simple

Yes, Keep IT Simple! IT being Information Technology. Why do we software folks sometimes stray from this fundamental truth? Is it the urge to tinker? to patch up everything?

This isn't just a catchy phrase; it's a philosophy that underpins usability, maintainability, and ultimately, adoption. In my own career I experienced cases that vividly illustrate this truth.

The Actuarial Package

I once had the privilege of being part of a team that built a truly elegant solution: an application designed to empower actuaries within a life insurance system to create their own formulas for new products. Imagine – no wrestling with predefined variables, inputs, or outputs. It was intuitive, direct, and precisely what the users needed.

However, as my role at the time shifted towards global marketing efforts, I lost touch with the application's development team. What happened next is a cautionary tale I've witnessed far too often in our industry. Driven by the allure of "more," the development team began to layer on "options" – SQL integrations, complex tools, and a host of other features. In a mere two months, the beautifully simple application that had the potential to revolutionise how actuaries worked transformed into a robust monster that, sadly, gathered digital dust. Nobody used it.

MANTIS and Natural

Another example was the 1980’s 4GL debate. MANTIS was simple, few options, English-like syntax, easier for non-programmers and programmers to develop applications quickly. It competed with other mainframe-based development tools like Natural and RAMIS. MANTIS and Natural were popular and gained traction as alternatives to COBOL for faster application development.

At the end NATURAL dominated in enterprise-scale systems because MANTIS

struggled with large batch jobs. NATURAL outlasted MANTIS also due to the association with the ADABAS database.

My point is that Mantis, with its limited yet powerful set of statements, stood in stark contrast to the intricate web of options presented by Natural/Adabas. The simplicity of Mantis fostered adoption and ease of use, while the complexity of Natural often became a barrier.

Simplicity is a Superpower.

This tendency to over-complicate – why does it persist in the software industry? Is it a misguided belief that more features equate to more value? A fascination with cutting-edge technologies, even when they don't serve the core purpose. We forget that the most powerful software is often the most intuitive and the least intrusive.

My dream of that simple, effective actuarial tool wasn't about technological wizardry; it was about empowering users to solve their problems directly, without being bogged down by unnecessary complexity. The lesson learned is profound: simplicity isn't a compromise; it's a superpower.

In our Modernisation Times

As we continue to innovate and build the software of tomorrow, let's remember the power of subtraction.

In the contemporary landscape of software development and modernisation, encompassing cloud transformation, AI implementation, and data strategy, simplicity is vital.

Legacy systems are complex, and companies struggle to recruit people to maintain them. It is essential to modernise these systems by refactoring monolithic programs into simpler modules.

Furthermore, preparing for the near future of quantum systems, and autonomous AI, simplicity will become the decisive factor creating intuitive interfaces that shield users from underlying complexity. This will achieve both faster adoption and greater business impact. While complexity may be unavoidable in the infrastructure, the competitive advantage will belong to those who can translate technological sophistication into elegant simplicity for their stakeholders.

Let's prioritise clarity over complexity, usability over endless features. Let's listen intently to our users and build solutions that truly serve their needs, without the burden of unnecessary intricacies.

What are your experiences with simplicity versus complexity in software?

Has your team fallen into the ‘feature’ trap?

How do you enforce simplicity in IT strategy?

I'd love to hear your stories and perspectives in the comments below.

#SoftwareDevelopment #SimplicityInTech #UserExperience #KISSPrinciple #TechLeadership #CIOStrategy


To view or add a comment, sign in

More articles by Mely Lerman

  • COBOL Toolkit White Paper

    Author: Mely Lerman Date: April 16, 2025 Executive Summary Financial institutions rely heavily on COBOL systems that…

    2 Comments
  • COBOL next stop: AI

    There is a lot of contempt for COBOL, in special among young developers. This is a big mistake! COBOL is the most…

    26 Comments
  • If the CEO asks what to do with the COBOL

    Over time, issues linked to COBOL have been postponed and today innovation is being crippled by this ongoing debt…

    19 Comments
  • COBOL: The Profession of the Future

    COBOL is often dismissed as an outdated technology: “COBOL is a dinosaur” , “grandpa’s code”, “COBOL is not sexy”. Try…

    27 Comments
  • Reliable COBOL and the Cloud Chaos

    Cloud migration is indeed a blessing! Agility, scalability, innovation are strategic reasons for cloud migration. Cloud…

    13 Comments
  • Three Paths to Legacy Modernisation

    Five years ago, I read an article by a German PhD discussing why companies are maintaining their COBOL code rather than…

    18 Comments
  • COBOL programmers, founders of the Digital Age

    The period of the 1960s was a time of monumental change, marked by significant cultural, social and technological…

    1 Comment
  • Is COBOL Conversion to Java the Answer?

    I've been working with COBOL systems for a long time and have a deep appreciation for this robust and reliable…

    20 Comments
  • COBOL Toolkit DEMO

    In the rapidly evolving world of technology, we often forget that true innovation isn't about discarding the old, but…

  • Innovation: Breathing Life into Legacy

    We are so busy chasing disruption, looking for the latest and we forgot a profound truth: true innovation is not just…

    15 Comments

Insights from the community

Others also viewed

Explore topics