Recording how systems connect.
WHY IT MATTERS
Integrations are invisible until they break, and then nobody remembers how they work.
WHAT TO RECORD PER INTEGRATION
What it connects Direction of data flow What triggers it Which system owns which data Where credentials are stored How failures are handled Who owns it
WHY THE OWNER MATTERS MOST
Unowned integrations are maintained by nobody until an incident.
WHAT DIAGRAM TO DRAW
Systems as boxes, data flows as arrows, labelled with what flows and how often.
WHY A DIAGRAM
It reveals dependencies and loops that prose conceals.
WHAT TO INCLUDE FOR EACH EXTERNAL PROVIDER
Their documentation address Support contact Account details and who holds them Contractual limits Cost basis
WHY THE SUPPORT CONTACT SPECIFICALLY
Finding it during an incident wastes the time that matters.
WHAT TO WRITE AS A RUNBOOK
How to tell whether it is working How to reprocess a failed item How to disable it Who to contact
WHAT TO KEEP IN VERSION CONTROL
Mapping definitions Configuration The documentation itself
WHAT TO REVIEW
The list, periodically, for integrations that can be retired.
