Essay 01 · Operational software · July 2026

Signals before dashboards

Most teams do not lack information. They lack a reliable moment when information becomes somebody’s next move.

Most teams do not lack dashboards. They lack a reliable moment when a signal becomes somebody’s action.

A dashboard can make a problem visible and still leave the original workflow unchanged. Someone has to open it, understand the context, decide whether the signal matters and remember who should act. The organisation technically knows more, but nothing has become operational yet.

Information becomes operational only when it changes what happens next.

Visibility is not ownership.

The gap between a useful insight and useful software is usually not detection. It is the decision that follows detection.

A strong operational product answers four questions at the moment a signal appears: What happened? Why does it matter? Who owns the next move? What should happen now?

Weak output
A new metric to interpret
Strong output
A clear decision to make
Weak workflow
Someone remembers to look
Strong workflow
Ownership is created

The product question.

When teams start with available data, they often build the most impressive visualisation they can. When they start with the unresolved decision, they build something smaller and more useful.

Do not ask only what the data can tell you. Ask what decision should become easier because the data exists.

This principle shaped Sighub. Renewal information can be present in a system and still fail to create timely action. The useful product is not another overview of customer risk. It is the moment scattered evidence becomes a concrete task with context and ownership.

UA
Ulaş ArslanProduct builder and Customer Experience Manager in Rotterdam.