M29BuildTechnology· Module 5
Integration
Orders are entered in one system, re-typed into another and reconciled by hand at month-end.
- Fix
- Grow
- Scale
- Technology
- Operations
- ~5 min · Map
The business problem
Disconnected systems force people to become the integration. They re-key data, reconcile figures and chase discrepancies. Errors appear at every handover, and management reports are late because data must be collected and combined manually.
Why it matters
Integration means data is entered once and flows where it is needed. It saves time, removes errors and makes real-time reporting possible.
What you will learn
- Map where data moves between systems
- Decide the direction and timing of each data flow
- Choose between native connectors, integration platforms and custom work
- Plan for errors and data ownership
Core questions
- Where is data re-typed between systems?
- Which system is the source for each data type?
- How often must data flow: real-time, daily, monthly?
- Who fixes an integration failure?
Work through the module
CaseWhat is happening?
E-commerce retailer, 25 people · Illustrative teaching case
An online retailer re-enters website orders into its accounting system and updates stock manually. Overselling and reconciliation errors are frequent. Connecting the online store, stock and accounts so that orders and stock flow automatically removes the double entry and most overselling.
DecisionWhat does the leader need to decide?
Keep manual reconciliation, or invest in connecting the systems?
FrameworkHow should they think about the problem?
Single entry, single source
Each piece of data is entered once, in its system of record, and flows to other systems automatically. Define the source, the flow, the timing and the owner for every integration.
ToolWhat can they use?
Integration mapMap
- Systems as boxes; data flows as arrows
- Mark each flow as manual or automatic
- Estimate hours and error rates for manual flows
- Name source, frequency and owner for each flow
ApplicationHow does it apply to their business?
Apply it to your own business:
- Draw the data flows for your order-to-cash process
- Mark manual flows and estimate their cost
- Pick the most costly flow to integrate
ImplementationWhat changes?
What should change in the business:
- Clean the data on both sides before connecting
- Integrate the chosen flow
- Set up monitoring and an owner for failures
ReviewDid it work?
How to tell whether the change worked:
- Has manual re-entry stopped for that flow?
- Have reconciliation errors fallen?
- Are reports available sooner?
After this module you should be able to decide
Keep manual reconciliation, or invest in connecting the systems?
And leave with: An integration plan for your most costly data gap.
Sequence · Technology
Related modules
Part of these learning paths