DesignDiverso

03/06/2026

Industrial software failures are often blamed on “human error.”

But after years observing real-world operational environments, the reality is frequently the opposite:

systems fail humans.

Many SCADA, ERP and industrial platforms are still designed around technical architecture first — and actual operator cognition, stress, fatigue, decision-making and usability second.

The result?

alert fatigue
workflow friction
dangerous workarounds
poor adoption
operational mistakes
hidden productivity losses

We recently published a deep dive on safety-critical UX in industrial software systems, based on practical observations from real operational environments.

It explores why many industrial interfaces still struggle with usability despite technological progress — and why UX in these contexts is not just a “design issue,” but often an operational and safety issue.

Read here:
https://designdiverso.com/safety-critical-ux-scada-systems-why-industrial-software-still-fails-humans/

Safety-Critical UX, SCADA, HMI, and Human-AI Interface Design explained through real operational workflows, industrial systems, cognitive load, automation, and human factors.

15/03/2026

Most “digital transformation” projects fail for a simple reason.

They start with technology architecture instead of operational workflows.

In the past few years, frameworks like MACH architecture, composable ERP, and headless systems have become the dominant narrative in enterprise consulting.

Microservices.
API-first platforms.
Cloud-native stacks.

But architecture alone rarely fixes broken systems.

If workflows are fragmented and processes unclear, organizations often end up with distributed complexity instead of operational clarity.

We recently published a deep dive on this topic:

👉 Process-Driven Enterprise Systems vs MACH Architecture

The article explores:

• Why many composable ERP projects struggle
• The hidden complexity of architecture-first transformation
• Why process-driven enterprise systems often deliver better operational outcomes

If you're involved in ERP modernization, enterprise architecture, or digital transformation, this perspective may be useful.

Read the full article here

Process-Driven Enterprise Systems and automation systems built for real operations. Discover why MACH and composable ERP often fail—and what works instead.

10/03/2026

I still haven’t deleted Skype from my phone.

Not because I still use it - even though it’s been replaced by Teams.

But because that little blue “S” reminds me of a different era of software.

An era when mobile apps were built to solve real problems.

When Skype appeared, it changed everything:
suddenly you could call family, colleagues, or partners across the world without worrying about international tariffs or burning through SIM credit.

For many of us working internationally, it literally opened the world.

I was an early adopter, and it felt revolutionary.

Then it was acquired by Microsoft.
And like many great products, the focus slowly shifted.

Features multiplied.
Interfaces became heavier.
And the original simplicity that made it powerful faded.

Today we live in an ecosystem where too many apps are designed not to serve users, but to capture attention and monetize it through ads, tracking, and endless engagement loops.

But I believe we’re entering a different phase.

One where companies begin asking again:

• Does this product actually solve a meaningful problem?
• Does it respect users’ time and attention?
• Does it create real value for businesses and people?

At DesignDiverso, this is exactly the mindset we try to bring into the products and platforms we design.

Technology should enable an organic economy — not a system where every interface exists only to extract clicks.

Maybe that old Skype icon stays on my phone as a small reminder of that principle.

Build technology that connects, empowers, and serves.

Not just software that chases attention.