An irritant rarely arrives well phrased. It arrives in one sentence, often blunt, dropped between two doors. This grid starts from that sentence exactly as it was said and takes it, in half an hour, through to a costed figure, a decision properly framed and a first dated move.
Fill it in on your own, or with one or more colleagues, before the meeting, and always before opening an artificial intelligence tool. If three questions stay blank, the matter is not ready to be decided. That is already a result.
Nobody likes being framed on a subject that irritates them, starting with oneself. You first want to put it as you live it. That is why the grid opens on a raw sentence and not on a tick box, and why the questions are taken one at a time, in order. Under pressure, you hold four things in mind, rarely more.
Give the first seven minutes to question zero and the two that follow, without looking for structure. The framing holds once the problem is stated in your own words. Never before.
The examples follow a single case: a fourteen-employee company whose 2004 press brake breaks down too often. Replace them with your own. Print the grid, write by hand, keep it on the table during the discussion.
Write it down without correcting it, with the words and the mood of whoever said it, including if that is you. Rephrase it by naming what weighs, then wait for the “that is exactly it”. Putting a word on a tension lowers its charge, and the discussion can begin.
Describe the problem without slipping a solution into it. The column of what does not happen is the one most often forgotten. Yet it is the one that points to the cause.
Hours lost, euros, late deliveries, regulatory risk, wear on the teams. A costed loss mobilises more than a promised gain, and it sets the real urgency of the subject.
Either the answer is known and it only has to be applied. Or it exists and needs an expert or figures to be found. Or nobody can predict it, and only a trial of a few weeks will teach it. That last case is not settled in a meeting.
A subject that ends neither in yes or no, nor in a dated trial with its stopping criterion, will be back on the table next quarter.
Name people and a day on the calendar. In an SME, failure rarely comes from the decision-maker. It comes from the one nobody thought to consult: an operator, a banker, an inspector or a customer.
A single option serves to justify a preference already formed. Set the deciding criterion before looking at the options, otherwise it will bend to them. An irreversible option deserves twice the examination of any other.
Separate the measured, the estimated and the missing. Write missing data rather than an invented order of magnitude, then note a name and a date beside it.
Data that does not leave the company, commitments nobody can make alone, regulatory obligations, decisions that belong to a third party. To be written down before submitting anything to an AI tool.
Taking failure for granted releases the objections that enthusiasm holds back. The most awkward answer becomes the objection to examine before deciding.
An indicator, a target value, a measurement date set to the rhythm of the subject: three months for a breakdown, a year for a compliance project. Then a sentence in “if… then”, with a name and a date. An intention written in that form turns into action far more often.
The same questions, applied to three entirely unrelated cases. Here is what question zero, the cost of the status quo, the expected decision and the proof come out as.
It all fits on a single page. At the top, your rephrased sentence, the one everyone agreed on. Below it, the monthly cost of the status quo, often the first figure ever put on this subject. Then come the nature of the problem, the decision or the trial chosen, the missing figures with their owner and their date, and lastly the first move.
The day you read it again, the sentence dropped in passing has become a case you can take to your banker, your team or your inspector.
None was invented for the occasion. The analysis of what happens and what does not comes from Charles Kepner and Benjamin Tregoe, who formalised it in the 1960s for industrial diagnosis. Stating the problem without a solution opens the Six Sigma DMAIC approach. Sorting by the nature of the subject follows Dave Snowden's Cynefin framework, and the parties to consult follow the logic of ISO 9001 as well as ISO 31000 for risk.
The pre-mortem is due to the psychologist Gary Klein, and the “if… then” formulation to the work of Peter Gollwitzer. Reformulating until agreement comes from motivational interviewing, practised in healthcare for forty years. The findings retained on attention and emotions are those research has replicated. The spectacular promises of neuromanagement have been left aside.
A fourteen-employee company with a cutting and bending shop has to decide the fate of a 2004 press brake that breaks down too often. The case is fictional, built from situations common in engineering and metalwork.
Thirty-five minutes, ten of them spent on question zero alone, before any structured question. Four costed options, including the status quo, two of them irreversible. Three items of data identified as missing.
The answers copied out as they stood, plus a short instruction. Question 8 filtered what had to stay inside: no prices, no customer names, no employee names.
A weighted comparison table, the list of what is missing with who fetches it and by when, a recommendation, the most likely failure scenario, and the condition that would invalidate the recommendation.
The note does not decide. It establishes that the decision cannot be made as things stand, names the three missing figures and sets the technician's visit for 1 October. That is the expected outcome of honest scoping.
Produce no figure that was not supplied, and write missing data instead. Recommend no option without naming its cost. Flag a badly framed decision before dealing with it.
Without them, the tool fills the gaps with plausible orders of magnitude, and a case goes into a meeting carrying figures nobody has measured. A usable document rests on the scoping written by hand before opening the tool, far more than on the tool's power.
This grid is what I have people do at the start of every assignment. When the subject outgrows one sheet, the scoping audit takes over: half a day on site to set the priorities, the action plan and its schedule.