Exact Belief-State Planning

Combine everything Part IV has established — you can't see the state, only a belief — with the sequential decisions of Part II, and you arrive at the most faithful model of project decision-making there is. It is also one of the hardest problems in the field.

The partially observable Markov decision process (POMDP) extends the MDP with one honest admission: you never observe the state directly. Added to the usual states, actions, transitions and rewards is an observation model — the probability of each possible signal given the true (hidden) situation. You act, the world changes unseen, you receive a noisy observation, you update your belief, and you decide again. That is precisely the loop of running a real project.

1A POMDP is an MDP over beliefs

The key move that makes POMDPs tractable to think about is this: although you can't see the state, your belief (Chapter 18) is something you always know. And it turns out the optimal decision depends only on your current belief — so a POMDP is really an MDP whose "states" are beliefs. The catch is severe: beliefs are continuous, so this belief-MDP has infinitely many states. You've traded an unobservable state for an observable but infinite one.

2The structure that saves you: alpha vectors

Remarkably, the optimal value function over beliefs has a clean shape — it is piecewise-linear and convex. It can be represented by a set of alpha vectors, each corresponding to a conditional plan: a complete "if you see this, do that" strategy. The value of any belief is simply the best of these plans at that belief, and which plan is best depends on where your belief sits. Convexity carries a meaning worth savouring: value is highest when you're certain (at the edges) and lowest when you're maximally unsure — uncertainty itself is costly.

Figure 1. Each faint line is a conditional plan's value across beliefs; the bold upper envelope is the optimal value. Which plan is best depends on your belief: proceed when you're confident things are fine, escalate when you're confident they're not, investigate in the uncertain middle. Value dips lowest where you're least sure.

3Why exact solutions don't scale

Exact methods compute this set of alpha vectors — enumerating conditional plans and pruning those that are never best. They are correct and they define what "optimal" means. But the number of conditional plans explodes as the planning horizon grows: each extra step branches over every action and every possible observation. Exact POMDP solving is therefore feasible only for very small problems. Its lasting value is conceptual — it names the true problem, reveals its structure, and sets the target that the approximate methods of the next two chapters chase.

Key idea

The POMDP is the honest model of deciding without seeing the state, and its optimal policy is a library of conditional plans, each best for a certain range of belief. Exact solutions establish what optimal looks like; they simply cost too much to compute at any real scale.

What it means in practice

Recognise that managing a project genuinely is a POMDP — you act on beliefs about a state you can't see, and the right response shifts with your confidence, not just your best guess. The structure carries a practical lesson even without solving the maths: your response should depend on how sure you are, and uncertainty itself is expensive, so reducing it (better observations, earlier signals) has real value. The next chapters make this computable; this one makes it honest.

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 Exact Belief-State Planning. 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 Exact Belief-State Planning as a decision instrument rather than an administrative form. The subject terms—exact, alpha, vectors, planning, partially—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 Exact Belief-State Planning?