soapplied
EN · EL · DE · NL

Systems thinking

When to dissolve a technology problem instead of solving it

Some technology problems persist because the organisation keeps reproducing the conditions that create them. In those cases a better technical solution may only manage the symptom. To dissolve the problem is to redesign the surrounding arrangement so the problem no longer arises in the same form — for example by changing ownership, information flow or the need for a hand-off.

Systems thinkingArchitectureDecision design

Some technology problems persist because the organisation keeps reproducing the conditions that create them. In those cases a better technical solution may only manage the symptom. To dissolve the problem is to redesign the surrounding arrangement so the problem no longer arises in the same form — for example by changing ownership, information flow or the need for a hand-off.

Example pattern

A reconciliation tool may solve repeated data mismatch. Changing master-data ownership and removing duplicate creation points may dissolve much of the reconciliation problem.

Look for recurring demand for fixes

If the same class of issue returns after multiple projects, the system may be generating it.

Use judgement

Not every problem should be “dissolved.” Some simply need competent repair. The point is to keep the wider design option available.

Why this matters to soapplied

These ideas influence how I frame technology decisions: understand purpose and perspective, see the interactions, imagine a better whole, and then choose a feasible intervention. The method should remain practical enough to produce a decision, not become an academic exercise.

Independent first read

Bring one decision.

Start with the situation as you see it. The first task is to understand the wider system before deciding what intervention makes sense.