The scenario is set on the ECOPETROL Cartagena Refinery Expansion in July 2011. An amine regenerator re-tray. A Turnaround Manager who wants the crown pipework refitted two days early. A confined space team lead who has already confirmed it is technically possible. And an HSE Director who has thirty seconds to decide what to do with the request. The mistake most senior practitioners make in this moment is asking for a revised risk assessment. Which produces a technically defensible document. Which gets initialled. Which is fully compliant. And which nearly kills a man on day twelve. The technique the module teaches is called the Consequence Narrative. It is a Boardroom Code technique, delivered as three sentences at the base of the column, with the gaze changing between each part. When it is deployed correctly, most Turnaround Managers refuse their own request within thirty seconds of hearing it. Watch the video. Download the workbook. Complete the four sections against a scenario currently in play on your own site. Then come back here. Here is the question I want you to answer in the thread below. What is the wrong question you are currently being asked on your site? The compliance question that has been placed in front of you where a leadership question should have been. Name it in one sentence. Then draft the leadership question that should have been asked. Post both. I will respond to every reply in the thread this week. If you do not know how to identify the wrong question, that is a valuable answer too. Post that and I will help you find it. The technique cannot be taught in a video alone. It has to be practised against real scenarios in real time. This thread is where the practice happens. Paul.

A worked example from my own practice Before any of you post, I want to do the practice myself. So you can see what I am asking of you, and so you have something to follow rather than a blank page to fill. This is my own answer to the brief above. It is a drive home I keep coming back to. The road was the A66 heading east across Cumbria. It would have been ten or twelve years ago now. The time was around five in the afternoon on a Friday in November. The light was beginning to go. I had been on site all week. The job was a planned shutdown on a heavy industrial plant in the north of England. The week had gone well by every measurable standard. The audits had been clean. The work had been completed ahead of schedule. There had been no incidents. The team had been pleased. And on the drive home, alone in the car, the voice arrived. It said something like this, and I am paraphrasing because the exact words have softened in my memory, but the substance of it is unmistakable. It said, the workforce performed safety for you this week. They did not own it. The moment you left the site this afternoon, the version of the culture you have been working on for six months walked out with you. And you do not have a single piece of evidence to the contrary. That was the voice. Not a flash of insight. Not a dramatic moment. A quiet, calm, devastating piece of self-knowledge that arrived because, for an hour and a half, I was alone with my thoughts and my professional defences had been left at the site gate. I did not do anything with it. I pushed it down. I told myself the voice was Friday tiredness. I had a glass of wine that evening and the voice was gone by the next morning. On Monday I went back onto site and ran the same kind of week I had been running for the previous six months. Three more shutdowns came and went, on different sites, with the same dynamic. The dashboard stayed green. The Friday voice came back periodically, and I pushed it down periodically. Here is what I would do now.

A worked example from my own practice Before any of you post, I want to do the practice myself. So you can see what I am asking of you, and so you have something to follow rather than a blank page to fill. This is my own answer to the brief above. It is the moment I keep coming back to. The site was in the north of England. The job was a confined space entry, midway through a planned shutdown. The worker was a man named Jim — I will not use his full name — who had been on tools for the best part of forty years. Quiet. Steady. Not a complainer. On the Wednesday morning of the shutdown, Jim approached me by the access point. He said — and I am paraphrasing only because the exact words have softened in my memory — he said something like "Paul, the brief on this one has changed three times this week. I am not sure anyone is actually leading this entry." I defended. I told him the brief had changed because the conditions on the line had changed, that the iteration was a sign of the system working, that the supervisor team were in close coordination. All of which was technically accurate. None of which was what Jim had asked. What he was telling me was that the worker who was about to make the entry could not feel a coherent leadership presence behind the plan. He was telling me that the man going into the confined space did not know whose call this was. He was, in his quiet way, telling me that something had drifted in the leadership of the job — and he was hoping I would do something about it before the entry happened. I did not. Not in the conversation. Not in the forty-eight hours afterwards. I clarified the brief in writing, I sent an updated permit, and I moved on to the next priority on my list. The entry happened safely. Nothing went wrong. Which is the worst possible outcome of a missed conversation, because it teaches the leader that the defence was vindicated by the result. Here is what I would do now. The silence. When Jim spoke, I would stop walking. I would put down whatever I was carrying. I would turn fully toward him. I would say nothing for three or four seconds — not a calculated pause, just enough that he knew I had heard the seriousness of what he had taken the trouble to come and tell me. He had walked thirty metres out of his way to find me before the entry. The silence acknowledges the deliberateness of that walk.