Your first conversation with the CEO

transcript

Your first conversation sets the tone for everything that follows. The mistake new Chairmen make is treating the CEO like a search box: they type a vague request, get a generic answer, and conclude the agent is not very smart. The CEO is exactly as good as the brief you give it.

A good brief has three parts: the objective, the constraints, and the definition of done. The objective is what you want to be true that is not true today. The constraints are the budget, the deadline, and anything that is off limits. The definition of done is how you will know it worked. If you give the CEO those three things, it will come back with a plan and a proposed org, not a paragraph of hedging.

Watch what happens when you brief it well. The CEO does not just answer. It decomposes the objective into work, proposes which roles it needs to hire into the org, estimates the spend, and tells you what it will do without asking versus what it will bring back for approval. That last part is the contract between you. Read it before you say go.

You will notice the CEO asks you questions back. This is a good sign, not a stall. A CEO that never asks anything is guessing. When it asks whether you would rather optimize for speed or for cost, answer in one line and move on. You are calibrating its judgment so it needs to ask less over time.

Keep your messages short. You are not writing a specification document; you are running a company by conversation. The CEO holds the context. If you said last week that the brand voice is calm and clinical, you do not need to repeat it. The colony remembers, which is the entire point of the Memory engine you will meet later in the Academy.

There is a rhythm to a good briefing relationship that takes a week or two to settle into. Early on you will over-explain, because you do not yet trust the CEO to fill the gaps. That is fine; it is how you teach it your standards. As the colony's memory fills with your decisions and corrections, your briefs get shorter, because the context you used to spell out is now assumed. A brief that would have taken a paragraph in week one takes a sentence in week four. That compression is the system working, not you getting lazy.

Beware the brief that is really a list of tasks in disguise. If you find yourself writing step one, step two, step three, you are managing, not chairing, and you have given up the leverage the product exists to provide. State the outcome and the constraints, and let the CEO decompose it. If the decomposition is wrong, correct the decomposition, not the individual steps. You are calibrating a decision-maker, not operating a machine.

End the conversation with an explicit go or an explicit hold. Ambiguity is the one thing the CEO handles badly, because it is built to respect your authority. If you say maybe, it waits. If you say go, it works. Say go only when the plan, the budget, and the definition of done all look right to you.

copy-paste prompts

Objective: I want a weekly customer-update email going out every Friday that summarizes what we shipped and what is next. Constraints: keep tooling spend under $40 a month, draft must reach me by Thursday noon for approval. Done means: a sent email every Friday with an open rate I can see. Propose the plan, the roles you need, and the monthly cost. Tell me what you will do without asking and what you will bring to me.

When you have to choose between moving fast and keeping cost down on this objective, default to keeping cost down unless the deadline is at risk. Remember that for future decisions on this project.