An integration estate cannot usually be replaced at once. Teams need a sequence that reduces visible operational pain while improving ownership and controls. A 90-day plan should begin with the handoffs that create visible operational pain, not a promise to replace every interface. Use a short inventory to choose one high-value change, prove it in the workflow, and decide what comes next from evidence.
What good engineering looks like
Which handoff creates the greatest combination of business impact, failure frequency and change cost? Answer this for a named workflow and an accountable team. Identify the information needed at the moment of decision, the system that can settle a dispute, and the route for correcting dependent copies. The technical design should make those business rules visible to the people who operate and support the handoff.
-
Days 1–30: map interfaces, owners and recurring exceptions.
-
Days 31–60: fix one high-value contract, observability or reconciliation gap.
-
Days 61–90: validate the result and decide the next consolidation or replacement step.
-
A named owner for a rejected, delayed or repeated item.
-
Evidence that the receiving system applied the intended business state.
A practical starting point
-
Choose one real case and write down its trigger, expected outcome and responsible team.
-
At day 30, confirm owners and baseline failure patterns.
-
At day 60, test the selected contract, observability or reconciliation change with real users and exceptions. At day 90, compare the outcome with the baseline and decide whether to extend, change or stop the approach.
-
Record what the test exposed, who will resolve each open question and how the fix will be checked.
Keep the first design small enough to review with the people who run the process. Test an exception alongside the normal case. A successful transport test shows that data moved; it does not by itself prove that the receiving team can make the right decision or recover from a partial failure.
The decision to make
Use evidence from actual workflows to reset priorities at each gate. Avoid promising a fixed transformation from a first-pass inventory. Decide what level of timing, traceability and recovery this workflow actually needs. Document assumptions that remain untested and revisit the choice when a partner, process or business rule changes. The point is a dependable operating decision, not simply a working interface.
Explore Algoza's related services: https://algoza.co.za/services/integration