Course Guide
A practical, ready-to-adapt guide for designing or refreshing an Operations Strategy course. It brings together course positioning, constructively aligned intended learning outcomes, twelve core concepts with teaching notes, a 12-session syllabus, applied simulations, recent readings, case studies and assessment guidance.
An Operations Strategy course should teach students how organisations convert competitive priorities into long-term choices about performance objectives, processes, capacity, supply networks, inventory and working capital, technology, improvement, product and service development, resilience and implementation. A coherent 12-session design moves from strategic alignment and market requirements through process, capacity and network choices, then into working capital, digital operations, improvement, responsible operations and strategic control.
It can run as a final-year undergraduate module, an MSc or MBA elective, or executive education, typically across about 24-36 contact hours within 150-180 notional learning hours. The central distinction is between running today’s operation well and designing the operating system the organisation will need in the future. Students should learn to defend trade-offs using operational, financial and stakeholder evidence rather than optimise one metric in isolation.
teach Operations Strategy as a named or closely related course
sessions as the most common course-design model
taught at undergraduate level
taught at postgraduate level (levels overlap)
offered as core; the rest elective or capstone
include an applied or simulation-based component
Operations Strategy integrates market positioning, supply networks, investment economics, technology and responsible operations, making it a natural bridge between functional operations and enterprise strategy.
How well this course prepares students for six role families, scored out of 10. Indicative, based on how directly the concepts map to each path - not a placement statistic.
Each is mapped to the session where students already hold the concepts to make a defensible decision, rather than added as an activity at the end.
This guide is for professors, lecturers, educators, module leaders, course coordinators, unit convenors, instructors of record and programme directors designing or refreshing an Operations Strategy course in a university or business-school setting. It is globally portable across course, module and unit terminology and can be adapted to local credit structures, assurance-of-learning processes and course-approval requirements.
It is especially useful for final-year undergraduate, MSc, MBA and executive education cohorts where the course owner wants students to connect operational detail with strategic judgement. The page is a course-design guide rather than a technical operations handbook: it helps you sequence content, write intended learning outcomes, align assessment, place applied work and collect defensible evidence for course review.
An Operations Strategy course examines how an organisation builds an operating system that supports its competitive position over time. The lifecycle starts with strategic alignment and market requirements, then develops performance objectives, operations capabilities, process choice, capacity, supply networks, inventory and working capital, process technology, improvement, product and service development, resilience and responsible operations before closing with formulation, implementation and strategic control.
The applied challenge is to keep strategy distinct from routine operations management while grounding decisions in operational evidence. Students should learn that lowest cost, highest utilisation, least inventory or largest NPV are not automatically the right answers. They should judge when flexibility, headroom, supplier continuity, learning capability, digital readiness or responsible operations justify a different choice, and defend an integrated recommendation under uncertainty.
A one-screen planning view for syllabus design, module approval and constructive alignment. The detailed rationale and teaching notes sit in the sections below.
Planning area | Suggested approach |
|---|---|
Best fit | Final-year or senior undergraduates, specialist MSc/MS cohorts, MBA/EMBA and executive education. Best after an introductory Operations Management module. |
Typical length | 10, 12 or 14 teaching sessions, with 12 as the standard model. Roughly 24-36 contact hours plus independent study and assessment, giving about 150-180 notional learning hours. |
Course role | A specialist operations/strategy elective, an integrative capstone within Operations Management or Supply Chain programmes, or a strategic operations block within an MBA. |
Useful prerequisites | Introductory Operations Management or equivalent exposure to processes, capacity and inventory; basic spreadsheet and financial literacy. |
Main student output | An operations strategy board paper or consulting-style recommendation linking market requirements to process, capacity, supply network, technology, working capital, capability building and implementation. |
Best assessment fit | One group applied output carrying most of the summative weight plus an individual assumptions note, reflection or short oral defence that produces attributable evidence. Most courses use two assessment points rather than every format listed later. |
Best simulation fit | Working Capital Management after sourcing and inventory; Managerial Accounting after capability/process economics; Capital Budgeting for capacity/technology/development investment; ESG for responsible operations; Porter’s Five Forces for outside-in market requirements. |
The intended learning outcomes below use assessable verbs and are designed for constructive alignment with the cases, applied decisions and assessment options on this page. Bloom’s taxonomy appears once here because the point is practical: the course should move students from explanation and diagnosis toward evaluation, integration and defence, while producing evidence that can support course review and assurance-of-learning processes.
The sequence reflects patterns commonly seen in Ivy League and leading global business-school courses on Operations Strategy and closely related modules such as Operations Management, Supply Chain Management, Strategic Management, and Technology and Innovation Management. This is a course-design pattern, not a claim that every leading school teaches the subject in the same way.
There are twelve core concepts:
The following notes expand each core concept into a teaching question, suggested coverage, intended outcomes, teaching approach, runnable case-style example, likely difficulty, quick check and appropriate applied activity.
The alignment map below shows how the course moves from strategic direction to an integrated implementation decision. Requiring an output at each stage produces formative evidence session by session and makes the summative board paper an assembly of tested judgements rather than a new task at the end.
Stage of operations strategy work | Principal concepts | Expected student output | Assessment evidence |
|---|---|---|---|
Set strategic direction | Concepts 1-2 | Strategy map plus order-winner/qualifier scorecard | Formative evidence that students can translate market promises into operations priorities. |
Diagnose capabilities and architecture | Concepts 3-4 | Capability-gap map and process-choice recommendation | Evidence of inside-out reasoning and operating-model coherence. |
Commit structural resources | Concepts 5-6 | Capacity investment paper and supply-network recommendation | Evidence that students can compare scale, timing, ownership, dependency and risk. |
Manage operating economics | Concept 7 | Expansion-readiness recommendation | Quantitative and qualitative evidence linking cash, service, suppliers and growth. |
Move the performance frontier | Concepts 8-10 | Technology investment memo, improvement system and launch portfolio | Evidence connecting investment, learning and design to strategic performance. |
Protect and execute the strategy | Concepts 11-12 | Responsible-operations policy plus capstone board paper | Summative evidence of integrated judgement, sequencing and defence under uncertainty. |
A high-performing local metric is not automatically a good strategy. Credit the system-level judgement, the assumptions behind it and the consequences for other parts of the operating model.
The architecture can remain stable across final-year undergraduate, MSc, MBA and executive education cohorts. What changes is scaffolding, technical depth, ambiguity and the standard of defence expected. The aim is not to remove advanced themes from undergraduate teaching, but to make the evidence and decision path more explicit.
Undergraduate cohorts benefit from structured datasets, visible calculation steps and tightly framed cases. MSc cohorts can handle incomplete data and deeper financial/operational modelling. MBA and executive cohorts can move quickly into cross-functional conflict, stakeholder challenge, implementation sequencing and board-level defence.
Course design area | Undergraduate version | Postgraduate / MBA / executive version |
|---|---|---|
Course emphasis | Build the lifecycle clearly and make each framework visible before introducing ambiguity. | Move quickly into conflicting evidence, cross-functional disagreement, implementation constraints and board-level defence. |
Scaffolding | Structured cases, defined datasets, explicit calculation steps and a clear decision question. | Incomplete briefs, optional data, competing stakeholder claims and fewer prompts. |
Cognitive demand | Accurate concept use, comparison of alternatives and justified recommendations. | Assumption challenge, scenario design, integration across decision areas and defence under questioning. |
Quantitative depth | Accessible capacity, cost, working-capital and investment calculations. | Sensitivity analysis, capital rationing, scenario economics and more complex data interpretation. |
Cases and simulations | Guided preparation, clear objectives, structured worksheets and an explicit debrief. | Pressure tests, negotiation, assessment evidence or capstone integration with individual defence. |
Assessment | Correct application, clarity, evidence use and a defensible recommendation. | Judgement quality, trade-off recognition, evidence challenge, implementation logic and response to challenge. |
Each stage leaves behind a reusable decision artefact so the final capstone integrates work students have already tested and defended.
Session | Topic | Teaching focus | Student activity | Best-fitting simulation, where relevant | Assessment or output |
|---|---|---|---|---|---|
1 | What is operations strategy? | Strategic alignment; four perspectives; structural and infrastructural decision areas; operating-model coherence. | Classify decisions and build a customer-promise-to-operations strategy map. | One-page strategy map and decision classification. | |
2 | Performance objectives, order winners and trade-offs | Cost, quality, speed, dependability, flexibility; market requirements; order winners/qualifiers; performance frontiers. | Prioritise performance objectives for two segments and defend trade-offs. | Market-requirements scorecard and written priority rationale. | |
3 | Operations capabilities and resource-based advantage | Resources, routines, learning, path dependence, cumulative capability and operational economics. | Build a capability map and allocate a constrained investment budget. | Capability-gap memo with resource-allocation rationale. | |
4 | Process choice, design and operational focus | Volume-variety, process types, focused operations, service-process design, bottlenecks and complexity. | Redesign a mixed process and compare focused versus shared operating models. | Process-choice recommendation with performance consequences. | |
5 | Capacity strategy, scale, timing and location | Capacity cushions; lead/lag/track; scale; location; capital intensity; demand uncertainty. | Build base/downside demand scenarios and recommend a capacity path. | Capacity investment paper with scenarios and rejected alternative. | |
6 | Supply network, sourcing and supplier strategy | Make-or-buy, vertical integration, supplier segmentation, single/dual sourcing and network dependency. | Map a critical supply network and compare sourcing configurations. | Supply-network recommendation and dependency map. | |
7 | Inventory, working capital and expansion readiness | Inventory buffers, DSO/DIO/DPO, Cash Conversion Cycle, supplier/customer terms, service and liquidity. | Make month-by-month policy choices and defend an expansion recommendation. | Expansion recommendation plus working-capital assumptions note. | |
8 | Process technology, data and digital operations | Automation, analytics, AI, IoT, digital twins, data quality, skills and implementation risk. | Compare two digital investments and identify process/data prerequisites. | Digital-operations investment memo with implementation risks. | |
9 | Lean operations, quality and improvement capability | Lean, flow, standardisation, problem solving, quality, learning routines and cumulative capability. | Diagnose a failed improvement programme and design a sustained learning system. | Improvement-system design with cadence, measures and owners. | |
10 | Product and service development strategy | Design for operations, commonality, modularity, postponement, launch readiness and portfolio choices. | Select a constrained launch portfolio and identify operations-readiness gaps. | Product/service portfolio and readiness recommendation. | |
11 | Resilience, risk and responsible operations | Disruption, redundancy, flexibility, recovery, environmental/social trade-offs and stakeholder conflict. | Compare resilient networks and negotiate an operating-policy position. | Resilience and responsible-operations policy memo. | |
12 | Formulation, implementation and strategic control | Integrate choices; implementation sequence; capability roadmap; KPIs; review cadence; trigger points. | Build and defend a two-year operations strategy to a board-style challenge panel. | Capstone operations strategy and individual defence. |
Operations Strategy is a decision-led subject. Students can learn process, capacity, supply and technology frameworks from lectures, readings and cases, but the discipline becomes more realistic when they must commit to a policy, allocate scarce resources, respond to changing information and defend consequences for customers, suppliers, finance and other stakeholders.
Applied simulations belong after the relevant teaching, not as entertainment at the end. A structured briefing, explicit prior knowledge and documented debrief turn activity into assessable evidence. Simulation outputs support academic judgement; they do not replace it.
There is an accreditation dimension worth noting when building an internal case for experiential learning. The strongest argument is not that students enjoy a simulation, but that a structured applied component can generate auditable evidence of analysis, evaluation and decision-making when it is constructively aligned with the intended learning outcomes and debriefed deliberately.
If you need the accreditation language itself, what AACSB and AMBA say about simulations sets it out.
Teaching format | What it does well | Limitation | Best use in this course |
|---|---|---|---|
Traditional case study | Provides a rich written situation with exhibits and a defined decision context. | Students can discuss a recommendation without experiencing sequential consequences or competing roles. | Supply-network design, process choice, capacity, digital investment and resilience. |
Simulation | Requires students to analyse information, make trade-offs and commit to decisions with consequences or stakeholder opposition. | Needs preparation and debriefing; otherwise students may remember the activity rather than the concept. | Working capital, resource allocation, capital budgeting, ESG and market-structure judgement after relevant concepts. |
Working Capital Management is the strongest direct fit for Operations Strategy, with Managerial Accounting as a useful second deep dive. Capital Budgeting, ESG and Porter’s Five Forces can support specific sessions where their decision structure maps clearly to the course logic.
Course point | Simulation | How to use it | Why it fits |
|---|---|---|---|
Session 2: market requirements and order winners | Use Growth and Risk team analysis before translating industry structure into operational priorities. | Supports the outside-in lens without pretending industry analysis itself is operations strategy. | |
Sessions 3-4: capabilities and process economics | Use after students know product economics and capability trade-offs. | Connects contribution margin, break-even, ROI and NPV to resource allocation across CFO, COO and CMO perspectives. | |
Sessions 5, 8 or 10: investment choices | Use when students must compare projects and ration capital. | Applies NPV, IRR, Profitability Index and Payback, then forces a portfolio choice under a fixed $10 million budget. | |
Session 7: inventory, working capital and expansion | Use as the primary applied Operations Strategy simulation. | Connects DSO, DIO, DPO, Cash Conversion Cycle, inventory, commercial terms and expansion readiness over a 12-month scenario. | |
Session 11: resilience and responsible operations | Use after students can connect operating performance with stakeholder and sustainability consequences. | Management, Investor, Regulator and Union roles negotiate production, investment, ESG budget, wages and workforce choices while tracking financial and pollution outcomes. |
AI can accelerate first drafts of market summaries, process descriptions, capacity scenarios, supplier-risk lists, investment commentary, KPI suggestions and board-paper structure. That changes what a polished artefact proves. Credit should shift toward the assumptions students choose, the evidence they trust, missing information they identify and the decisions they can defend.
A practical permitted-use policy is clearer than leaving students to guess. AI can be allowed for brainstorming, structure, language checking and exploring alternatives where local rules permit, provided use is declared and students remain responsible for source verification, calculations, evidence selection and analytical choices.
AI is useful where operations decisions generate large volumes of information but still require constraints and context. It can help compare scenarios and organise evidence, but it cannot determine the organisation’s risk appetite, stakeholder priorities or willingness to invest in capability. Those remain strategic judgements.
Teaching area | AI implication | Lecturer response |
|---|---|---|
Market and performance analysis | AI can summarise customer, competitor and industry information quickly but may blur segment differences or fabricate evidence. | Require traceable sources, a defined segment and an explanation of which evidence changes an order winner or qualifier. |
Capacity and investment | AI can draft assumptions and scenarios but may hide units, time horizons or inconsistent constraints. | Require an assumption table, base/downside cases and a live defence of the chosen capacity path. |
Supply-network analysis | AI can map supplier risks but may miss tier-two dependencies or use stale geopolitical claims. | Credit source quality, dependency identification and what remains unknown; require current evidence for live risks. |
Working capital | AI can explain DSO/DIO/DPO and draft recommendations. | Assess whether students connect the metric to service, supplier continuity, cash and expansion consequences. |
Digital operations | AI can generate plausible automation use cases. | Require a causal chain from technology to process change to performance outcome, plus data and implementation prerequisites. |
Capstone board paper | AI can produce polished prose that weakens the assessment signal. | Shift credit toward assumptions, evidence selection, rejected alternatives, individual defence and response to challenge. |
Sample permitted-use rule: AI-assisted drafting is permitted where declared, but all evidence, calculations and recommendations remain the student’s responsibility and must be independently defensible in writing or oral questioning.
Core textbook: Nigel Slack and Mike Lewis, Operations Strategy, 7th edition, Pearson, copyright 2024. It is the strongest single-text fit because it moves from the meaning and performance of operations strategy into responsible operations, capacity, purchasing and supply, process technology, improvement, development, formulation, implementation, monitoring and control.
Alternative textbook: Nigel Slack, Alistair Brandon-Jones and Nicola Burgess, Operations Management, 11th edition, Pearson, 2026. Use it where students need broader operational foundations before strategy-level judgement.
The fictional cases in the Concept Details are designed to be licence-free seminar exercises with complete figures. For a longer assessed case, the following two published options are suitable and verified.
P. Fraser Johnson · Ivey Publishing via Harvard Business Publishing Education · 2023
Why it fits: Useful for capacity, global supply-network configuration, sourcing risk, vertical integration and the operations implications of rapid scale.
Best placement: Sessions 5-6 or Session 11.
Assessment fit: A network-design or board memo comparing capacity and sourcing alternatives under scale and disruption risk.
John R. Wells, Benjamin Weinstock, Galen Danskin and Gabriel Ellsworth · Harvard Business School · 2021
Why it fits: Supports discussion of operating model, fulfilment scale, technology, capacity, customer promise and how operations capabilities reinforce corporate strategy.
Best placement: Sessions 1, 4, 5 or 8.
Assessment fit: A strategy-coherence memo linking customer promise to process, capacity and technology choices.
Best placement: Session 7, after supply-network and sourcing strategy. Session aim: show that cash efficiency, service, supplier resilience and growth readiness can pull in different directions.
Session stage | Time | Teaching purpose | Lecturer approach | Student output |
|---|---|---|---|---|
Pre-class preparation | Before class | Give students the metrics and Northwood context so class time is used for judgement. | Assign a one-page primer on DSO, DIO, DPO and Cash Conversion Cycle plus the simulation briefing. | One-page note identifying one cash lever and one operational risk. |
Opening frame | 10 minutes | Set the strategic question. | Ask: “Can a company improve cash and become operationally weaker at the same time?” Establish expansion, service and supplier constraints. | Initial vote: Expand, Expand with Caution or Delay. |
Mini-lecture | 18 minutes | Connect working capital to Operations Strategy. | Link inventory buffers, supplier terms and customer credit to service, resilience, liquidity and growth capacity. | Three metrics plus the stakeholder affected by each. |
Simulation intro | 7 minutes | Move from concepts into the Northwood decision. | Launch Working Capital Management and confirm the evidence students should capture. | Personal decision log started. |
Working Capital Basics | 40 minutes | Check calculations and interpretation before policy changes. | Circulate while students work through fundamentals; use questions rather than giving the answer. | Completed metric analysis. |
Reflection checkpoint | 5 minutes | Make assumptions explicit before the 12-month stage. | Record which policy students expect to create most value and its main risk. | Short forecast and risk statement. |
Working Capital Management | 60 minutes | Experience sequential policy consequences. | Students manage receivables, inventory, payables and commercial terms across 12 simulated months. | Decision log with turning points and updated metrics. |
Expansion decision and debrief | 30 minutes | Convert outcomes into strategic judgement. | Require Expand, Expand with Caution or Delay; compare cases where cash improved but service or supplier resilience deteriorated. | Individual recommendation and two assumptions that would change it. |
Why this session matters: it demonstrates a central Operations Strategy habit: a locally attractive metric can create system-wide risk. Students leave with individual evidence that can be reused in the capstone strategy.
The intended learning outcomes reward judgement rather than recall, so assessment should ask students to recommend and defend. A common defensible design is one group applied output carrying most of the summative weight plus an individual component that produces attributable evidence, subject to local regulations. For example, 65% group operations-strategy board paper/presentation plus 35% individual assumptions note or oral defence.
Assessment option | What students do | Typical use |
|---|---|---|
Operations strategy board paper | Teams recommend a coherent set of process, capacity, network, technology and capability choices for one company. | 30-40% or the main component of a 60-70% group assessment. |
Board presentation and challenge | Teams defend the strategy under new information and stakeholder questioning. | Pair with the board paper; add individual questioning where marks must be attributable. |
Individual assumptions note | Each student states the three assumptions that matter most, the evidence used and what would change the recommendation. | 20-35%; strong for individual attribution and AI-resilient assessment. |
Case analysis | Students analyse one verified case and compare at least two strategic operating alternatives. | 20-40%; suitable for undergraduate or MSc cohorts. |
Simulation decision memo | Students convert an applied simulation into a recommendation linked to course concepts. | 10-25%; use as evidence and reflection, not score transfer. |
Capacity or investment paper | Students evaluate capacity, location, technology or development options using scenarios and investment evidence. | 15-30%; can be individual. |
Supply-network risk memo | Students redesign a sourcing/network configuration and defend cost, capability and resilience trade-offs. | 15-30%; works well with Apple or Tesla. |
Individual oral defence | Short viva-style questioning on evidence, assumptions and rejected alternatives. | 10-25% or for moderation/validation under local rules. |
The strongest courses keep bringing students back to system-level choices and long-term capability. The table below highlights common ways a strategy course can drift into disconnected tools or locally optimised metrics.
Common mistake | Why it weakens the course | Better approach |
|---|---|---|
Turning the course into tactical Operations Management | Students learn forecasting, scheduling or lean tools without seeing the long-term pattern of choices. | Use tactical methods only where they illuminate a strategic capacity, process, network, technology or capability decision. |
Treating frameworks as lists to memorise | Students reproduce five objectives or four perspectives but cannot make a choice. | Attach every framework to a segment, evidence set, recommendation and rejected alternative. |
Making cost the default objective | It hides speed, dependability, quality, flexibility and differentiation. | Use order winners and qualifiers to show what customers or stakeholders actually reward. |
Maximising utilisation without valuing headroom | High utilisation can look efficient while increasing delay, fragility and lost-demand risk. | Use demand ranges, capacity cushions and downside scenarios before recommending scale and timing. |
Teaching inventory only as a control problem | Students miss cash, service, supplier and resilience consequences. | Connect inventory to DIO, cash conversion, supplier terms, stockout risk and expansion readiness. |
Separating finance from operations | Good operating proposals can be unaffordable; attractive NPVs can ignore capability or implementation risk. | Combine operational logic with working capital, cost behaviour and investment appraisal. |
Adding digital and AI as a generic technology week | Content becomes trend commentary rather than operations strategy. | Require a causal chain from technology to process change, performance objective, capability requirement and measurable value. |
Treating lean and quality as toolkits | Students see one-off projects rather than a learning system. | Teach problem solving, standard work, management cadence and improvement routines as capabilities. |
Leaving resilience and responsibility until the end | Students optimise an efficient network and bolt on risk or sustainability afterwards. | Include risk and stakeholder consequences in capacity, sourcing and technology decisions, then synthesise in Session 11. |
Using simulations before students hold the concepts | Students remember competition or scores rather than why a decision was defensible. | Place simulations after relevant theory, state prior knowledge, require a decision artefact and run an explicit debrief. |
Subject-design questions come first, followed by operational, assessment and copy-paste utility questions.
The closest adjacent course for process design, capacity, quality, inventory and continuous improvement.
A natural extension for sourcing, network design, logistics, inventory and resilience.
Useful for linking operations choices to competitive positioning, capabilities and wider business strategy.
Useful for product economics, cost behaviour and resource-allocation foundations.
Inventory, receivables, payables, cash conversion and expansion readiness.
Product economics, investment metrics and cross-functional allocation.
If you are adapting this guide, preserve the progression from market requirements to operating choices, resource commitment, capability building and implementation. Then decide where students should make a consequential applied decision rather than adding activity for its own sake.
Request more information and book a demo
Tell Finsimco your course level, cohort size, teaching format and the part of Operations Strategy you want students to practise. The team can show how the relevant simulations fit into an existing syllabus rather than forcing you to redesign the module around the platform.