Sourcing & Supply Chain Coordination
Executive Readiness Lens
This chapter helps you make one hard operational choice: how do we align sourcing decisions, contract logic, and replenishment behavior so local optimization does not destroy chain-wide performance? In most firms, procurement optimizes purchase cost, sales optimizes campaign lift, and operations absorbs the volatility. The result is familiar: rising expedite costs, unstable service levels, and inventory imbalance.
Coordination is not a soft concept. It is a structural design choice across incentives, information flow, and decision rights. By the end of this chapter, you should be able to identify coordination failure patterns, choose fit-for-purpose contract and control mechanisms, and run a weekly coordination cadence that improves service reliability without uncontrolled cost inflation (Lee et al., 1997; Simchi-Levi et al., 2008).
Canonical Grounding (Sourcing and Coordination)
- Bullwhip dynamics driven by ordering behavior, pricing, and information distortion (Lee et al., 1997).
- Information sharing and replenishment coordination in network performance.
- Contract mechanisms (buy-back, revenue sharing, quantity flexibility) to align chain incentives.
- Push-pull boundary logic and decoupling decisions in sourcing and replenishment design.
Working Heuristic (Author Synthesis): ALIGN Loop
Use the ALIGN loop for sourcing-coordination design:
- Architecture: Map who decides what across sourcing, planning, and sales. This exposes hidden decision conflicts.
- Link incentives: Align commercial and sourcing KPIs to shared service and margin outcomes. This reduces local optimization behavior.
- Information quality: Define one trusted demand and inventory signal source. This improves replenishment accuracy.
- Governance cadence: Run weekly exception reviews and monthly policy reviews. This sustains coordination discipline.
- Network resilience: Build backup options for critical suppliers and lanes. This reduces disruption impact.
Critical leadership rule
If suppliers are governed only on price while business goals require reliability and speed, service failure is designed-in.
Corporate Reality Check
Run this check before your next sourcing or S&OP cycle. It identifies where contract logic and operating behavior are misaligned.
Scan failure patterns first, then monitor signals each week. This helps you intervene before volatility becomes structural.
Common failure patterns:
- Procurement contracts reward unit-price reduction but ignore lead-time volatility.
- Sales campaigns are approved without capacity and replenishment feasibility checks.
- Supplier reviews focus on cost variance while OTIF degradation is treated as secondary.
Failure signals:
- Repeated emergency buying despite stable forecast windows.
- OTIF drops after commercial promotions.
- Fill-rate misses increase while total inventory remains high.
What to do instead: redesign KPI and contract logic around shared outcomes, and enforce one cross-functional coordination rhythm.
Case Lens (Documented Case): Barilla JITD and Coordination Redesign
Barilla's Just-in-Time Distribution case is frequently used to show that demand amplification is often a coordination and incentive problem, not only a forecasting problem. By improving information sharing and replenishment logic across entities, volatility can be reduced and service stability improved (Lee et al., 1997).
The transferable lesson for managers is clear: coordination gains require simultaneous redesign of contracts, metrics, and decision cadence.
Lesson: end-to-end alignment outperforms local optimization even when each function appears individually efficient.
Full Case Walkthrough (8-minute read)
Click here to read full case study
1. Case Context
In fragmented supply networks, each participant often makes decisions based on local targets and incomplete signals. This creates cyclical instability where upstream planning sees demand shocks that do not reflect final customer consumption.
The Barilla teaching case is important because it demonstrates a recurring pattern across industries: when replenishment logic depends on disconnected ordering behavior, chain-level performance degrades regardless of local efficiency efforts.
2. Decision Trigger
Leadership trigger in this setting: service volatility and cost escalation persist despite repeated planning interventions.
Typical trigger conditions:
- High order variability relative to actual sell-through.
- Frequent expediting and reactive allocation decisions.
- Margin pressure from mismatch, markdowns, and carrying cost.
The decision question becomes explicit: should replenishment remain order-driven, or shift to shared-signal coordination with stronger governance?
3. Timeline (Simplified)
| Phase | What Happened | Coordination Relevance |
|---|---|---|
| Legacy behavior | Local order optimization dominated planning | Demand amplification increased |
| Diagnosis phase | Mismatch and volatility patterns were analyzed | Root causes shifted from forecast blame to coordination design |
| Redesign phase | Shared data and replenishment rules introduced | Signal integrity improved |
| Stabilization phase | Governance and accountability routines hardened | Service and variability outcomes improved |
4. Options Considered (Managerial Framing)
Most organizations confronting this problem face three options:
- Keep current model and buffer with extra inventory.
- Keep model but enforce stricter ordering discipline.
- Redesign contract, signal flow, and control cadence together.
Option 3 is usually more durable because it addresses the structural drivers of volatility rather than absorbing symptoms.
5. Execution Moves
Execution moves that transfer across sectors:
- Define one source of truth for demand and inventory signals.
- Segment suppliers and SKUs by risk, criticality, and variability.
- Align campaign approval with sourcing and capacity constraints.
- Run exception governance with owner, due date, and escalation logic.
- Use contract clauses that reward reliability and responsiveness, not only price.
For managers, the key insight is practical: policy and incentive design drive coordination quality more than dashboard volume.
6. Outcomes and Evidence
When coordination design improves, organizations generally see lower volatility, better fill-rate performance for priority categories, and reduced emergency procurement.
Evaluate outcomes in three layers:
- Service layer: fill rate and OTIF stability in critical categories.
- Economic layer: inventory turns, working capital, and expedite cost.
- Governance layer: exception closure speed and policy adherence.
Caveat: benefits decay quickly if cross-functional accountability is not sustained.
7. What to Transfer to Managerial Practice
What to copy:
- Establish one cross-functional cadence for demand, sourcing, and replenishment decisions.
- Track and reduce manual overrides that distort planning signals.
- Tie supplier and internal KPIs to shared outcome metrics.
What to adapt:
- Contract structure by supplier maturity and category risk profile.
- Review frequency by volatility and service criticality.
What to avoid:
- Price-only sourcing scorecards.
- Promotions approved without sourcing feasibility review.
- Static policy settings despite shifting demand behavior.
8. What We Know vs What Is Inferred
| Category | Statement Type |
|---|---|
| What we know (documented) | Bullwhip dynamics are consistently linked to signal distortion and coordination gaps (Lee et al., 1997). |
| What is inferred (managerial synthesis) | The strongest enterprise lever is alignment of contract logic, incentives, and governance cadence. |
9. Discussion Questions
- Which current KPI most strongly encourages local optimization over chain outcomes?
- Where does your coordination process currently break: data, decisions, or incentives?
- Which supplier category should move first to reliability-linked contract logic?
- What exception threshold should trigger BU-level escalation?
- How should sourcing governance differ for stable vs volatile categories?
Monday Morning Playbook
30-minute prep
- Pull four-week data on fill rate, OTIF, expedite spend, and supplier lead-time variance. This creates an evidence baseline.
- Identify top ten SKUs by revenue and volatility. This focuses decisions where value and risk are concentrated.
- List recurring coordination exceptions with owner and function. This reveals repeat failure patterns.
60-minute coordination review
- Validate policy fit for priority segments in the first 15 minutes. This aligns stakeholders on target posture.
- Review top exceptions and root causes in the next 20 minutes. This isolates where alignment fails.
- Approve two contract/process corrections with owners in the next 15 minutes. This creates accountable interventions.
- Lock escalation and checkpoint dates in the last 10 minutes. This ensures closure discipline.
7-day follow-through
- Publish an exception closure dashboard with named owners. This keeps execution visible.
- Run one policy experiment on a high-volatility category. This generates rapid learning under control.
- Review impact in next week's cadence and update rules. This institutionalizes learning loops.
Role-Based Activation
- People Manager: Enforce one non-negotiable handoff rule per day. This reduces avoidable coordination loss.
- Functional Leader: Remove one approval bottleneck causing late replenishment decisions. This improves flow speed.
- BU Leader: Align sales, sourcing, and operations incentives to one shared service-margin objective. This reduces policy conflict.
- Strategy Office: Maintain a quarterly coordination-risk map by supplier and category. This improves proactive resilience planning.
KPI and Evidence Block
Track leading, lagging, and risk indicators in one evidence view. This helps balance reliability, cost, and resilience under changing demand.
Review these metrics at the stated cadence with named owners. This turns coordination from intention into managed execution.
| Metric Type | Suggested Metric | Review Cadence |
|---|---|---|
| Leading | % priority SKUs with policy-compliant replenishment | Weekly |
| Leading | Exception closure within agreed SLA | Weekly |
| Lagging | Fill rate for A-category SKUs | Monthly |
| Lagging | OTIF by supplier tier | Monthly |
| Risk | Expedite procurement spend as % of sourcing spend | Weekly |
Tools Pack
Tool 1: Coordination Fit Card
For each category, define:
- Demand profile: Stable / Seasonal / Volatile
- Supplier posture: Cost-led / Balanced / Reliability-led
- Replenishment logic: Push / Hybrid / Pull
Tool 2: Exception and Escalation Log
| Exception | Root Cause | Owner | Escalation Trigger | Due Date | Status |
|---|---|---|---|---|---|
Practice MCQs
Q1.
What is the first managerial decision in sourcing coordination design?
- A. Expand supplier count immediately
- B. Define decision rights and shared outcomes across functions
- C. Automate procurement approvals only
- D. Increase safety stock uniformly
Q2.
If procurement optimizes unit price while BU targets require reliability, the likely result is:
- A. Stronger service stability
- B. Coordination conflict and service volatility
- C. Lower complexity
- D. No meaningful effect
Q3.
Which operating intervention usually stabilizes coordination fastest?
- A. Annual sourcing strategy workshop
- B. Weekly exception review with cross-functional owners
- C. Large ERP replacement
- D. Adding policy documents
Q4.
What is a strong leading indicator of sourcing-coordination health?
- A. Office utilization
- B. Exception closure within SLA
- C. Annual headcount growth
- D. Brand recall score
Q5.
Which statement best explains durable improvement in coordination performance?
- A. Tool upgrades alone are sufficient
- B. Contract logic, incentives, and cadence must be aligned together
- C. One-time negotiation resets are enough
- D. Coordination is mainly a forecasting issue
Flashcards
Click the card to flip
Continue Learning
References
- Lee, H. L., Padmanabhan, V., & Whang, S. (1997). The bullwhip effect in supply chains. Harvard Business Review. https://hbr.org/1997/04/the-bullwhip-effect-in-supply-chains
- Simchi-Levi, D., Kaminsky, P., & Simchi-Levi, E. (2008). Designing and managing the supply chain (3rd ed.). McGraw-Hill.
Coordination advantage is built when incentives, contracts, and cadence reinforce one shared operating outcome.