Model-Based Methods

If the trouble is that you don't know how the project behaves, the most natural response is to find out — build a model from what you observe, then use everything from Part II to plan against it.

Model-based methods close the gap between "unknown model" and "everything we can do once we have one". You interact with the environment, record what happens, assemble those observations into an estimated model of the dynamics and rewards, and then plan against that learned model using the exact and approximate methods of Part II. As more experience arrives, the model sharpens and the plan improves. It is learning and planning, interleaved.

1Learn, plan, act, repeat

The cycle is straightforward. Act in the environment; observe the transition and reward you received; fold that observation into your model estimate (in the simplest case, tally the observed frequencies of each transition, exactly the parameter learning of Chapter 3); then plan against the current best model to choose what to do next. A Bayesian variant keeps a whole distribution over possible models, which connects directly to exploration — you can plan to visit states precisely because they'd teach you the most about the model.

Figure 1. Model-based learning interleaves four steps: act, observe, update the learned model, and plan against it. Each observation improves the model; the improved model yields a better plan — so every scrap of real experience is reused many times.

2Why it's frugal with experience

The great virtue of model-based methods is sample efficiency. Real interactions are expensive — in a project, a single observation might be a whole month of delivery — so you want to squeeze maximum value from each. A learned model lets you do exactly that: every real observation improves the model, and then you can plan (or simulate) against that model as much as you like at low cost. Some approaches deliberately blend a little real experience with a lot of cheap simulated experience drawn from the learned model, getting more improvement per costly interaction.

Key idea

Don't just react to outcomes — assemble them into a model of how your project actually behaves, then plan against it. A learned model turns each expensive observation into repeated planning value, which is why model-based methods learn fastest when data is scarce.

What it means in practice

Early in a project — or the first time you attempt a new kind of project — you don't yet know its dynamics, so build the model as you go: capture how this project actually responds to your actions, and plan against that captured understanding rather than a generic assumption. This is organisational learning made systematic. Because project data is precious and slow to gather, the discipline of extracting a reusable model from every observation, then planning hard against it, is exactly where model-based thinking earns its keep.

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Model-Based Methods. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to convert the subject into a governed decision, owned work, usable evidence and a reviewable outcome. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Use Model-Based Methods as a decision instrument rather than an administrative form. The subject terms—learning, model-based, model, experience, planning—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.

Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.

A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.

Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.

Step-by-step operating method

Clarify the decision. Name the outcome, sponsor, affected stakeholders and decision that this work must enable.
Set boundaries. Record scope, assumptions, constraints, dependencies, tolerances and escalation conditions.
Plan the evidence. Define deliverables, measures, owners, due dates and acceptance criteria before execution.
Control delivery. Compare actual performance with the baseline, assess changes and manage risks and issues explicitly.
Close the loop. Confirm acceptance, transfer ownership, capture lessons and track benefits beyond handover.

Completion and governance protocol

Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.

Information type	Minimum useful content	Review test
Outcome	Observable change and intended recipient	Not merely a deliverable or activity
Measure	Definition, baseline, target, frequency and source	Two reviewers would calculate it the same way
Ownership	One accountable role plus contributors and approver	Authority matches responsibility
Uncertainty	Assumption, risk or issue with response and trigger	Status reflects current reality
Control	Version, approval, review date and change rule	Current baseline is identifiable

Common failure modes and recovery actions

1. Watch for

Producing a document with no named decision or accountable owner.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Mixing risks, current issues, assumptions and actions in one unstructured list.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Measuring activity or output while leaving the intended outcome undefined.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Accepting changes without evaluating effects on value, scope, schedule, cost and risk.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Closing the project at delivery even though benefit ownership has not transferred.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.

Review checklist

Which decision or commitment does this artefact support?
Who owns each action, risk, acceptance and post-project benefit?
What is the baseline and what variance triggers escalation?
Where is the evidence that the result was accepted and transferred?
Are mandatory requirements distinguished from recommendations and illustrative values?
Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
Is there a named owner and a trigger for review, escalation, change or retirement?

Questions for deeper application

What is the most important distinction a practitioner must preserve when applying Model-Based Methods?