Actor–Critic Methods

Part II has run two threads — estimating the value of situations, and directly tuning the decision rule. Actor–critic methods weave them into one.

Value-based methods (Chapters 6–8) ask "how good is this state?" and act greedily. Policy methods (Chapters 9–11) tune the decision rule directly but lean on noisy outcome signals. Actor–critic methods take the best of both: a critic that learns to judge situations, feeding a lower-noise signal to an actor that improves the decision rule. It is the synthesis the whole part has been building toward, and the backbone of modern reinforcement learning.

1Two roles, one loop

The actor is the policy — it chooses actions. The critic is a value function — it estimates how good the current situation and the actor's choices are. Instead of judging each decision against the raw, noisy final return (as bare policy gradients do), the actor is updated using the critic's assessment, which is far steadier. In turn, the critic learns from what actually happens as the actor acts. Each improves because the other does.

Figure 1. The actor decides; the environment (the project) responds; the critic evaluates the result and passes a cleaned-up "advantage" signal back to the actor. Forecasting and action improve together in a single loop.

2The advantage signal, and refinements

The critic's most useful output is the advantage: how much better (or worse) an action turned out than the critic expected. Positive advantage reinforces the choice; negative discourages it. Generalized advantage estimation tunes the trade-off between a low-noise but slightly biased advantage and a high-noise but unbiased one. A deterministic policy gradient variant suits continuous actions, and pairing an actor–critic with the tree search of Chapter 8 produces the class of systems that mastered games like Go — a learned critic guiding the search, the search improving the actor.

Key idea

An actor decides and a critic judges. Because the actor learns from the critic's steady assessment rather than from raw noisy outcomes, the pair improves faster and more reliably than either approach alone.

What it means in practice

The most effective risk operating models pair the same two roles: a forecasting capability that continuously assesses how healthy each project is, and a decision function that acts on those assessments — with each feeding the other. The forecaster tells the decision-maker not just the outcome but whether it beat expectations; the decision-maker's actions give the forecaster fresh evidence to sharpen its judgement. Neither the dashboard nor the playbook works nearly as well in isolation.

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 Actor–Critic 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 Actor–Critic Methods as a decision instrument rather than an administrative form. The subject terms—actor, critic, methods, value, estimation—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 Actor–Critic Methods?