CWC Consulting

What is
Behaviour Execution Risk (BER)?

Behaviour Execution Risk (BER) is the risk that human behaviour, through unspoken assumptions, misaligned incentives, conflicting operating norms and divergent decision-making, undermines Execution Integrity: the state in which a transformation delivers the outcomes it was commissioned to achieve. BER is a programme risk category. It is tracked and governed like delivery risk or financial risk, not managed as a “people side” concern through engagement surveys and training rollouts.

What BER is made of

Five things that make a programme drift

  • Human behaviour

    What people actually do once the design meets their working day.

  • Unspoken assumptions

    Beliefs nobody wrote down, and nobody tested.

  • Misaligned incentives

    Teams rewarded for outcomes the programme does not need.

  • Conflicting operating norms

    Two functions, two sets of rules, one shared process.

  • Divergent decision-making

    The same evidence reaching opposite conclusions.

Together these are Behaviour Execution Risk, the single largest driver of transformation failure.

The evidence

Why BER matters

Research consistently places the failure rate of digital transformations at over 80%, with roughly 70% of those failures attributable to behavioural and cultural factors rather than technology or architecture.

BER is CWC Consulting's term for what that research is describing: the quiet, cumulative divergence between what the programme was designed to achieve, what gets built, and what people actually do with it.

Traditional delivery disciplines already instrument technical risk through RAID logs, control testing and dependency mapping. BER surfaces the behavioural equivalent, and does so early enough to govern against: operating-model conflict, incentive misalignment and adoption drift.

The symptoms

How BER manifests

None of these appear on a RAID log. Read as a register, they are what a behaviour risk entry actually looks like.

  1. Erodes Strategic Intent

    Contradictory models

    1. Business and I&T hold contradictory models of what the transformation is for.
    2. The divergence stays invisible until delivery forces a choice between them.
  2. Erodes Adoption

    Quiet reversion

    1. Teams quietly revert to old ways of working after go-live, without anyone escalating.
    2. Benefits are reported against a process nobody is following.
  3. Erodes Delivery

    Unsustainable decisions

    1. Programme governance ratifies decisions that frontline operations will not sustain.
    2. The gap surfaces as rework, not as a governance failure.
  4. Erodes Strategic Intent

    Sponsor drift

    1. Sponsor commitment visibly weakens as delivery slips into the embedding phase.
    2. The embedding window closes without an owner.
  5. Erodes Adoption

    Cultural reassertion

    1. Cultural norms that pre-dated the transformation reassert themselves inside the new processes.
    2. The operating model drifts back without anyone choosing it.

The technical build may be sound. The failure is in the alignment.

Intent, delivery, and adoption: the three dimensions of Execution Integrity.

The method

How CWC surfaces and governs BER

CWC's methodology combines Enterprise Architecture discipline with Organisational Psychology, Leadership, and Culture consulting. That combination is what makes behaviour risk visible in programmes where it would otherwise go undetected.

Our two core instruments are:

Frequently asked questions

Frequently Asked Questions

Change resistance is a symptom. BER is the underlying system of behavioural, cultural, and governance patterns that produces it.

Treating resistance alone (through communications, training, or workshops) addresses the surface. Treating BER addresses the mechanism, the misaligned incentives, unspoken norms, and conflicting operating models that make resistance rational.

As early as possible, and continuously.

Before Target Operating Model sign-offHighest leverage

Build and delivery

Go-live

Start of embeddingSecond highest

The highest-leverage moment is before the Target Operating Model is signed off, when behavioural assumptions baked into the design can still be revisited at low cost. The second-highest-leverage moment is at the start of the embedding phase, when BER usually compounds silently if left unchecked.

Yes. The BER Snapshot is CWC's diagnostic instrument.

It surfaces behaviour risks by sector, by programme phase, and by functional interface, producing a prioritised risk register that complements (rather than replaces) the programme's existing RAID log.

In his words

Deen on why this matters

Two minutes with CWC's Managing Director on what Behaviour Execution Risk looks like inside a live programme, and why it rarely reaches the risk register until the cost is embedded.

Video to come

Deen Balogun, Managing Director, CWC Consulting