Case Study 03 · Agri-Food Group · Integration
Event-driven integration as the spine of an ERP programme
Designing the integration architecture and running product delivery for an ERP programme — sitting between the business and the engineers building it.
The Situation
The ERP programme had ambition and budget. What it lacked was a single point of accountability for the integration layer — the place where most ERP programmes succeed or fail.
The role combined architecture, product delivery and business analysis. None of those disciplines could carry the work alone; the integration was where they had to meet.
Approach
- Designed the integration architecture using APIs and event-driven patterns, with a deliberate eye on what would still be extensible in three years.
- Led product discovery and backlog management — the architecture and the backlog kept in lockstep, so design decisions had a near-term home.
- Owned delivery execution across the integration workstream, including dependency management with adjacent programmes.
- Acted as the bridge between business and engineering teams, where most translation losses tend to happen.
Outcome
- Integration architecture in place as the spine of the wider ERP programme.
- Backlog and architecture kept in single-source alignment throughout delivery.
- Cross-team dependencies resolved without escalation to programme leadership.
What Travels
Integration architecture is rarely an engineering problem first. It is usually a translation problem — between business intent, system constraint and delivery rhythm — and it earns its keep by making the next phase of the programme cheaper than the last.
Need a Business Consultant?
Ready to ship the next phase of your business?
Talk to a senior consultant today — no sales pitch, just a 30-minute working session to map your options.