State Uncertainty

Combine the strategic uncertainty of Part V with the state uncertainty of Part IV and you reach the most tangled situation of all: no one sees the whole picture, and each party knows things the others don't.

This chapter is where partial observation meets multiple agents. Now you must reason on two fronts at once — about the hidden state of the world and about what the other parties know, believe, and will do given their own private information. It is the formal home of information asymmetry, and it underlies procurement, bidding, disclosure, and disputes.

1Games of incomplete information

When agents hold private information — a contractor knows its true costs; a bidder knows its own valuation — the interaction becomes a Bayesian game. Each agent has a "type" capturing what it privately knows, and each reasons about the probability distribution over the others' types. A competitive tender is the archetype: you choose a bid without knowing rivals' costs, so you reason about the distribution of what they might do and best-respond to that. Strategy becomes inseparable from belief about who you're dealing with.

Figure 1. Each party sees only a slice of the hidden truth and must reason not just about the state, but about what the other knows — and what the other thinks they know. These nested, recursive beliefs are the essence of strategic interaction under information asymmetry.

2Decentralised decisions and recursive beliefs

When several agents each act on their own partial observations, possibly without sharing what they see, you have a decentralised POMDP — among the hardest decision problems known, precisely because each agent must reason about others who are themselves reasoning under uncertainty. That opens an unnerving regress of recursive beliefs: what I believe about the state, what I believe you believe, what I believe you believe I believe, and onward. Exact treatment is intractable at any real scale, so practical work leans on bounded reasoning — modelling a few levels of this regress, not infinitely many.

Key idea

When information is held unevenly and no one sees the whole state, strategy and belief fuse: your best move depends on what others privately know and on what they think you know. Reasoning a level or two into that regress is usually as far as anyone can — or needs to — go.

What it means in practice

Information asymmetry is the water project professionals swim in — in procurement, claims, and negotiations, the other side always knows things you don't, and vice versa. Reason explicitly about what each party privately knows and, one level deeper, about what they assume you know; a surprising amount of negotiation turns on that second level. And recognise asymmetry as something you can act on: sometimes the winning move is to reduce it (due diligence, disclosure, independent verification), and sometimes it's to manage your own signalling with care.

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 State Uncertainty. 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 State Uncertainty as a decision instrument rather than an administrative form. The subject terms—information, games, decisions, bayesian, decentralised—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 State Uncertainty?