Skip to content
Nominal FR Let's talk about your project
Home/Perspectives/Organisation

The real problem is never the one announced

When a leadership team calls in an outside view, it arrives with a problem already named. That is normal, and it is almost always a symptom. The analysis begins by agreeing not to believe it straight away.

Driss Lebrun · October 2026 · 5 min read

01

The announced problem is a symptom

“Our lead times are slipping.” “The team can't keep up.” “We need a new tool.” Each of these sentences is true, and none is a cause. A slipping lead time is the consequence of something else: an approval that waits, information that arrives incomplete, a priority that changes three times in a week.

The trap is to treat the symptom because it is visible. A person is added, software is bought, one more meeting is organised. The symptom recedes for a while, then returns, often elsewhere.

02

Everyone is right about their part of the facts

Leadership sees the results and the gaps. Managers see the decisions they are asked to make. Teams see the work as it is really done, with its workarounds. Nobody is lying, and nobody has the whole picture.

That is why the analysis is done on site, and separately. A group interview produces a polite consensus; individual interviews produce facts. Put end to end, they trace the real path of a file, an order or a decision.

03

One question saves weeks

There is one Nominal asks every time: “What do you work around every day to make things work?” The answer shows the gap between the written process and the real one. It is almost always where the cause lies.

The spreadsheet everyone keeps alongside the official tool. The person who gets called because they are the only one who knows. The approval requested by message because the normal route is too slow. Every workaround is a piece of information.

04

Name the cause, then choose

Once the cause is named, the options become clear, and often simpler than expected. A delegation rule rather than a hire. A step removed rather than software. A fifteen-minute routine rather than one more committee.

The role of an outside view is not to bring a ready-made solution. It is to make the situation legible, so that leadership decides knowing the effects of each option.

Perspectives

Read next.

Next step

Does this speak to you? Let's talk.

Let's talk about your project