Every beginner walks into his first advisory session carrying the same private fear: what if they ask me something I don't know?
I remember it well. You prepare for three days. You read everything. You rehearse the answers to questions nobody ends up asking. And then you sit down across from a director who has been told by his ministry to "do something with AI," and within ten minutes you realise that none of what you memorised is what the room needs.
The fear is understandable, but it rests on a false premise — that the consultant is a container, and the client has come to draw from it. That the value you provide is proportional to the volume of what you know. I have sat in enough of these rooms now to be confident this is wrong, and wrong in a way that actively damages young consultants.
The myth of the full container
If knowledge alone made a consultant, the best consultants would be professors. They are not. Some of the most learned people I know are unable to be useful in a room for ninety minutes, and some of the most useful people I know have a narrower base of knowledge than they let on.
What the client actually brings to the session is not a question. It is a situation — tangled, political, half-articulated, usually inherited from someone else. He describes it to you in the language available to him, which is often borrowed language: he says he wants a chatbot, he says he wants "AI," he says he wants what the neighbouring ministry announced last month. The words he uses are almost never the problem he has.
The beginner answers the words. The experienced consultant answers the situation.
That is the whole difference, and everything below is just the mechanics of it.
What happens in the room
An advisory session is not a lecture and it is not an interrogation. It is a negotiation over what the problem actually is — conducted politely, under time pressure, in front of people whose interests do not all align.
There is usually someone in the room who wants the project to happen and someone who quietly does not. There is someone protecting a budget and someone protecting a department. There is often a person who says almost nothing and whose approval determines everything. The beginner does not see any of this. He sees an audience.
I have learned to spend the first third of a session almost entirely on listening and reframing. Not because listening is a virtue — though it is — but because it is the only way to locate the real question. And the real question is rarely technical. "Can AI read our archived documents?" is technical. "How do I show the minister progress before the fiscal year closes without committing to a system my team cannot maintain?" is the real one. Both are asked with the same sentence.
Nine differences
I have watched enough beginners — and been one — to name the pattern:
1. The beginner performs knowledge. The experienced consultant arranges it. The beginner mentions three model architectures to establish that he belongs in the room. The experienced consultant knows the room was already granted; his job is now to reduce, not to add.
2. The beginner fears silence. The experienced consultant uses it. Silence after a question is not failure. It is the client thinking, which is the point of the session.
3. The beginner answers the question asked. The experienced consultant finds the question underneath it. And crucially — he then says the underlying question out loud, and asks if he has understood correctly. Reframing without permission is arrogance; reframing with permission is the service itself.
4. The beginner sells a solution. The experienced consultant sells clarity. A client who leaves with a clear map of his own situation will come back. A client who leaves with a proposal he does not fully understand will not.
5. The beginner says yes. The experienced consultant scopes. Nothing destroys a young consultant faster than agreeing, in the warmth of a good meeting, to something he cannot deliver. The strongest sentence in this work is: that is possible, but not in that timeframe, and here is why.
6. The beginner hides the limits of his knowledge. The experienced consultant marks them clearly. "I don't know, and I will find out by Thursday" is not a confession of weakness. Said calmly, it is the single most credibility-building sentence available to you, because it tells the client that everything else you said, you actually knew.
7. The beginner treats every session as a performance. The experienced consultant treats it as one node in a relationship. The first session is not where you win. It is where you earn the second one.
8. The beginner leaves the room when the session ends. The experienced consultant leaves a document. More on this below.
9. The beginner is attached to being right. The experienced consultant is attached to the client moving. Sometimes the technically superior recommendation is the wrong recommendation, because the organisation cannot carry it. A consultant who cannot make this distinction is an engineer with a nicer chair.
So how much must you actually know?
Not everything. But the shape matters more than the quantity. In my experience it is three layers:
Deep in one thing. You need one domain where you are genuinely at the frontier and cannot be embarrassed. This is your floor. Everything else you say is trusted, or not, based on how solid this floor sounds when someone taps on it.
Map-level across the neighbours. You do not need to have built every system. You need to know what exists, what it costs, what it typically fails at, and who has done it before. Enough to say "that has been tried, here is how it usually goes" — which is worth more to a client than a technical deep-dive he did not ask for.
Fluent in the client's world. This is the layer beginners skip entirely, and it is the expensive one. How his budget cycle works. What his procurement rules forbid. Who signs. What his data actually looks like — not what the policy document says it looks like. Where his last three initiatives died and why. This knowledge is not transferable and cannot be read; it accumulates only through sessions, which is precisely why the tenth year is not the first year repeated ten times.
The session is not where the work is
Here is what took me longest to learn: the advisory session is the visible part, but the value is created on either side of it.
Before — one page. What I think their situation is, what I intend to ask, what I will not offer even if invited to. Going in without deciding your boundaries in advance means negotiating them while tired and being liked.
After — a short written summary, sent within forty-eight hours. What we discussed, what was decided, what remains open, what happens next and who owns it. Two pages, never twenty. Most consultants do not do this, which is exactly why doing it is so disproportionately effective. It converts a pleasant conversation into a documented commitment, and it makes you the person holding the thread.
The follow-up is where consultants are actually made. Everything else is conversation.
A closing thought
The question "do I know enough?" never resolves. You will not wake up one morning sufficiently knowledgeable. What changes is that the question stops being load-bearing.
Knowledge, in this work, is not a warehouse you fill before you are permitted to speak. It is a posture — a way of standing inside someone else's problem with enough calm to see its shape, enough honesty to name what you cannot do, and enough discipline to write down what was agreed.
The beginner arrives hoping to be found sufficient. The consultant arrives hoping the client leaves lighter than he came.
That is the whole craft.
Yousuf
15/08/2026
Amirat