The room is booked. Somebody has confirmed the numbers for lunch. Your operations lead is coming, your finance director is coming, and a person from outside your company will spend the day asking questions about how your work actually gets done.
What is sitting with you now is the quiet worry that you will be the one who does not follow it. That there will be a moment where everyone nods at something and you will decide, in that second, not to be the person who asks. You have sat in that meeting before, in a different subject, and you remember exactly how it felt to let it pass.
So it is worth saying plainly what the day is for, because the worry is aimed at the wrong thing. Nobody will ask you to understand anything you do not already understand. What the day needs from you is knowledge you have and the visitor cannot get.
The day needs the one thing only you hold
A design can settle almost everything on paper before anybody meets. How many times a system may go around before it must answer. Who it may write to, and how often. What waits for a person. What gets written down. Those are decisions with values, and the values are published: ArkOne’s reference design for an executive agent, the Cabinet, states all of them on the Register, a standing page of every setting in the design. None of them is about your company, which is why none of them needs your day.
What a design cannot settle is where the judgement sits in your work, and that has no general answer: it is a fact about your business, held by your people, and mostly never written down anywhere. Some recurring work is genuinely decided. Somebody weighs one thing against another, brings in something they know that is not written in any file, and lands on an answer another competent person might not have reached. Other recurring work only looks decided, because a person has always done it and nobody has ever separated the part they judge from the part they execute. Both feel the same to the person doing them, and both get described in the same words when you ask.
Telling those two apart is the whole business of the day. It cannot be done from outside, because from outside they are identical. It cannot be done from a document, because the document was written after the fact by somebody summarising. It can be done in a room with the people who do the work, in about the time a good question takes to answer.
Two things will come up often enough on the day to be worth carrying in, and both are about where judgement sits rather than about how any of it is built. The first is the authority setting: every specialist in the reference design arrives set to propose and wait, meaning the work is drafted in full and stops until a person answers, until somebody writes otherwise. The second is what gets written down: a ledger where nothing is edited and a correction is a new entry standing beside the old one. If a sentence on the day loses you, those two are almost always what it is circling. The pages to read first put the rest of the vocabulary in order, if your evening is long.
What to bring, and one job taken apart
What is useful to bring is a small number of things that live in your people’s heads rather than in a folder, and here is what each one is for.
| What to bring | Who actually holds it | Why the day cannot proceed without it |
|---|---|---|
| Three jobs that repeat every week | Whoever does them, not whoever owns them | A job nobody in the room performs cannot be taken apart, only described |
| One recent example of each going wrong | The person who fixed it | The failure shows where the judgement was, faster than the description does |
| The rule nobody wrote down | Your longest-serving member of staff | An unwritten rule is what a design gets wrong when nobody knew to ask |
| Who is allowed to say yes, and up to what | You, and only you | Authority is a decision about your company; the setting merely records it |
Exhibit 2. Illustrative. What only your own people can bring to the day, and one recurring job taken apart.
The second row does more work than it looks. When you ask somebody to describe a process, they describe the version in their head, which is the version where it works. The failures are where the judgement lives, because a failure is almost always a moment where somebody weighed something and weighed it wrongly. Bring the awkward ones rather than the tidy ones.
The third row is the one people forget to bring because they do not know they hold it. Every company has a rule that has never been written anywhere and that one person applies without thinking: never send this class of customer anything on a Thursday, always ring rather than write when this word appears, never quote this client against the standard schedule. The person who knows it does not experience it as a rule. It is simply how the job is done.
The fourth row cannot be delegated to the day. Whether something may be sent without a person looking at it is a question about your appetite for risk, and the honest reference position is that nothing acts alone until somebody decides it may. Your visitor can name the setting and say where it lives. What it should be, in your company, is yours.
Now the exhibit that makes this concrete. Suppose a freight forwarding and customs brokerage of about two hundred and forty people, invented for this exercise, moving shipments for manufacturers across three ports. One recurring job: a customer asks why their consignment is being held, and somebody has to answer them the same day. It happens perhaps thirty times a week. Here it is taken apart.
| The step | What it involves | Machine or person |
|---|---|---|
| Establish what is held, and where | Reading the entry against the carrier’s status and the port’s hold notice | Machine; the three sources say what they say |
| Assemble the paperwork history | Which documents were filed when, and which were queried | Machine; it is a sequence of dated records |
| Draft the explanation | Setting out the cause in the customer’s own terms | Machine, proposed for a person to read |
| Decide what to tell this customer | Whether to name the party at fault, and whether to offer to absorb the charge | The person, always |
Exhibit 3.
The first three rows are the ones a machine holds well, and they are also the ones that consume the afternoon. Somebody senior spends twenty minutes assembling a picture from three systems and a folder before they can begin to think about the reply. That assembly is not judgement. It is retrieval, and it is slow because the sources do not talk to each other.
The last row is judgement, and it is not a small one. Naming the party at fault is sometimes the right thing and sometimes the end of a commercial relationship you have spent four years building. Whether to absorb a storage charge turns on what this customer has cost you this year, what they are worth next year, and something your operations director knows about their new procurement manager. No design settles that, and no design should be asked to.
What makes the fourth row worth noticing is that it takes about ninety seconds once the first three rows are in front of you. The judgement was never the expensive part. The expensive part was the assembly that had to happen before anybody could exercise it, and the reason the job feels like a decision from end to end is that one person has always done both halves.
That is the pattern the day looks for in your work, and the invented brokerage is here only to show you the shape of it. The account of why a pilot quietly dies is what happens when the fourth row gets handed over by accident, and the paper on the authority setting is where the fourth row is written down as a value somebody owns.
What to ask, so the day is yours
Four things to say out loud, and none of them requires you to know anything technical. They are the questions that keep a day about your company rather than about a design.
Which step here is the judgement, and which steps only feel like it? Ask it of every process on the board, and ask it of the person who does the job rather than the person who manages them. You will be surprised how often the answer changes when you put the question to the second person. Where the two disagree, you have found something worth an hour.
What breaks if we get this one wrong? A misfiled entry and a wrongly-worded message to a regulator are both errors, and one of them ends a licence. Sorting the recurring work by what a mistake costs is a chief executive’s sort, and it reorders a list faster than any other question in the room. It also tells your visitor which rows need a person in them whatever the arithmetic says.
Who in my company would own this once it runs? Ask it on the day rather than in month four. The answer is a name and a person’s existing workload, and if there is no name, you have learned the most useful thing available. The hardest part of one of these arrangements to add afterwards is a person to look after it.
What did we not look at today, and why? Ask this in the last hour. A day covers what a day covers, and the list of what was left out is genuinely more useful than an extra item covered thinly. It is also the honest test of whether the room was being thorough or being agreeable.
Two things the day cannot do, and it is better to hear them now than to feel let down at four in the afternoon. It cannot tell you whether to buy anything. That turns on a budget, a contract and a timetable that nobody settles in a room, and a day that ended in a purchase decision would have been selling rather than examining. And it cannot value work it has not seen: any figure produced on the day is arithmetic on numbers your own people supplied, which makes it a model of your business rather than a finding about it. Treat both limits as the point rather than the disappointment. What a day can produce is a defensible view of where to look first, and that is the decision that has been sitting unmade.
One question, to one person, this week
Pick the person in your company who does one recurring job that everybody would notice if they were away for a fortnight. Go to them, not to the person who manages them, and ask one question: which step in that job are you actually deciding something, and which steps are you just getting to the point where you can decide.
Ask it once and then stop talking. What you are listening for is whether the answer arrives as one step or as several. One step, named quickly, means the job has a shape somebody can work with. Several, or a pause, or a version that changes halfway through, means the judgement and the assembly have never been separated in anybody’s mind, including theirs, and that is the more useful finding of the two because it is the one the day is built to resolve.
Bring the answer, in their words rather than yours, and bring them if you can. A day spent taking apart a job the room can only describe is a day spent on somebody’s summary of the work, and a summary has the judgement already smoothed out of it.
component: null
Asked plainly
Do I need to understand AI to get value from a clinic day?
No, and the day works better if you spend none of it trying. What the room cannot supply is knowledge of your own business: which recurring pieces of work turn on somebody's judgement, and which only look that way because one experienced person has always done them. That distinction decides what can be handed to a machine and what must not be, and nobody outside your company can draw it for you.
What should a CEO bring to an AI workshop or consulting day?
Bring the work rather than the technology. A short list of jobs that repeat every week, the names of the people who actually do them, one example of each going wrong, and the rule nobody has ever written down that a long-serving member of staff applies without thinking. Documents help less than people do, because the undocumented judgement is the part the day is looking for.
What can a single day of AI consulting not do?
It cannot tell you whether to buy anything, because that turns on a budget and a contract nobody settles in a room. It cannot value work it has not seen, so a saving quoted on the day is arithmetic on your own figures rather than a finding. And it cannot examine a process nobody in the room performs. A day is a day, and its output is a decision about where to look first.