MGF5690 Chap.11 Service Sourcing and Supply
Service Sourcing and Supply
Service sourcing decides which capabilities remain internal, which are obtained from external providers and how the resulting relationship is governed. Cost matters, but so do strategic importance, customer contact, knowledge, uncertainty, reversibility and dependence. A contract can specify outputs and safeguards, yet complex services also require information sharing, escalation and relationship management.
Platform work adds algorithmic coordination and worker-control questions. Supplier diversity can strengthen access, innovation and resilience when selection and development preserve relevant capability and performance standards.
What this chapter covers
- 01
Internal, external and hybrid sourcing boundaries
- 02
Strategic importance, capability and transaction risk
- 03
Service specifications and performance measures
- 04
Governance, escalation and relationship quality
- 05
Platform work and algorithmic coordination
- 06
Supplier diversity, resilience and development
Worked example · free
Source a customer support function
- +2Separate routine contacts from complex cases that carry strategic customer and product knowledge.
- +2Use a hybrid boundary with clear routing, shared records, escalation and learning forums.
- +2Balance cost and response targets with resolution, customer effort, knowledge capture and dependency.
Key terms
- Sourcing boundary
- The division of service activities and decision rights between internal and external parties.
- Service-level agreement
- A documented set of expected service outputs, measures and responsibilities between parties.
- Supplier dependence
- Exposure created when important capability or continuity relies on a provider that is difficult to replace.
Service Sourcing and Supply FAQ
Why can a low-price supplier increase total service cost?
Poor fit can create monitoring, coordination, rework, escalation, switching and customer-recovery costs. Evaluation should include the operating relationship and failure consequences, not only the quoted unit price.
When is relational governance important?
It matters when work is uncertain, interdependent or difficult to specify completely. Shared problem solving and trust complement formal controls, but accountability, data access and escalation rights must remain clear.
How can supplier diversity improve operations?
A wider supplier base can offer market insight, innovation, access and resilience. Benefits require fair discovery and qualification, suitable work packages, capability development and performance expectations that remain relevant and transparent.
Assessment move
Start by defining the service capability and its importance to the customer promise. Evaluate boundary options through capability, knowledge, uncertainty, dependence, customer contact and reversibility before discussing provider price. Then specify how information, measures, decisions and escalation will cross the boundary.
Use balanced indicators: cost and response alongside resolution, quality, customer effort, resilience and knowledge retention. For platform or diversity cases, include the workers and smaller suppliers whose constraints may otherwise be hidden by transaction efficiency. Map the service at activity level before deciding what to source.
Routine transactions, specialist judgement, customer recovery, data stewardship and improvement learning may justify different boundaries even when they sit within one department. Mark which activities create strategic knowledge or direct customer trust. Evaluate internal, external and hybrid options against a consistent set of criteria.
Capability, scale and cost matter alongside uncertainty, observability, asset specificity, data sensitivity, switching difficulty and failure consequence. A provider's headline efficiency can be offset by coordination, monitoring, rework or lost learning, so explain total operating effects. Specify the service output in customer-relevant terms.
Response time alone can encourage premature closure; pair it with resolution, accuracy, effort or recurrence. Define data access, decision rights and escalation as carefully as targets. When work is difficult to specify completely, formal measures need relational governance that supports joint problem solving without obscuring accountability. Analyse the handoff between organisations.
State what context transfers, who retains case ownership and how a customer avoids repeating information. A contract cannot rescue a fragmented process if routing and records fail. Include governance forums, exception triggers and a learning loop from provider interactions into product or service improvement. Test dependence and reversibility.
Ask how quickly the organisation could replace capacity, recover data, retain critical knowledge or operate during provider disruption. Concentrating work may improve scale yet deepen exposure. A dual or staged arrangement carries extra coordination cost, which should be weighed against continuity and bargaining risk. Platform work requires examination of the coordination mechanism.
Ratings, automated allocation and opaque performance rules can shift risk to workers and influence customer outcomes. Identify whose behaviour the algorithm rewards and which appeal or safety process exists. Transaction convenience should not hide unstable capacity or poor job quality. Treat supplier diversity as an operational capability, not a symbolic count.
Smaller or underrepresented suppliers may contribute local insight, innovation and resilience, but procurement design, work-package size, payment terms and qualification can create barriers. Preserve relevant standards while making access and development practical. In the assessment, separate the sourcing boundary decision from supplier selection.
Support the boundary with evidence about the capability and uncertainty, then design governance for the chosen relationship. Track cost, quality, customer effort, resilience, workforce effects and knowledge retention. End with a plausible failure scenario and explain how responsibilities and continuity arrangements protect the service promise.
Working through Service Sourcing and Supply in MGF5690? Sia is AskSia’s AI Management tutor — ask any MGF5690 Service Sourcing and Supply question and get a clear, step-by-step explanation grounded in how MGF5690 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
