Before the Pattern Sets: What Gets Established in the Early Weeks of a Major Programme

In the third week of a nuclear alliance mobilisation, a senior engineer has raised a concern about a potential interface conflict in the secondary systems to his line manager twice. The line manager believes it is probably manageable - likely something the team will work through once delivery begins - and has suggested the engineer park it while the mobilisation milestones take priority. The engineer has registered the response. He will not raise the concern again until he is certain, which means he will raise it when the evidence is undeniable, which is also when addressing it will be most expensive.

Nothing catastrophic has happened. A reasonable management judgement has been made under time pressure, by someone trying to keep a complex mobilisation on track. And in doing so, something has been decided about this programme that nobody explicitly agreed to: the social contract about which kinds of concerns are welcome at which moments, and what it costs professionally to raise them.

What the most common form of programme assessment captures is a different picture. The risk register records what has been formally raised. The mobilisation satisfaction survey measures overall sentiment. The governance meeting minutes note actions and decisions. In all of this, the mobilisation appears to be proceeding well, and it is - except that a pattern about professional honesty is already forming below the level of formal record, at a speed and in a direction that none of these instruments are designed to detect.

How this pattern forms is well-researched and specific. People calibrate their willingness to raise concerns against evidence they can observe directly - what has actually happened when others in this programme or organisation spoke up. Stated policy and aspirational values form part of the backdrop, but in a new programme or alliance, the relevant evidence set develops quickly and from only a few early interactions. Three or four instances in the first weeks - a concern met with "let's park that for now," a challenge acknowledged but not acted on, a risk surfaced in the governance meeting and then quietly managed out of the register - are sufficient to establish what the programme actually expects from its people, regardless of what the alliance charter says.

By the time an organisation recognises this pattern as problematic, it has typically been setting for months, and changing it requires substantially more effort than understanding it at inception would have taken. Operational pressure makes this correction harder still, because the moment at which the accumulated concerns tend to surface is also the moment at which the programme's capacity to absorb new problems is at its most stretched.

This is the diagnostic window that most major programmes do not use. In the early weeks of a programme, before the social contract has been fully established through experience, the professional and psychosocial conditions that determine whether people will raise concerns early, challenge decisions at the right moment, and surface problems at a point where they can still be addressed at reasonable cost are both measurable and developable. They are not fixed characteristics of the organisations or individuals involved. They form through specific interactions, and they can be assessed with some precision at a point in the programme lifecycle when the assessment still has the power to change something.

Nuclear delivery makes this visible with particular clarity. Great British Nuclear's SMR programme, Hinkley Point C, and Sizewell C each require leadership teams drawn from different organisational backgrounds - civil engineering, nuclear operations, defence, public sector commissioning - to collaborate under sustained commercial and schedule pressure on decisions where the cost of getting things wrong is severe. Whether those leadership teams have the specific conditions that allow professional honesty to operate at the moments that matter is not a question that safety compliance metrics or general engagement surveys are designed to answer. It requires specific assessment of the conditions that predict whether people will actually behave as the programme needs them to, as distinct from behaving as the programme's policies expect them to.

The insight from the third week of that nuclear alliance is that the conditions for genuine challenge, honest support, and the evolution of the work are being created or shut down at a point when the programme's attention is entirely focused on governance milestones and mobilisation metrics, which is, fair enough, where formal accountability currently sits. The conditions forming underneath that formal picture are not visible in the standard reporting. They are, however, measurable - and they are measurable before the pattern has finished setting, which is when measuring them is actually able to support action.

What would change in your programme design if you treated the psychological conditions of the first month as seriously as the governance structure that surrounds them?

References
Edmondson, A. (1999) Psychological safety and learning behavior in work teams, Administrative Science Quarterly, 44(2), pp. 350-383.
Great British Nuclear (2025) SMR programme framework.