Why Ariba programmes stall after stage two
Most Ariba implementations configure sourcing and stop. The value sits in stages three and four — integration and adoption — and that is where planning usually runs out.
Nexolve TechnologiesDelivery team
The pattern we keep seeing
A programme goes live on sourcing, sometimes contracts. The steering committee celebrates, the implementation partner rolls off, and eighteen months later the business still emails most of its suppliers. The platform was bought for the full source-to-pay chain; it is being used for a fraction of it.
This is not a configuration problem. It is a sequencing problem. Upstream modules are demonstrable — a sourcing event makes a good screenshot. Integration and adoption are unglamorous: interface monitoring, supplier wave planning, catalogue ownership. Programmes stall because the unglamorous stages were never staffed.
What stages three and four actually need
Integration needs an interface catalogue with named owners, error handling agreed with both system owners, and testing against real release cycles — not just go-live day. An Ariba-to-S/4HANA interface that fails silently will be discovered at month-end, by finance, in the worst possible way.
Adoption needs the things nobody demos: supplier segmentation, wave plans, templated communications, guided enablement, and weekly metrics. Agree the adoption numbers before the programme starts, or you will never be able to say whether it worked.
The fix is boring and known
Plan all four stages — upstream, downstream, integration, adoption — with the same rigour, before configuration starts. Staff supplier onboarding as a managed workstream with its own milestones. Keep the team that configured the platform accountable for the adoption numbers.
None of this is novel. It is simply what gets cut when a programme is priced to win rather than priced to deliver.
