The Work Between the Systems

An employee downloads a report from the sales system, cleans it and uploads it into finance. A representative reads an email, finds the account in a separate application and copies the request into an internal tracker. A warehouse worker updates inventory in one place, while someone in the office adjusts a second record so the website shows the correct quantity. A manager collects updates from several people before preparing a report for leadership.

None of these activities may be described as the company's core work. Yet without them, the core work would stop. This is the work between the systems: the checking, transferring, translating, reminding, reconciling and following up required when technology does not carry information cleanly through the business.

It is easy to underestimate because it is distributed across many roles and performed in small increments. It is also one of the clearest signs that the organization's architecture no longer reflects its operation.

When systems cannot communicate, people connect them. They copy information from one screen to another. They rename files so another department can understand them. They send messages to announce that a transaction has moved. They remember which fields mean slightly different things in separate systems. They investigate why two reports disagree.

From the organization's perspective, the process appears complete. The order entered the first system and eventually appeared in the second. But the connection was not created by technology. It was created by human attention.

This arrangement is more fragile than it looks. The organization is depending on employees to recognize what must be transferred, perform the transfer correctly, notice missing information, interpret inconsistencies, remember informal rules, and recover when something fails. The system boundary becomes a place where errors, delay and uncertainty accumulate.

The difficulty is not merely that administrative employees perform repetitive work. Highly skilled professionals often perform it too. A project manager spends time reconstructing status. A salesperson searches for fulfilment information. An accountant corrects operating data. A production supervisor prepares reports by hand. A senior employee checks that routine actions occurred because no system provides confidence that they did.

The cost is therefore greater than the minutes consumed. It includes the opportunity cost of attention. Every hour spent moving information is an hour not spent interpreting it, improving the operation, serving the customer or addressing a more difficult problem.

The organization may appear fully employed while a significant part of its capacity is devoted to making disconnected systems behave like one.

The work between systems develops gradually. A new platform is purchased for one department. Another application is added later. A website is rebuilt. A location adopts a local tool. A spreadsheet is introduced as a temporary measure. An acquisition brings another set of systems. Each decision may be reasonable in isolation. The collective environment becomes difficult because the handovers were never designed as a whole.

Organizations continue tolerating the resulting manual work for several reasons. The tasks appear small: copying one record may take two minutes, but repeated thousands of times the cost becomes material. The work is distributed, so no single department sees its complete size. Employees become highly efficient at the workaround, which makes the process look easier than it is. The process still reaches an outcome, so the hidden effort does not appear in the final result. And integration is treated as an IT matter, discussed without examining the business rules, ownership and exceptions the connection must carry.

A weak integration transfers fields. A strong integration preserves meaning and responsibility. Suppose a website sends an order into an ERP. The technical question is whether the order data can be transmitted. The operating questions are broader.

An API can move information. It cannot resolve an unclear operating model. That is why integration projects sometimes succeed technically while the business continues to rely on manual checks. The connection exists, but the process around it remains uncertain.

Time debt

Employees repeatedly perform tasks that could be eliminated or automated.

Quality debt

Each transfer creates another opportunity for omission, duplication or interpretation error.

Visibility debt

Management cannot see the complete process because parts of it occur in messages, files and personal routines.

Knowledge debt

The organization becomes dependent on people who understand how the gaps are bridged.

These debts compound as the business grows. More transactions produce more transfers. More locations create more variation. More systems increase the number of possible handovers. What began as a tolerable workaround becomes part of the operating model.

There are places where a human transition is appropriate. A complex case may require professional interpretation. A sensitive customer situation may need personal attention. A quality exception may demand physical inspection. A commercial decision may require negotiation.

The goal is not a process without people. The goal is a process in which people participate because judgment is needed, not because software cannot carry information from one place to another.

A useful distinction is between human judgment, where the person considers context, ambiguity, consequence or relationship, and human transport, where the person moves, reformats, announces or verifies information because the systems do not. The first may create value. The second often reveals a design problem.

Leaders can uncover the work between systems by following a real transaction from beginning to end. Choose an order, service request, application, production batch, shipment or invoice. At every stage, ask:

This exercise is more revealing than beginning with a catalogue of software. It exposes the actual operating chain.

Organizations often associate automation with visible, impressive technology. But some of the highest-value improvements are quiet. A completed form creates the correct record automatically. An approved order becomes available to fulfilment without re-entry. Inventory changes appear across the necessary channels. A customer is informed when an actual event occurs. A manager sees an exception without requesting an update.

The employee experiences the improvement as an absence: no second entry, no status email, no reconciliation spreadsheet, no reminder, no search for the latest file.

The work between systems is often one of the largest practical opportunities available to a growing organization. It can be addressed through clearer process ownership, better use of existing platform capabilities, configuration, direct integrations, workflow orchestration, shared data definitions, a custom interface spanning several systems, retirement of duplicate applications, or redesign of the process itself. The right response depends on the cause. But the first step is always visibility. A company cannot improve work it has never formally recognized.