Your first week as Chairman

transcript

You now know every control. This final lesson puts them in order, as a first week you can actually follow. Treat it as a checklist, not a theory. By Friday you will have a colony that runs a real piece of your business on a schedule, inside a budget, with you in the loop only where it counts.

Day one is the brief and the budget. Have the conversation from lesson two: give the CEO one real objective, the constraints, and the definition of done. Before you say go, set the colony cap from lesson five to a number that would not hurt. Do not hire a large org. Let the CEO propose the smallest team that can hit the objective, and approve that.

Day two is governance. Set your approval gates from lesson four: outbound money, anything public, anything that changes a customer. Confirm the kill switch is one click away and practice the stop once so it is not a stranger when you need it. This is the day you make delegation safe, before you lean on it.

Day three is the org. Read the chart from lesson three. Confirm every outcome you care about has a single owner and no agent is overloaded. If the CEO is running on the right model tier and the workers on cheaper ones, your economics are already healthy. Trim anything idle.

Day four is the routine. Stand up the morning brief from lesson six. Let it run once and read it the next morning. This is the moment the product changes character: you stop starting work and start receiving it. Add a second routine only if the first one earns it.

Day five is the review. Open the audit trail from lesson seven and read the week by exception. Where did spend go. Which approvals deserved you and which were noise you should loosen. What did the CEO do well, and what should it remember for next time. End the week by telling the CEO, in one message, what to keep doing and what to change. That message is the Chairman's real job, distilled: direction, in plain language, backed by evidence.

A word on what week two should feel like, so you know whether week one worked. You should wake up to a brief you did not have to ask for, find a short queue of approvals that each genuinely need you, see a spend line that is comfortable, and read an audit trail only when something catches your eye. If that is your morning, the foundation is solid and you are ready to go deeper. If instead you are starting every piece of work by hand, approving trivia, or anxiously reading the whole trail, something in days one through five did not stick, and it is worth going back to that lesson rather than pushing on.

Do not rush to scale. The temptation after a good first week is to triple the org, stand up five routines, and raise every cap. The Chairmen who last do the opposite: they let one good colony run for a few weeks until its rhythm is boring, and only then add the next objective. A boring colony is a compliment. It means the controls hold, the routines deliver, and the company runs without drama. Boring is what you are building toward.

That is Chairman Fundamentals. You can run a company now. The next paths in the Academy go deeper: building the org for scale, designing workflows your agents author, governing spend across many projects, and running a regulated business that survives an audit. But the foundation is this: brief well, budget hard, gate the risky few, watch the trail, and let the company work. Welcome to the board.

copy-paste prompts

It is the end of my first week. Summarize the week by exception: where spend went against the cap, which approvals genuinely needed me versus which were noise I should loosen, what you did well, and what you will change. Then ask me for one message of direction for next week.