Beliefs

Here is the uncomfortable truth Part IV insists on: you cannot see the true state of your project. You see reports, metrics, and test results — shadows of the state, arriving late and distorted. So you reason about a belief instead.

Parts I–III let you at least observe which situation you were in. Real projects deny even that. The schedule status you're shown is a lagging summary; the "green" on the dashboard may be optimism; the true health of the work is hidden behind imperfect signals. The right object to reason about is therefore not the state but a belief: a probability distribution over which state the project might actually be in, given everything you've observed so far.

1Keeping the belief current: filtering

A belief must be updated as evidence arrives, and the update is pure Bayes. Start with your current belief; account for the effect of the action you took (the project moves on); then fold in the new observation, upweighting the states that would most likely have produced what you saw. The result is your revised belief. Repeated over time, this is Bayesian filtering — and the belief it maintains is a sufficient statistic of the entire history: carry it, and you can throw the raw log away.

Figure 1. A belief over hidden project states. An amber report is more likely to arise if the project is genuinely at risk, so observing it shifts belief toward that state. You act on this distribution — not on the raw report.

2Representing the belief in practice

For a handful of discrete states, keep the belief as an exact table of probabilities and update it directly.
For continuous quantities with roughly linear dynamics and noise, the Kalman filter keeps the belief as a Gaussian — a mean and a spread — updated in closed form. Its extended and unscented variants handle mild non-linearity.
For messy, non-linear, multi-modal situations, the particle filter represents the belief with a swarm of sampled hypotheses, reweighting and resampling them as evidence lands — flexible enough for almost anything.

Key idea

When you can't observe the true state, the honest object to hold — and to act on — is a belief: a probability distribution over where you might be, kept current by folding each new observation into the last. The belief, not the latest report, summarises everything you know.

What it means in practice

Stop treating the status report as the truth and start treating it as evidence about a hidden truth. Maintain an explicit, probability-weighted picture of where the project really stands — and, crucially, of how confident that picture is — updating it as each indicator arrives rather than lurching with every fresh number. A belief that carries its own uncertainty tells you not just your best guess at project health, but how much you should trust it, which is exactly what a good decision needs.

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 Beliefs. 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 Beliefs as a decision instrument rather than an administrative form. The subject terms—filtering, belief, bayesian, kalman, particle—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.