Integration projects fail on the details: who owns the record, what happens on failure, and who watches the queue on a Friday afternoon.
Start with ownership and flow
- Be clear about which system owns each type of information.
- Map what needs to move between systems, when it needs to move and what happens when it fails.
- Keep support and monitoring in scope from the start, not as an afterthought.
The best integration design is usually the one people can understand, support and change without creating new dependencies every time the business moves.