Overview
Manufacturing Outsourcing: A Knowledge Perspective examines outsourcing as a knowledge problem as well as a cost and capacity decision. Effective decisions depend on historical and contextual knowledge about products, processes, performance, suppliers, and the trade-offs built into the operating model.
The authors use theory, practical examples, and case studies to show how organizations can acquire, create, transfer, and use the knowledge needed to make outsourcing work. The emphasis is especially relevant where responsibility crosses company or geographic boundaries.
The book organizes outsourcing choices around structural questions—what to make or buy, where activity should sit, and which partner to select—and infrastructural questions about coordination, integration, performance, and learning. Each choice depends on knowledge that can be fragmented across engineering, operations, procurement, suppliers, and prior projects.
Key ideas
- Cost is only one decision input. Reliability, capability, flexibility, innovation, and the knowledge consequences of moving work also shape long-term value.
- Historical context supports make-or-buy choices. Managers need evidence about product performance, process dependencies, suppliers, and previous decisions.
- Knowledge crosses organizational boundaries imperfectly. Language, incentives, systems, and commercial relationships influence what partners share and understand.
- Outsourcing can weaken internal learning. Moving execution elsewhere may also reduce the experience from which future design and operational judgment develop.
- Integration requires explicit ownership. Someone must maintain the interfaces, assumptions, escalation routes, and feedback loops between organizations.
Why it matters for handovers
Work rarely moves cleanly with a procedure alone. The receiving party also needs assumptions, quality expectations, escalation paths, known failure modes, and the reasoning behind past decisions.
That reinforces a broad Flamekeeper principle: a handover must capture relationships, decision context, and operational exceptions alongside the nominal process. The same principle applies whether work moves to a colleague, a new team, or an external partner.
Questions to carry into a handover
- Which design or operating knowledge must remain inside the organization even if execution moves outside it?
- What assumptions and escalation paths sit at the boundary between internal teams and suppliers?
- Which supplier relationship or performance history would be invisible in the formal contract?
About the authors
Asbjørn Rolstadås, Bjørnar Henriksen, and David O'Sullivan combine research and industry experience in production management, manufacturing strategy, outsourcing, innovation, and applied knowledge management. Rolstadås built a long academic and industrial career in production management; Henriksen worked in consultancy and applied research at SINTEF and NTNU; and O'Sullivan researched manufacturing strategy and innovation while working with multinational companies. That mix supports the book's movement between theory, decision frameworks, and cases.