SI Design #1: Simplicity Acts as Foundations for Everything

Illustration of a shelf with four SaaS blocks in shades of purple and orangeIllustration of a shelf with four SaaS blocks in shades of purple and orange
Illustration of a shelf with four SaaS blocks in shades of purple and orange
Posté par
Cécile G.
Le
3 Feb
.
2026
Copier l’URL de l’article

It is awfully tempting to transfer the plug & play mindset to all things.

You start by adding one new tool to fulfill a specific need, then you integrate one solution because the teams is asking for it (or demanding it), and you end up with piled up services and absolutely zero clue on its toll on your systems’ architecture.

Although each add-on brings an amount of complexity to your information system. Alongside this complexity, the risks of breaches rises.

In 2012, Google learnt the lesson the hard way. A simple change in the Wi-Fi password generated a cascading failure situation for its internal password management system.

Said system was only able to restart after the intervention of an engineer. They had to powerdrill open a safe located in Australia to get access to a chip card.

What was the root of this situation? A system complexified over time by knotty dependencies and opaque recovery processes.

Design simplicity is not a cosmetic fad. It is a strategic bedrock, ever more in a context where centralisation of SaaS tools is capital.

Centralisation is a Great Way to Fight Complexity

Centralising your SaaS is not priorly a topic of operating costs or usability. It boils down to simplifying your information system.

Instead of managing more than 10 messaging and collaboration tools, 3 project planners et 5 other SaaS for cloud storage, centralising enables to sensibly decrease the number of elements in place and their interactions.

Practically speaking, this is equal to: 

  • using primarily integrated suites (such as Google Workspace, Microsoft 365, etc.) rather than standalone tools,
  • limiting strictly the number of connectors and third-party integrations to what is necessary,
  • documenting clearly all dependencies between tools when they exist yet are not obviously seen,
  • resisting the temptation to add another tool because there’s “one, oddly specific use case it covers”.

Simplifying your information system is a means to improve your day-to-day operations efficiency. This is the way.

Sort out your SaaS

Once it is time for a coworker to leave the company, its access management and retrieval can take a few seconds when everything is centralised.

The same goes for onboarding a newcomer, you ease out their learning curve and shorten the time they will need to focus on their work.

When faced with a security breach, you can quickly act and contain damages if your architecture is clear to you.

Design intricacies are not a fatality. You can prevent them and gain strategic leverage to protect your assets and data from accidents they create.

Being able to take in the tools you need without indulging in the new, superficial plethora of software the market offers is a critical skill to maintain.