If you have ever heard yourself say it, you are in good company. We ran the change management program. Everyone completed the training. The policies are there in plain sight for anyone who wants to read them. Each of those statements is true. None of them answers the question that matters, which is whether anything is different in the corridor, on the floor, or in the meeting where nobody said the thing they were thinking. A program delivered is not a behaviour adopted. A training record is proof of attendance. A published policy tells you where the document lives, not whether a single person consults it under pressure.

Every certified organisation I work with can produce the folder. Policies signed. Management review minutes filed. Risk register current. Corrective actions closed inside the required timeframe. The auditor arrives, the artefacts are produced, the certificate is renewed, and the board receives a report saying the system is operating as intended.

Then something happens that the folder did not predict. And when you trace it back, you find somebody knew. Usually several somebodies. It never reached a document.

That is the distance worth talking about. Not the distance between good organisations and bad ones. The distance between what your evidence trail proves and what your people are doing.

Why the distance exists

ISO standards are written to be auditable. That is their strength, and it is also the source of the problem.

An auditor cannot observe judgement. An auditor cannot sit inside the conversation where a supervisor decides whether to raise something, or the moment a team agrees without discussion because the meeting is running late. So the standards ask for what can be inspected. Documented information. Records. Evidence of review. Demonstrated commitment.

Look closely at how commitment gets demonstrated. Top management shall demonstrate leadership and commitment. How do you evidence that? A signature. An agenda item. A minute recording that the policy was reviewed on the date it was due. Every one of those artefacts is genuine. Not one of them tells you how the room thought.

So organisations build for the artefact, because the artefact is what gets checked. Do that for a decade and you end up running two systems side by side. There is the system in the manual, and there is the system people use to get the work done. Most employees can describe both fluently. Only one of them ever meets an auditor.

The distance also widens without anyone deciding it should. Standards are reviewed on a cycle. Audits are periodic. Behaviour is daily, and conditions change constantly. A process written for a situation that no longer exists keeps running because it is documented, and documented things carry momentum. Nobody challenges it, because challenging it looks like nonconformance.

Then there is the board, sitting furthest from the behaviour and receiving the most summarised version of it. Directors carry personal obligations, and they discharge them using assurance built from artefacts. Green on the dashboard. No view of the thinking underneath it.

Where the five principles sit

The Weird Wisdom® principles are not an alternative to your management system. They are the behavioural layer your management system assumes exists.

Being Comfortable with the Unknowns. Clauses on risks and opportunities depend on people naming what they do not yet know. The Unknown is the thing out there that has not been identified. Uncertainty is what happens inside a person when they meet it. Documentation rewards certainty, so Unknowns get filtered out of the register, because naming one looks like an admission that control is incomplete. Get an organisation comfortable with Unknowns and the uncertainty dissolves. What is left is a risk process describing reality rather than confidence.

Failure as Growth. Your nonconformance system exists to generate learning. In many organisations it generates closure. The finding gets shut, the root cause is recorded as human error, and nothing changes. If reporting a failure costs the person who reports it, your incident data is fiction, and your board is reading a novel.

Harmony in Contradictions. Every operation runs on competing demands. Throughput against thoroughness. Cost against quality. Responsiveness against due process. The manual behaves as though these tensions do not exist. Staff resolve them privately, dozens of times a day, and the resolution never appears in a record. Name the contradiction out loud and you get to design for it instead of pretending it away.

Question the Norms. Internal audit asks whether the process was followed. It rarely asks whether the process is still right. Continual improvement requires questioning, and audit culture often punishes it. That is a contradiction sitting inside your own system.

Explore the Unconventional. Rules, standards and ethics are not obstacles. They are the tools. Inside them there is enormous room to meet a requirement differently and better. Sequential approvals become parallel ones. Conformity is unchanged. The outcome improves.

The risk of leaving it alone

The first risk is the obvious one. Certification without capability. You pass the audit and fail the event, because the event was never in the manual.

The second is regulatory. A complete document set is no longer a defence when behaviour tells a different story.

The third is financial and largely invisible. Audit preparation cycles. Duplicated processes. Staff maintaining the real workflow and the documented one. Repeat findings that keep returning because the corrective action treated the paperwork rather than the pattern.

The fourth is people. When the report matters more than the reality, your most capable staff learn that speaking up produces friction and no change. They stop. Then they leave. The ones who remain are the ones comfortable with the arrangement, which is exactly the group least likely to warn you.

The fifth is time. Nearly every serious failure was visible to someone well before it became visible to everyone. The delay between those two moments is a behavioural problem, not a documentation one.

What fixing it gives you

Your evidence trail starts describing what happens rather than what was intended. That single change makes audits shorter, findings fewer and assurance meaningful.

Reporting rises before it falls. Expect that. When people believe raising something produces a response rather than a consequence, near miss and incident numbers climb. It looks worse on the graph and it is the healthiest signal you will get all year. Severity follows it down.

Corrective actions hold, because they address the thinking that produced the behaviour rather than the record that captured it.

Your organisation absorbs regulatory change faster. When people understand the intent behind a requirement rather than only the steps, a new version of a standard is an adjustment, not a project.

And the board finally receives assurance worth having. Not a document count. Evidence that the people responsible for the system understand what it is for.

I saw the scale of this in a Perth organisation some years ago. We were engaged on two priority areas, and bullying was not one of them. Nine months in, the HR team checked something they had noticed. Bullying reports were down 71.6 per cent. Nobody had run a bullying program. The behaviour changed because the thinking changed, and the measurable outcome arrived somewhere nobody had targeted.

Your management system is not wrong. It is carrying a load it was never designed to carry on its own. It can describe what should happen. It cannot make people think well when the instructions run out.

That part is buildable. It just is not built by writing another procedure.