Convenience is part of policy design
Teams choose workarounds when the compliant route takes longer or asks for information twice.
Management decisionMeasure abandonment and first-action time, then simplify the highest-volume routes.
Procurement & Supply Chain
4–6 weeks (design) + 6–10 weeks (delivery)
Spend Management: From Visibility to Behaviour Change
The organisation had spend visibility, but teams continued buying off contract when the compliant route was slower. We redesigned the highest-volume buying routes, embedded preferred suppliers and policy rules, assigned exception owners and established a weekly category decision cadence.
#Spend management
#Guided buying
#Policy
#Adoption
#Cadence
Decentralised organisationTurned spend controls from reporting into a working system with pathways, owners, and weekly actions.
Anonymised case study. Focus: changing buying behaviour through front-door design, decision rights and category governance.
Change the buying path before enforcing policy
Connect demand signals to a guided route, explicit approval and a weekly category decision so spend data changes future buying behaviour.
- 01 • SignalDemand intent
Need, timing, value and current supplier
- 02 • RouteGuided choice
Preferred channel, supplier or sourcing path
- 03 • DecidePolicy gate
Approve, compete, consolidate or stop
- 04 • TransactSystem record
Contract, PO, receipt and invoice
- 05 • ImproveCategory action
Remove the next leakage or friction cause
Illustrative applicationMarketing software renewals
- Starting point
- Renewals reach procurement after supplier commitment, leaving little time to test demand, consolidation or alternatives.
- Management intervention
- Route renewals 90 days before expiry and require an owner to choose renew, compete, consolidate or stop.
- Acceptance evidence
- Renewal coverage and preferred-channel use improve while urgent exceptions and automatic renewals decline.
Strategic analysis
What management should take from the case
Each finding connects an observed business signal to a decision, owner or allocation choice.
Visibility requires a decision owner
A spend signal does not inform category action until an owner can change demand, route or supplier choice.
Management decisionLink every priority measure to a category action, owner and review date.
Exceptions show whether policy fits demand
Repeated exceptions can indicate weak compliance or an impractical route.
Management decisionReview reason codes weekly and decide whether to enforce, redesign or retire the rule.
Implementation evidence
Operating models and delivery artefacts
Anonymised working assets used to define decisions, configure the workflow and transfer ownership into operations.
Operating artefact
The behaviour-change levers
We map spend leakage to a few levers procurement can actually control: convenience, decision rights, and consequence design.
Dashboards help only when they trigger weekly actions with owners.
Operating artefact
Guided buying and intake pathways
The routing map embeds preferred options, policy rules and an owned escalation route for urgent demand.
Route-change governance keeps guidance current as suppliers, demand and policy change.
Operating problem
- • Dashboards existed but did not change decisions or behaviours
- • The compliant path was slower than the workaround path, so leakage was rational
- • Policy exceptions were handled ad hoc with no learning loop
- • Preferred-supplier guidance sat outside the buying workflow
- • Post go-live, adoption friction was not measured and fixes were slow
Delivery approach
- • Start with the front door: intake and guided buying pathways for top request types
- • Define decision rights and a light steering cadence (who decides, when, with what evidence)
- • Embed preferred suppliers and policy guidance directly into the workflow
- • Make exceptions measurable: reason codes, SLAs, and a weekly root-cause review
- • Bridge business and vendors/SIs: translate policy and buying rules into configuration and integrations
- • Use AI/automation for admin reduction (request summaries, routing suggestions) with human accountability
Outputs handed over
- • Guided buying pathways + intake routing rules for top categories
- • Policy-to-workflow mapping (what is enforced, what is guided, what is escalated)
- • Exception model: reasons, owners, SLAs, and weekly actions
- • Preferred supplier embedding plan (catalogue, templates, and communications)
- • Adoption sprint plan + KPI pack and stabilisation checklist after go-live
Operational outcomes
- • Fewer workarounds as the compliant path became faster and clearer
- • More consistent decision-making through a weekly cadence and explicit owners
- • Improved adoption and reduced friction post go-live via measured fixes
- • A governed route-change process that protected adoption as categories and policies changed
Measures used to govern delivery
- • Preferred channel usage (directional, with clear definitions)
- • Policy exception rate (and top reasons)
- • Time-to-first-action for requests (intake health)
- • Savings delivered vs planned (with confidence rules)
- • Stakeholder satisfaction signals (escalations, turnaround time)
Baseline to target KPIs
These KPIs show where buying pathways, policy rules, and weekly category decisions need correction.
MetricTypical baselineTarget state
MetricOff-path buying (workarounds / off-contract)
Typical baselineCommon in categories where the compliant path is slow
Target stateReduced via guided buying, clear escalation routes, and enforcement where needed
MetricPolicy exception rate
Typical baselineExceptions handled ad hoc with no learning loop
Target stateMeasured reasons with owners and weekly root-cause actions
MetricPreferred supplier usage (directional)
Typical baselinePreferred-supplier guidance sits outside the buying workflow
Target stateEmbedded in pathways and tracked with clear definitions
Baselines and targets are operating ranges used to frame discovery and acceptance. They are not presented as verified client results.
Timeline
4–6 weeks (design) + 6–10 weeks (delivery)
- 01
Design (Weeks 1–3): baseline leakage, define policy and pathways, agree decision cadence and owners
- 02
Delivery (Weeks 4–6): implement guided buying, preferred suppliers, and exception handling rules
- 03
Delivery (Weeks 7–10): adoption sprint, KPI pack, and stabilisation after go-live
- 04
Scale (Weeks 11–16): extend to more categories and refine based on measured friction points
Related service
Continue into the service page tied to this example, or compare the wider advisory offer.