Integration before automation: which one the problem needs

• Re-keying is the signature of missing integration. The same information entered twice, usually by two people, usually with slightly different values.
• Repeated decisions inside one system signal automation. The record is already there; a person is just checking the same conditions and taking the same action each time.
• An argument about ownership signals a process decision. Where no one agrees who should act, automating the step simply makes the disagreement fire faster.

1. Take one real item — an order, an enquiry, a new hire — and write down every place its data is entered or copied.
2. Mark each step as typed by a person, generated by a system, or checked by a person.
3. Note every export, spreadsheet, and email that carries the data between systems. Those are the gaps, whether or not anyone calls them integration work.
4. Identify which system holds the authoritative version of each field. Where two systems both claim to, that is the first thing to fix — integration between two sources of truth copies the disagreement.

• Integrate where the data is needed elsewhere and the receiving system can accept it directly. This removes the copy rather than speeding it up.
• Automate where the same conditions are evaluated repeatedly and the action is unambiguous. Automations that encode a judgement call are the ones that get switched off a month later.
• Document as manual, with an owner where the volume is low or the step needs human judgement. A deliberate manual step with a named owner is a decision; an accidental one is a queue.

Sequence integration before the automation that depends on it. An automation written against data that arrives by hand will need rewriting once the connection exists, and in the meantime it produces tasks based on whatever the last person typed.

Three things belong in the scope, not in a later conversation: which system is authoritative for each field, what happens when the connection fails or a record is rejected, and how the thing is switched off. Duplicate records created by a retry are a common result of adding a connection without deciding what a failure does. An automation nobody can disable is harder to remove than it was to add.

The example below is hypothetical and describes a pattern rather than a client account.

This work is scoped as systems integration and automation, part of the Operations & Systems capability. Where the handoff being integrated was never defined, the boundary work in operational consulting comes first — connecting a system to an undefined process tends to make the ambiguity faster.