INSIGHTS
Thinking across process and technology.
Notes on enterprise operations, SAP, integration, automation and AI — with a particular focus on the decisions between them.
The interesting question is rarely whether a technology can be used.
It is where it belongs, what it should replace — and what should remain unchanged.
Themes I'm exploring
AUTOMATION
Automation is an intervention, not a strategy.
Automation can remove effort and increase capacity, but it can also preserve a process that should have been redesigned, integrated or removed.
The useful question is not simply what can be automated, but whether automation is the appropriate intervention.
INTEGRATION
When integration is a better answer than another automation layer.
UI automation is valuable when direct system interaction is unavailable or uneconomic.
But when stable system interfaces exist, another automation layer may add complexity that does not need to be there.
AI & CONTROL
Where AI belongs — and where deterministic controls should remain.
AI is particularly useful for variability and interpretation.
That does not mean every decision should become probabilistic.
Enterprise solutions often need a deliberate boundary between AI, deterministic logic, system validation and human judgement.
Questions worth asking
- Are we automating the problem — or removing it?
- What should move closer to the system rather than remain in the user interface?
- Where does variability justify AI?
- Which decisions still require deterministic control?
- When should human judgement remain part of the operating model?
- What should be retired rather than rebuilt during a platform transition?
The decisions between technologies matter as much as the technologies themselves.
This section will develop into practical notes and case-based observations from enterprise operations, automation, integration and AI.
See how I approach these decisions