top of page

The User Should Not Have to Become the Integration Layer

Writer: DTEK Nerd
DTEK Nerd
Nov 5
2 min read

Updated: Nov 9

OBSERVATION 010

THE ASSUMPTION:  When people carry context between systems, the human has become middleware.



We call a surprising amount of manual integration “workflow.”


Open System A. Find the record. Copy the identifier. Open System B. Search again. Re-enter the relevant details. Interpret the result. Download something. Upload it somewhere else. Tell System A what happened. Maybe send an email so everyone knows the process moved forward. The user just integrated the systems.


This pattern is so common that organizations stop seeing it as an architectural problem. It becomes training. A checklist. A standard operating procedure. A productivity issue. Someone eventually proposes another dashboard so the user can see more of the systems they are manually reconciling.


But the underlying problem is often simpler: the systems do not preserve the operational thread between them. The person does.


Humans are remarkably good at this. They understand intent, recognize that two differently formatted records describe the same thing, remember what happened five minutes ago, notice an exception, and know when the normal sequence should stop. That flexibility makes people excellent at bridging bad integration. It also makes the cost easy to hide.


Every manual handoff consumes attention. Every re-entry creates another opportunity for error. Every screen transition asks the user to reconstruct context the technology already had somewhere else. At scale, skilled people spend their time transporting and reconciling information instead of applying judgment to it.


Automation alone does not fix this. Automating a fragmented process can simply create faster fragmentation. The architectural goal should be to preserve the thread so the user enters where their judgment is needed, not wherever two systems fail to meet.


People should be part of the operation. They should not be the bus that keeps it connected.


WHAT WE ARE WATCHING

“Workflows” whose essential logic consists of people copying, reconciling, re-entering, or carrying context between systems that are supposedly integrated.

bottom of page