Structure Learning

Sometimes you don’t know which risks drive which. Structure learning tries to read that shape from the data — while being honest about what data alone can never tell you.

So far the diagram — which factor points to which — was drawn by hand from domain knowledge. Often that is right and proper. But sometimes the relationships are exactly what you’re unsure of: does the design maturity drive the rework, or do both simply track an aggressive schedule? Structure learning asks whether the data itself can suggest the graph, rather than assuming it.

1Scoring a candidate structure

The core move is to define a score for any proposed structure and then prefer high-scoring ones. A good score balances two forces in tension. It rewards fit — how well the structure explains the observed data — and it penalises complexity — how many links and parameters the structure demands. The penalty is essential: a fully connected graph can always fit the data best, yet it memorises noise and predicts the future worst. Standard scores (the Bayesian score, or the closely related information-criterion penalties) formalise this trade-off.

Figure 1. A structure’s score is roughly its fit minus a penalty for complexity. The over-connected model fits marginally better but pays a heavy complexity price — so the leaner, more general model wins. This is the mathematical guard against reading noise as signal.

2Searching an astronomical space

You cannot score every possible structure — the number of valid graphs grows faster than exponentially in the number of variables. Instead you search: start somewhere, then repeatedly try small local edits — add an edge, remove an edge, reverse an edge — and keep any change that improves the score. It’s a greedy climb toward a good-enough structure, not a guaranteed-best one, and that pragmatic trade is exactly why it’s usable on real datasets.

3The limit you must respect: Markov equivalence

Here is the caution that matters most for risk. Several different diagrams can encode identical statistical relationships. From observational data alone, “A causes B” and “B causes A” can be completely indistinguishable — both predict the same correlations. Such indistinguishable structures form a Markov equivalence class. Learning can recover the skeleton (which factors are linked) and orient some arrows, but it cannot, in general, tell you the direction of every link without either a controlled intervention or genuine domain knowledge.

Figure 2. Two structures that fit the data equally well. Observational correlation cannot separate them; only an experiment or outside knowledge can settle the direction of the arrow. Reading causation off correlation here is a guess, not a finding.

Key idea

Data can propose the wiring of a risk model and prune the implausible, but it cannot always tell you which way the influence runs. The honest output of structure learning is often a shape with some arrows left deliberately undirected.

What it means in practice

Use data to challenge your assumed risk drivers — you may find links you never registered, or discover that two “separate” risks are really one. But treat any causal claim the data hands you with discipline: if the direction of influence would change your decision, you probably need a deliberate test or hard domain reasoning to establish it, not another correlation. Structure learning is a superb way to generate hypotheses about what drives your risk, and a poor way to prove them.

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 Structure Learning. 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 Structure Learning as a decision instrument rather than an administrative form. The subject terms—structure, learning, model, scoring, searching—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 Structure Learning?