11. Five forms of message

In a business factory, much of what goes wrong does not go wrong for lack of capability, but because of ambiguous messages: a request no one knows was accepted, a question no one answered, a «done» with nothing to prove it. This chapter proposes a way of writing each message that makes clear who owes what to whom.

The five forms

Every message, from a role to a person or between roles, takes one of five forms:

Form What for Who owes something afterwards
Tell inform, explain, summarize, recommend no one
Alert something that matters now no one, but it has to be seen right away
Ask request a piece of data, an opinion, a review the receiver: an answer
Need request an approval, a decision, something only the other can do the receiver: an answer now
Promise commit to delivering something the sender: the delivery

Five forms of message, and who owes something after each one.

The idea comes from a text by Max Grev published in November 2026, and it was adopted with few adaptations. Its value lies in the last column: each message establishes a debt, or none. A system where debts are explicit can be audited; one where they are not depends on someone remembering.

How what is open gets closed

An open request (an unanswered question, an unkept promise) can be closed in only five ways: it is delivered (with evidence), it can't be done (with the reason), it is renegotiated (with a new deadline), it is redirected (saying to whom) or it is canceled. Nothing else closes it. A request that simply stops being mentioned is not closed; it is lost.

Some rules that come with it

  • Every promise has a deadline: a time or an event («when the supplier's reply arrives»).
  • Every «done» brings its evidence: a link, an identifier, a screenshot.
  • Every question brings a recommended option and what happens with each answer.
  • Every Need says what stays blocked until it is answered.
  • An alert is earned: it is used only when something matters now, because an alert for everything stops being an alert.
  • A redirect is stated, never silent: «this belongs to another area; I passed it to them».
  • Before starting, whoever receives a request says what they understood and when they will consider it done, so that a misreading is corrected before it turns into rework.
  • A message may combine parts (a piece of information followed by a request), but each part keeps its form, the context goes first and the request last, and there is only one open request per message.

None of these rules is new on its own: several are good practice in any well-run team. What is new is applying them uniformly to agents and people, so that an agent that writes «promised for tomorrow at 10» is as committed as a person who says the same.

When to speak to a person

The five forms put in order what is said; what remains is to put in order when. The person's attention is the scarcest thing, and the rule that protects it is the following:

  • in the moment, only what needs them: a request for a decision, an alert, a promise that is holding them up, a «done» with its evidence, the answer to something they asked;
  • everything else waits for a summary, and the summary is sent only if it has something in it;
  • after hours away, the person first gets two numbers (how many things were finished and how many need them), and then only the ones that need them;
  • before starting, what was understood is stated (which avoids carefully researching the wrong question);
  • before asserting a cause, it is verified; if it could not be verified, it is said to be a hypothesis.

The experience behind this rule is common: a very active agent system can send dozens of progress messages in a few hours, and the person ends up reading a lot to decide little. One message per thing that needs the person, and the rest together, is preferable.

The measure

The scheme has a measure that justifies or refutes it: a person's total attention per task finished right, counting the request, the approvals, the reviews and whatever had to be redone.

One clarification prevents a misreading. Some reading is the work itself (a text that will go out under someone's signature, a strategy, a subtle design decision), and that is not cut. What is cut is the reading that serves only to verify, and that is what the evidence in each delivery and well-built questions are for.

Example. Purchasing writes to General Management: «Tell: the frame supplier raised its prices by 8 %. Need: approval to accept the new price list. The recommendation is to accept it: the second supplier is 12 % higher. If it is not accepted, the December order stays blocked». In one reading, General Management knows what happened, what is up to it and what not answering costs.

To recap, five forms of message, five ways of closing what is open and a handful of rules make explicit who owes what to whom, and people's attention is the measure of whether it works. The next chapter looks at how a request enters a business factory.