How to build a product management course: a complete guide for lecturers

Central question: What is the product manager accountable for, and how should decision rights work across product, design, engineering, marketing, sales and finance?

Product Management is often weakened by role confusion. Students may imagine the product manager as a project coordinator, a mini-CEO or the person who writes requirements. A stronger opening establishes the role as one of evidence-led product judgement: deciding which customer problems matter, what outcomes the product should create, what not to build, and how cross-functional teams will make and revisit those choices.

What this concept covers

• Product Management as an integrative business discipline, not a single-function role.
• Product versus project, programme, marketing and engineering management.
• Product operating models, empowered teams, decision rights and accountability.
• Outcome ownership, product discovery, product delivery and commercial responsibility.
• Stakeholder influence without relying on formal authority.

Learning outcomes

By the end of this concept, students should be able to:

• Distinguish Product Management from adjacent management roles.
• Map the main stakeholders and decision rights around a product.
• Define product outcomes that connect customer value and business value.
• Explain why product decisions require evidence from several functions.

How to teach it

• Give students one product and ask who owns the problem, solution, roadmap, launch and financial outcome.
• Use a responsibility map to compare weak feature-factory behaviour with an outcome-led product team.
• Ask groups to write a one-paragraph product-manager charter with explicit non-responsibilities.

Case-style example

SignalDesk, a B2B support platform with 50,000 monthly users and $4 million ARR, has 1,200 engineering hours available next quarter. Sales wants enterprise SSO, support wants reliability work and growth wants a freemium tier. Students build a decision-rights map, then recommend who should decide the next-quarter priority and what evidence must be supplied. One defensible answer prioritises revenue; another protects reliability. Students discover that Product Management coordinates a decision system rather than owning every decision.

Where students struggle

Students often equate authority with accountability. The product manager may own the quality of the product decision without directly managing the people who provide the evidence or build the solution.

Reading and a quick check

Set the role chapter from the core text alongside a short current piece on product-team collaboration. Quick check: ask students to write one decision a product manager should own and one they should influence but not own.

Applied teaching activity

Use the case-style example, a structured critique or a short product-review workshop. The aim is to make the decision observable without forcing a simulation where it does not add value.

Where it leads

With the role clear, the course can move to the first source of evidence: customers, users and the problem they are trying to solve.

Central question: Which customer problem is important enough to solve, and what evidence would prove that the team has framed it correctly?

Good Product Management begins before a feature idea. Students need to separate observed customer behaviour from proposed solutions, distinguish stated preferences from revealed needs, and learn how interviews, observation, support data and usage evidence contribute to problem definition. This concept also creates a foundation for ethical research, sampling discipline and evidence quality.

What this concept covers

• Problem statements, jobs, pains, gains and desired outcomes.
• Qualitative interviews, observation, surveys, support data and behavioural evidence.
• Research questions, sampling, bias and evidence triangulation.
• Customer versus user, buyer, administrator and other stakeholder roles.
• Problem severity, frequency, current alternatives and willingness to change.

Learning outcomes

By the end of this concept, students should be able to:

• Design a research question that does not presuppose a solution.
• Evaluate the quality and limitations of customer evidence.
• Distinguish a customer problem from a feature request.
• Write an evidence-backed problem statement and identify remaining uncertainty.

How to teach it

• Run a short interview clinic where students identify leading and neutral questions.
• Give groups the same set of messy interview notes and ask them to code needs independently.
• Require a problem brief with evidence, counter-evidence and a statement of what remains unknown.

Case-style example

ClinicLoop is considering an automated reminder feature because 18% of appointments are missed. The team has 42 interview notes, 1,800 support tickets and six months of booking data. Students code the evidence, then decide whether the real problem is forgetting, scheduling friction or lack of commitment. One team may build reminders; another may redesign cancellation and rescheduling. Students discover that the same headline metric can support different product hypotheses when the underlying behaviour is interpreted differently.

Where students struggle

Students tend to collect confirming quotes and call them validation. Push them to look for non-users, failed workarounds, contradictory evidence and situations where the problem is present but the proposed solution would still be rejected.

Reading and a quick check

Use the core text chapters on problem find-solve and concept generation. Quick check: give students three customer quotes and ask which one is evidence of a problem, which is a solution request and which needs follow-up.

Where a simulation fits

The Startup Creation Simulation fits after students have learned basic discovery methods. It gives teams a reason to turn market research and customer needs into a product concept, value proposition and MVP rather than treating research as a standalone report.

Where it leads

Once students can define a problem, they need to judge whether the opportunity is large, reachable and attractive enough to justify product investment.

Central question: Which market and customer segment should the product serve first, and what makes that choice economically and strategically attractive?

Product managers rarely have the resources to serve everyone. This concept connects market sizing, segmentation, competitive alternatives and strategic context to an explicit choice of where to play. The aim is not to produce a decorative TAM slide, but to decide which segment offers the best combination of need, reachability, differentiation and economics.

What this concept covers

• TAM, SAM and SOM as decision aids rather than headline numbers.
• Segment definition using needs, behaviours, context and economics.
• Direct competitors, substitutes and current workarounds.
• Internal strengths and weaknesses alongside external opportunities and threats.
• Segment attractiveness, accessibility, urgency and strategic fit.

Learning outcomes

By the end of this concept, students should be able to:

• Build an evidence-based segment definition.
• Compare segments using customer, market and commercial criteria.
• Interpret competitive context without defaulting to feature checklists.
• Defend a focused initial market rather than an undifferentiated target.

How to teach it

• Give groups three possible segments and require a weighted segment scorecard.
• Ask students to map the customer alternative, not only named competitors.
• Use a short SWOT workshop to connect internal capability with external opportunity without turning SWOT into a list.

Case-style example

TrailPay sells expense software. The small-business segment has 20,000 reachable firms, a £45 monthly willingness to pay and £600 estimated CAC. Mid-market has 4,000 firms, £420 monthly willingness to pay and £4,500 CAC. Enterprise has 500 firms, £2,500 monthly willingness to pay and £35,000 CAC. Students rank the segments, state assumptions and choose a beachhead. Different conclusions are defensible depending on retention and sales-cycle assumptions. Students discover why market size alone does not determine priority.

Where students struggle

Students often produce broad demographic segments that do not change product or go-to-market decisions. A useful segment should imply different needs, value propositions, product choices or economics.

Reading and a quick check

Pair the opportunity-identification chapter with a current strategy reading. Quick check: ask students to explain why a large TAM can coexist with a poor first target segment.

Where a simulation fits

The SWOT Analysis Simulation can support strategic diagnosis after students know how to distinguish internal capabilities from external conditions. The Go To Market Simulation becomes more valuable later, once students can convert segmentation into targeting and positioning.

Where it leads

A chosen segment creates the next question: what promise should the product make to that customer, and how should it be positioned against the alternative?

Central question: Why should the chosen customer switch to this product rather than keep the current alternative?

A product concept needs more than a list of features. Students should learn to articulate the customer, the important problem, the promised outcome, the reason to believe and the relevant alternative. This creates a bridge from discovery to product strategy and later to messaging, pricing and launch.

What this concept covers

• Customer value propositions and explicit target users.
• Functional, emotional and economic benefits.
• Positioning relative to a customer alternative or competitor.
• Product concept statements and reason-to-believe evidence.
• Consistency between promise, product capability, proof and price.

Learning outcomes

By the end of this concept, students should be able to:

• Write a focused value proposition for a defined segment.
• Separate product benefits from features and technical mechanisms.
• Construct a positioning statement that names a meaningful alternative.
• Identify what evidence would make the promise credible.

How to teach it

• Ask students to rewrite feature-heavy copy into outcome language.
• Give the same product to different segments and compare how the value proposition changes.
• Use a concept test where students predict which claim a sceptical buyer would challenge first.

Case-style example

HomeChef Pro is a meal-planning app aimed at time-poor families. It can launch with automated weekly menus, grocery-list integration and nutrition tracking. Research shows 62% of target users care most about saving planning time, while 28% prioritise nutrition. Students write two alternative value propositions and choose which one should lead the product concept. One emphasises convenience; the other healthier routines. Students discover that positioning is a strategic choice about which value to foreground, not a summary of every feature.

Where students struggle

Students frequently write value propositions that apply to everyone and therefore guide no product decision. Make them state the segment, alternative and measurable outcome the proposition is intended to improve.

Reading and a quick check

Use the concept-generation and concept-evaluation chapters. Quick check: give students a value proposition and ask them to identify the customer, problem, outcome, alternative and proof gap.

Where a simulation fits

The Startup Creation Simulation fits strongly here because teams must construct a value proposition and translate customer evidence into a startup concept. Later, the Go To Market Simulation tests whether positioning can survive pricing, messaging and market-entry trade-offs.

Where it leads

A credible concept must now sit inside a product strategy: a set of choices about where to play, how to win and what the team will not do.

Central question: What coherent set of choices will create customer value and business value, and what will the product deliberately not pursue?

Product strategy is where students move from insight to choice. A useful strategy connects target customer, product advantage, business model, capabilities and measurable outcomes. It should also define exclusions. If every attractive idea fits the strategy, the strategy is not doing enough work.

What this concept covers

• Product vision versus strategy, goals, tactics and roadmap.
• Where-to-play and how-to-win choices.
• Business model, revenue logic, cost drivers and strategic constraints.
• Strategic assumptions, risks, dependencies and non-goals.
• Product objectives linked to company-level goals.

Learning outcomes

By the end of this concept, students should be able to:

• Translate research into a coherent product strategy.
• Distinguish strategic choices from feature plans and slogans.
• Evaluate strategic fit between customer value and business model.
• State non-goals and assumptions that make the strategy falsifiable.

How to teach it

• Give students a one-page strategy template that forces choices and non-goals.
• Ask teams to critique strategies that contain goals but no choices.
• Use a pre-mortem: what assumption would make this strategy fail even if delivery is excellent?

Case-style example

OrbitClass serves 100,000 university users with 52% semester-to-semester retention. Management proposes an AI tutor, a marketplace and a corporate-training version. The product team has capacity for one major bet and a £700,000 annual development budget. Students choose one direction, write the strategic rationale and name two non-goals. A growth-first team may choose corporate expansion; a retention-first team may choose the tutor. Students discover that strategy creates value by concentrating scarce attention, not by collecting opportunities.

Where students struggle

Students often confuse vision, objective, strategy and roadmap. Keep asking: what choice has been made, what alternative has been rejected, and what evidence would make the team revisit that choice?

Reading and a quick check

Use the strategic elements, opportunity selection and product protocol chapters. Quick check: ask students to convert a goal such as "grow active users" into a strategy containing a target, advantage and non-goal.

Where a simulation fits

The Startup Creation Simulation supports business-model and growth-strategy choices. The SWOT Analysis Simulation can be used as a structured challenge to the strategy when students need to connect internal capability and external conditions to a recommendation.

Where it leads

Strategy narrows the field. Product managers then need a transparent method for turning that direction into priorities and a roadmap.

Central question: How should a product team allocate scarce capacity across customer value, strategic goals, technical work, risk and commercial commitments?

Prioritisation is one of the most visible product-management decisions and one of the easiest to teach badly. Students should use frameworks as aids to judgement, not as calculators that hide judgement. The strongest exercises force trade-offs between revenue, customer outcomes, risk reduction, learning and technical health.

What this concept covers

• Backlog versus roadmap versus product portfolio.
• Prioritisation criteria such as value, reach, confidence, effort, risk and strategic fit.
• Dependencies, capacity, technical debt and mandatory work.
• Now-next-later and outcome-based roadmaps.
• Portfolio balance between core, adjacent and exploratory bets.

Learning outcomes

By the end of this concept, students should be able to:

• Build a prioritisation model whose criteria reflect strategy.
• Challenge the inputs and false precision of scoring frameworks.
• Create a roadmap that communicates outcomes and uncertainty.
• Defend why lower-scoring work may still be strategically necessary.

How to teach it

• Give every group the same backlog but different strategy and capacity constraints.
• Require a roadmap plus an appendix showing rejected items and why.
• Run a stakeholder challenge where sales, engineering and compliance each contest the order.

Case-style example

FleetIQ has 24 roadmap candidates and only 40 engineer-weeks next quarter. A £300,000 renewal depends on audit logging, 4,000 users request mobile alerts, a reliability project could reduce incidents by 35%, and an AI feature is forecast to generate 600 trials but has weak evidence. Students choose a 40-week portfolio and defend it. A revenue-protection plan and a reliability-first plan can both be credible. Students discover that prioritisation frameworks expose assumptions but do not remove accountability for trade-offs.

Where students struggle

Students can become attached to a single scoring formula. Push them to examine confidence, dependencies, irreversible commitments and the cost of delay, then explain when a score should be overridden.

Reading and a quick check

Use the full-screen and product-protocol chapters. Quick check: ask students which roadmap item they would remove first if capacity fell by 25% and why.

Applied teaching activity

Use the case-style example, a structured critique or a short product-review workshop. The aim is to make the decision observable without forcing a simulation where it does not add value.

Where it leads

The roadmap identifies what should be explored next. The course can now move into designing the smallest credible product or experiment that reduces uncertainty.

Central question: What is the smallest product or prototype that can test the important assumptions without under-building the customer experience?

MVP is often mistaken for a poor first version. In Product Management, the purpose is learning: identify the riskiest assumption, choose the lowest-cost way to test it, and decide what evidence would justify further investment. Students should also distinguish prototypes, concierge tests, pilots, beta releases and production MVPs.

What this concept covers

• MVP as a learning vehicle, not a fixed feature threshold.
• Prototypes, fake-door tests, concierge tests, pilots and beta releases.
• Product requirements, acceptance criteria and product protocol.
• Build-versus-buy and scope decisions under time and budget constraints.
• Usability, reliability, accessibility, legal and reputational minimums.

Learning outcomes

By the end of this concept, students should be able to:

• Match an uncertainty to an appropriate prototype or MVP method.
• Write a concise requirement that states outcome and acceptance evidence.
• Define a minimum quality bar as well as minimum feature scope.
• Explain what the team should learn before committing further resources.

How to teach it

• Start with an expensive product proposal and ask groups to design a one-week learning test.
• Compare three MVPs that test desirability, feasibility and viability respectively.
• Require an explicit decision rule: if metric X is below Y, stop, change or investigate.

Case-style example

LumaCare plans a medication-adherence product with a £300,000 budget and 12-week window. The full idea includes reminders, caregiver alerts, pharmacy integration, analytics and a clinician dashboard. Students must design a four-week MVP that tests whether patients will use reminders consistently while preserving safety and privacy. One group chooses a coded app; another chooses a managed pilot. Students discover that the best MVP is the cheapest credible test of the riskiest assumption, not the smallest collection of features.

Where students struggle

Students frequently ask "what features belong in the MVP?" before asking "what uncertainty are we reducing?" They also underweight non-negotiable safety, accessibility, privacy or trust requirements.

Reading and a quick check

Use the design, development and product-use-testing chapters. Quick check: give students an assumption and ask whether a prototype, pilot or production MVP is the lowest-cost credible test.

Where a simulation fits

This is the strongest placement for the Startup Creation Simulation. Product development and MVP creation sit alongside market research, validation, business-model choices, branding and the investor pitch, so students must connect product scope to the wider venture logic.

Where it leads

A built or simulated MVP does not end the learning cycle. Students next need metrics and experiments that show whether behaviour changed in the intended direction.

Central question: What evidence should cause the team to continue, iterate, pivot or stop?

Metrics matter when they are tied to a decision. Students should learn to build a measurement model from product outcome to user behaviour, define leading and lagging indicators, and design experiments that can change a product decision. Product-market fit should be treated as a bundle of evidence rather than a single magic threshold.

What this concept covers

• North-star, input and guardrail metrics.
• Activation, conversion, engagement, retention, churn and cohort analysis.
• Experiment hypotheses, control groups, A/B testing and validity threats.
• Qualitative evidence alongside quantitative behaviour.
• Product-market fit, scaling signals and pivot decisions.

Learning outcomes

By the end of this concept, students should be able to:

• Define metrics that connect product behaviour to an outcome.
• Design an experiment with a decision-relevant hypothesis.
• Interpret experiment results without confusing statistical movement with strategic importance.
• Build an evidence case for continuing, iterating or pivoting.

How to teach it

• Give groups a dashboard with vanity metrics and ask them to rebuild it around decisions.
• Have students pre-register a hypothesis, success threshold and guardrail before seeing results.
• Compare strong short-term conversion with weak retention to force a product-market-fit debate.

Case-style example

Tutorly has 40,000 sign-ups, 38% activation and 17% eight-week retention. A new onboarding flow raises activation to 46% in a 6,000-user test, but early support contacts increase from 8% to 13%. Students decide whether to ship, run a longer test or redesign. A growth team may accept the support cost; an experience team may reject it. Students discover that experiments answer defined questions and create trade-offs - they do not automatically produce the product decision.

Where students struggle

Students often optimise the metric that is easiest to move. Require a causal story connecting metric movement to durable customer and business value, plus a guardrail that makes hidden costs visible.

Reading and a quick check

Assign Koning, Hasan and Chatterji on A/B testing alongside the market-testing chapters. Quick check: ask students to name the metric that would make an apparently successful experiment a failure.

Where a simulation fits

The Startup Creation Simulation supports the broader validation cycle, especially when the debrief asks students which assumptions were truly tested and which were merely asserted.

Where it leads

Evidence of demand still needs to translate into a sustainable product. The next concept connects product choices to price, cost, margin and investment economics.

Central question: Can the product create enough customer value and economic value to justify continued investment?

Product managers do not need to become management accountants, but they do need fluency in the economics their choices create. This concept connects price, volume, variable cost, contribution margin, break-even, customer acquisition, retention and product investment so students can distinguish attractive usage from attractive economics.

What this concept covers

• Pricing objectives, willingness to pay and price architecture.
• Variable and fixed costs, contribution margin and break-even.
• CAC, lifetime value, retention, payback and revenue quality where relevant.
• Investment appraisal and opportunity cost across product bets.
• How product scope and service requirements change economics.

Learning outcomes

By the end of this concept, students should be able to:

• Calculate and interpret basic product contribution economics.
• Compare pricing options using customer and financial evidence.
• Identify which product assumptions drive break-even and investment value.
• Recommend a product investment using more than topline growth.

How to teach it

• Use a simple product P&L with three pricing scenarios.
• Ask students to explain which costs the product decision can actually influence.
• Compare two products where the higher-revenue option has weaker contribution economics.

Case-style example

PureSip plans a smart reusable bottle. At £79, unit variable cost is £31, expected annual support cost is £7 and paid acquisition is £24 per customer. A £99 price reduces forecast volume from 18,000 to 13,500 units but cuts support demand by attracting a more committed segment. Students calculate contribution and break-even under both options, then recommend a price. One answer maximises adoption; another protects margin. Students discover that pricing is a product decision because it changes segment, usage expectations and economics together.

Where students struggle

Students can treat finance as a late approval gate. Product economics should be visible during prioritisation because feature scope, service level, channel choice and pricing all change the cost-to-serve and value of the product.

Reading and a quick check

Use the sales-forecasting and financial-analysis chapter. Quick check: ask which assumption matters more to product value - a 10% price increase, a 10% retention increase or a 10% reduction in variable cost - and require the calculation.

Where a simulation fits

The Managerial Accounting Simulation fits directly. Students compare products using contribution margin, break-even, margin of safety, ROI and NPV, then allocate a limited budget across opportunities from different executive perspectives.

Where it leads

A product with a credible economic case must still be delivered through a cross-functional system that manages dependencies, quality and stakeholder commitments.

Central question: How does a product manager move from direction to reliable delivery without turning the roadmap into a promise that cannot adapt?

Product Management sits between uncertainty and delivery. Students should understand agile principles, iterative planning and team interfaces, but the teaching focus should stay on product judgement: how discovery and delivery interact, how scope changes are governed, how trade-offs are communicated and how quality is protected.

What this concept covers

• Discovery and delivery as connected loops.
• Agile planning, increments, releases and evidence-based scope change.
• Product, design and engineering collaboration.
• Dependencies with sales, operations, legal, finance and customer success.
• Stakeholder communication, escalation and decision logs.

Learning outcomes

By the end of this concept, students should be able to:

• Build a delivery plan that preserves room for learning.
• Identify dependency and stakeholder risks before they become schedule surprises.
• Write decision logs that preserve rationale and assumptions.
• Respond to scope pressure without hiding trade-offs.

How to teach it

• Use a launch plan with hidden dependencies and reveal them in rounds.
• Ask students to rewrite a date-based roadmap as outcome plus confidence ranges.
• Run a stakeholder meeting where each group has different success criteria.

Case-style example

LedgerFox has three product squads preparing a regulatory reporting release in eight weeks. Engineering estimates 10 weeks, sales has promised a date to 12 enterprise clients and legal identifies a new audit requirement worth 20% of total effort. Students choose whether to reduce scope, move the date or add temporary capacity, then write the stakeholder message. Different choices are defensible if risks are explicit. Students discover that product leadership means making constraints visible early rather than hiding them behind delivery optimism.

Where students struggle

Students can over-focus on ceremonies and tools. The key question is whether the operating rhythm helps the team learn, make decisions and deliver customer value with an acceptable level of risk.

Reading and a quick check

Pair the development-team-management chapter with a current product-operating-model reading. Quick check: ask students which part of a roadmap is a commitment, which is a forecast and which is an option.

Applied teaching activity

Use the case-style example, a structured critique or a short product-review workshop. The aim is to make the decision observable without forcing a simulation where it does not add value.

Where it leads

Delivery creates a product that can enter the market. The next concept connects segmentation, positioning, price, channels and launch execution.

Central question: How should the product reach the right customer, with the right positioning, price, proof and channel strategy at launch?

A product is not successful because it ships. This concept makes launch a cross-functional commercial decision. Students connect the earlier choices on segment, value proposition and price to messaging, channels, proof, sales enablement, onboarding and adoption. The goal is a launch system that makes clear whom the product is for and what evidence will show whether adoption is working.

What this concept covers

• Segmentation, targeting and positioning for launch.
• Pricing, packaging, messaging and proof strategy.
• Paid, owned, earned, partner and sales channels.
• Launch readiness across product, support, operations and sales enablement.
• Adoption, activation and post-launch learning.

Learning outcomes

By the end of this concept, students should be able to:

• Design a focused go-to-market plan for a defined target segment.
• Connect positioning and price to a coherent channel strategy.
• Define launch-readiness criteria and adoption metrics.
• Adjust a launch plan when market conditions change.

How to teach it

• Require a one-page launch brief with target, message, price, channel and proof.
• Give groups a fixed launch budget and force allocation across channels.
• Introduce a post-launch twist such as competitor discounting or demand surge.

Case-style example

NexaHome is launching a smart energy monitor with a £600,000 launch budget. Homeowners offer a £120 gross margin but need education; small landlords offer £85 margin with faster repeat purchase; energy consultants offer lower volume but strong referral credibility. Students choose the first target, set the lead message and allocate budget across paid media, partnerships and sales enablement. Different plans can work. Students discover that a coherent GTM strategy is a set of reinforcing choices, not a list of channels.

Where students struggle

Students may treat launch as a marketing handoff. Product managers need to connect what was built, who it serves, what it costs, how the value is explained and what the team will learn after release.

Reading and a quick check

Use the strategic launch planning, implementation, market testing and launch management chapters. Quick check: ask students which launch assumption they would test before spending the full budget.

Where a simulation fits

The Go To Market Simulation is the strongest fit. Students act as market strategy leads, use segmentation, targeting and positioning, then make connected choices on pricing, messaging, proof strategy and brand focus before responding to a changing market scenario.

Where it leads

Launch begins the operating lifecycle. The final concept asks how the team should grow, improve, maintain or retire a product as evidence changes.

Central question: How should a product evolve after launch, and when should the team invest, optimise, reposition, maintain or retire it?

Product Management is a lifecycle discipline. Students should learn how acquisition, activation, retention, expansion, cost-to-serve and strategic relevance change as a product matures. This final concept also provides a place to discuss responsible product decisions, deprecation, migration and the organisational consequences of keeping weak products alive.

What this concept covers

• Post-launch growth loops and adoption constraints.
• Retention, expansion, churn and lifecycle cohorts.
• Continuous discovery and roadmap revision.
• Product-line rationalisation, maintenance and sunset criteria.
• Migration, customer communication, ethics and responsible deprecation.

Learning outcomes

By the end of this concept, students should be able to:

• Diagnose whether a growth problem is acquisition, activation, value or retention.
• Recommend when to invest, reposition, maintain or sunset a product.
• Design a migration plan that considers customer and operational risk.
• Use lifecycle evidence to revise the original product strategy.

How to teach it

• Give students a mature portfolio with revenue, growth, support cost and strategic-fit data.
• Ask them to recommend invest, maintain, harvest or sunset for each product.
• Require a customer migration plan for one product they choose to retire.

Case-style example

PulseBoard has £6.2 million ARR, 4% annual growth, 14% logo churn and £1.1 million annual support and infrastructure cost. A newer platform has £3.4 million ARR, 46% growth and can absorb 70% of legacy customers after a six-month migration project costing £500,000. Students choose whether to maintain, merge or sunset PulseBoard. One view protects current cash flow; another accelerates migration. Students discover that lifecycle decisions balance customer trust, strategic focus and opportunity cost, not only short-term revenue.

Where students struggle

Students often assume successful Product Management is endless growth. Mature products may create more value through simplification, migration or retirement, provided the organisation handles customer impact and evidence responsibly.

Reading and a quick check

Use the launch-management and public-policy chapters alongside a current reading on products that evolve with users. Quick check: ask students to name the metric that would trigger a sunset review and the customer evidence needed before acting.

Where a simulation fits

The Managerial Accounting Simulation can support portfolio trade-offs and resource allocation. The SWOT Analysis Simulation can be used where the lecturer wants students to revisit strategic fit under changed internal and external conditions.

Where it leads

This closes the lifecycle. Students should now be able to move from opportunity and discovery through strategy, build, launch, measurement and lifecycle decisions while defending the trade-offs at each stage.

10-week course structure

A 10-week version should compress adjacent decisions rather than remove the product lifecycle. Combine role with discovery, combine strategy with prioritisation, and protect one session each for MVP/validation, product economics and launch.

14-week course structure

A 14-week version creates room for deeper discovery, a separate concept-testing session, more analytics, simulation reflection and a fuller lifecycle capstone. Use the extra time for decision quality rather than simply adding more frameworks.

The Startup Creation Simulation is the closest direct fit to the discovery-to-MVP half of a Product Management course. The published case materials describe a 4-5 hour team experience in which groups move through a startup creation process and work with Business Model Canvas, business planning, product development and MVP, market research and validation, branding and marketing, and investor pitching.

Why it fits here

By the end of Session 7, students have already framed a customer problem, chosen a market, written a value proposition, set product direction and designed an MVP. The simulation lets them connect those choices rather than treating the MVP as an isolated design exercise.

What students do

• Form a coherent startup concept and business model around a target market.
• Use market research and customer-needs evidence to refine and validate the proposition.
• Make product-development and MVP choices rather than jumping straight to a full solution.
• Articulate the value proposition and distinctive customer benefit.
• Connect product choices with branding, marketing strategy and the commercial model.
• Prepare an investor-facing pitch that explains the opportunity, product and growth logic.

Recommended course placement

• At the end of Session 7 after MVP and product-development teaching.
• Across Sessions 7 and 8 when the lecturer wants a separate validation and debrief session.
• Before an assessed product strategy or MVP memo so teams can revise assumptions using the simulation experience.

Knowledge students should have before the simulation

• Customer problem and basic discovery evidence.
• Target customer and market segment.
• Value proposition and basic business-model logic.
• MVP as a test of an assumption, not simply a reduced feature set.

Delivery format

Suggested debrief questions

• Which customer assumption shaped your product most strongly?
• What did your MVP actually test, and what did it leave untested?
• Where did product scope conflict with the business model or pitch?
• Which piece of evidence would make you change the target user or value proposition?
• What did you build or propose because it was easy rather than because it reduced uncertainty?

The Go To Market Simulation provides a hands-on new-product launch decision. The published product page describes students acting as market strategy leads and applying Segmentation, Targeting and Positioning to analyse customer groups, select a focused market-entry strategy and position a product through pricing, messaging, proof strategy and brand focus. The activity is designed for roughly 2-4 hours and can be delivered in class, online or hybrid.

Why it fits here

By Session 11, students already hold the product concept, segment, positioning and economics. The simulation can therefore focus on integration: whether those choices still cohere when launch resources are limited and a market scenario changes.

What students do

• Analyse available customer groups and choose which segment should receive primary focus.
• Apply targeting and positioning rather than trying to serve every customer equally.
• Set pricing and make messaging choices that support the intended position.
• Choose proof and brand focus to make the proposition credible in market.
• Balance focus, reach, profitability and risk when launch choices conflict.
• Respond to a market twist such as booming demand, intense competition or an economic downturn, then reconsider the original plan.

Recommended course placement

• At the end of Session 11 after go-to-market teaching.
• Across Sessions 11 and 12 if the lecturer wants a launch decision followed by lifecycle and growth debrief.
• Before the final capstone so students can revise the launch section of their product recommendation.

Knowledge students should have before the simulation

• Segmentation and targeting.
• Positioning and value proposition.
• Basic pricing and product economics.
• Launch objectives and product-readiness logic.

Delivery format

Suggested debrief questions

• Which segment did you reject, and what would have to change to make it attractive?
• Did your price strengthen or weaken your intended positioning?
• Which proof point mattered most to customer credibility?
• What did the market twist reveal about the fragility of your launch plan?
• If you could run one experiment before launch, what would you test?

Grading with the Startup Creation Simulation

Teams work across a startup creation process that includes market research and validation, value proposition, product development and MVP, business-model and marketing decisions, and an investor pitch. Use the simulation as applied evidence rather than the grade itself.

• Quality of customer and market assumptions.
• Coherence between target user, value proposition and MVP.
• Evidence that product scope addresses a stated uncertainty.
• Quality of business-model and growth trade-offs.
• Individual ability to explain what the team would change after the simulation.

Grading with the Go To Market Simulation

Students act as market strategy leads and make connected decisions on segmentation, targeting, positioning, pricing, messaging, proof strategy and brand focus before responding to a changing market scenario.

• Quality of segment selection and evidence.
• Consistency between positioning, price, message and proof.
• Ability to balance focus, reach, profitability and risk.
• Response to new market information.
• Individual defence of the chosen launch trade-offs.

Grading with the Managerial Accounting Simulation

Students compare products using contribution margin, break-even, margin of safety, ROI and NPV, then allocate a $100 million budget across opportunities from CFO, COO and CMO perspectives before making a final CEO allocation.

• Calculation accuracy and interpretation.
• Ability to connect cost structures and product positioning.
• Quality of product selection and investment rationale.
• Recognition of trade-offs between executive perspectives.
• Individual explanation of which metric or assumption drove the recommendation.

Grading with the SWOT Analysis Simulation

Students evaluate a high-stakes expansion opportunity from competing perspectives, organise evidence through the SWOT framework and defend a strategic recommendation. Use the exercise to assess strategic diagnosis rather than the neatness of the four-box output.

• Correct distinction between internal strengths/weaknesses and external opportunities/threats.
• Evidence quality and materiality.
• Logic connecting diagnosis to the recommendation.
• Recognition of conflicting but defensible interpretations.
• Individual ability to explain which factor would change the decision.