Discovery & Diagnosis.

How to understand an organisation as it actually is — not just as it presents itself. The formal state and the informal one. Where the resistance will be before it appears.

Programmes compressing discovery were 2.7x more likely to face implementation challenges requiring redesign

McKinsey (2023)

The uncomfortable finding from discovery is the finding that changes the programme. That is the value. Full evidence →

Full practitioner methodology in the CN Portal Log in →

The key principles

How CN approaches this work.

Understand the informal organisation, not just the formal one

The org chart shows reporting lines. Discovery reveals influence lines. The person whose view shapes what forty people think may be two levels below the senior sponsor. The team that will quietly sabotage the programme may not appear anywhere in the stakeholder map. Discovery finds them.

Listen for what is not being said

People in organisations are skilled at saying the right things in formal settings. Discovery is designed to create conditions where the real picture emerges — the frustrations, the workarounds, the "this will never work because..." conversations that happen after the consultant leaves the room.

The burning platform must be real

If people do not believe the case for change is genuine and urgent, the change will not happen. Discovery tests whether the burning platform — as presented by leadership — is felt as real by the people who will have to change. If it is not, the programme design must address that gap before anything else.

Document what you find, not what you hoped to find

Discovery findings that confirm the original hypothesis are incomplete. The value of discovery is in the surprises — the unexpected resistance, the hidden dependency, the assumption in the business case that the organisation does not share. Those are the findings that prevent programme failure.

The readout is a deliverable, not a formality

The discovery readout to the sponsor is a genuine deliverable. It should contain uncomfortable findings. A readout that only confirms what the sponsor already believed has not done its job.

What good looks like

✓Discovery interviews include sceptics and opponents, not just supporters
✓Informal influence network mapped explicitly
✓Burning platform tested at multiple levels of the organisation
✓Readout contains findings that surprise the sponsor
✓Assumptions in the business case explicitly tested and challenged
✓Current state assessed across all six operating model layers
✓Resistance hotspots identified by name and team before programme design begins

Warning signs

✗Discovery limited to senior stakeholders who support the programme
✗Findings shaped to confirm the original brief
✗Informal organisation ignored — only formal structure mapped
✗Readout presented as a formality before the "real work" begins
✗Burning platform assumed rather than tested
✗Current state assessment based on documentation rather than observation

Diagnostic questions

Use these in client conversations or team reviews to quickly surface where the real issues are.

QHave you interviewed someone who thinks this programme is a bad idea — and genuinely listened to why?

QCan you name the three people in each affected team whose informal opinion will determine whether this change holds?

QDoes the sponsor know something uncomfortable that came out of discovery?

Full Practitioner Guide

The complete methodology is in the CN Portal.

The full guide covers: discovery interview design, stakeholder mapping methodology, informal network analysis technique, burning platform testing, current-state assessment across six OM layers, discovery readout structure, and how to handle findings that challenge the programme brief.

Access Portal Join the network