Most communicators can name the topic of their communication. Fewer can name the outcome. The gap between the two is where a great deal of communication effort is wasted.
A message about a project update has project update as its topic. Its intent is something else, perhaps to secure agreement on a next step, to surface a risk that has not been acknowledged, to reset expectations that have drifted, or to close a loop the recipient has been carrying. The topic is what the message is about. The intent is what the message is for.
Intent covers three things.
It covers the specific outcome the communication is designed to produce. Not a general aspiration. A specific state the exchange is supposed to leave the receiver in.
It covers the alignment between that outcome and the communication's actual design. A message intended to secure agreement but designed as a status report will not secure agreement. Design has to follow intent, or the intent is decorative.
It covers the honesty of the intent itself. Some communications have unstated intents that the sender is unwilling to name. A message ostensibly asking for feedback may actually be seeking validation. A message ostensibly explaining a decision may actually be foreclosing further discussion. Intent as a layer asks the practitioner to name what they are actually trying to do, not what they would prefer to describe themselves as doing.
Intent is not manipulation. Naming what you want a communication to produce is not the same as engineering the receiver into producing it. The practice of Intent is about clarity for the sender, the receiver is served by that clarity, not exploited by it.
The question sounds obvious. In practice, most communicators cannot answer it precisely.
Ask any practitioner what a specific message they are about to send is for, and you will usually receive a topic answer, "it's about the launch schedule," rather than an intent answer, "it's to move the launch date from next Friday to the following Wednesday, and to secure buy-in from the two people who will be inconvenienced by the shift." The topic answer names the content. The intent answer names the outcome the sender wants the message to produce.
Both answers can be given about the same message. Only the intent answer will produce a message that works.
When a communicator cannot state the intent of a message they are about to send, the message is not yet ready to send.
Intent's question is diagnostic in a specific way. It reveals whether the practitioner has done the upstream work of knowing what they want the exchange to produce. A practitioner who has done that work can name the intent in a single sentence. A practitioner who has not done that work will offer topic descriptions, aspirational descriptions, or defensive descriptions, none of which are intents.
The question is not asking the practitioner to justify their communication. It is asking them to know it clearly enough to design it well.
The pattern family most active in Intent is Frame, establishing the container inside which the exchange will happen. Framing in Intent is the practice of stating what kind of communication this is and what it is for, either explicitly to the receiver or implicitly through the communication's shape.
A well-framed communication tells the receiver what to do with it. It signals whether the exchange is closing a decision or opening one, sharing information for record or requesting a response, escalating a concern or de-escalating one. The framing does not need to be explicit, sometimes the shape of the communication does the work, but the framing has to happen somewhere, or the receiver will construct their own frame, which may or may not match the sender's intent.
The Cut pattern family appears in Intent as the practice of removing content that does not serve the intent. Messages that begin with clear intent often accumulate additional purposes as they are drafted, a note becomes a note-plus-explanation, becomes a note-plus-explanation-plus-request. Cut is where a practitioner returns to the original intent and removes what does not serve it.
The Return pattern family appears in Intent as the practice of returning, mid-communication, to the intent when the exchange begins to drift. Long emails, extended meetings, and multi-message threads all tend to lose their original intent as they unfold. Return is the move that pulls the exchange back to the outcome it was designed to produce.
The Daily Rep for Intent is on the curriculum roadmap and will be released in a subsequent curriculum expansion. In the interim, practitioners investing in Intent can install the ambient practice of stating the intent of every communication before drafting it, a single sentence, written or spoken, that names what the communication is for before any content is produced. Practitioners running this ambient practice for ninety days typically report the specific fatigue of realizing how many communications they had been sending without ever having named their intent.
A communicator whose amplitude in Intent is developed produces communications that arrive with a clear operating purpose. Their messages tell the receiver what they are for within the first sentence or two. Their meetings have named outcomes rather than named topics. Their long emails still have a locatable intent that a reader can identify after reading. Their communications end in a state the sender was designing for, a decision, a next action, a shared understanding, a closed loop.
A communicator whose amplitude in Intent is emerging produces communications that are topical rather than purposive. Their messages describe subject matter without landing on outcomes. Their meetings cover topics but do not close them. Their long emails accumulate multiple partial intents that compete with each other. Their communications end with the receiver informed but uncertain what to do next.
Consider a specific case.
A product manager we will call Kian sends a message to his director on a Wednesday afternoon. The message is 340 words long. It describes progress on a project, notes some risks, mentions a stakeholder who has been difficult, and closes with the sentence "let me know your thoughts." Kian considers the message a careful update. His director reads it, is not sure what response Kian is seeking, and, because it is Wednesday afternoon and there are seven other messages requiring more obvious action, moves it to a mental "come back to this" pile. It does not receive a response until the following Monday, by which time the project has moved past the moment the message was designed for.
Kian's Intent was emerging. The message had at least three partial intents, informing on progress, flagging risks, requesting guidance on the difficult stakeholder, and none of them was primary. The director, unable to identify which intent required action, defaulted to no action. The topic was clear; the outcome the message was designed to produce was not.
If Kian had been operating with a developed Intent, the same message would have arrived differently. It would have opened with a sentence like "I need a decision from you today on how to handle Priya's continued objections to the rollout schedule, everything else in this note is context for that decision." The topic would have been the same. The outcome the message was designed to produce would have been unambiguous. The director would have known within one sentence what response the message required, and would have responded before end of day.
Composite scene. Constructed from observed patterns in product management communication.
First, before drafting any significant communication, state its intent in a single sentence. Not the topic, the outcome. Written on scratch paper, in a note file, or spoken aloud. The sentence should be specific enough that if the communication produces the named outcome, you would consider it successful, and if it produces a different outcome, you would consider it unsuccessful. This practice, run consistently, is the operational core of Intent's development.
Second, distinguish between communications that have a single intent and communications that have multiple intents. Some genuinely need to accomplish more than one thing. When this is the case, name the intents in order of priority, and either design the communication to move sequentially through them or split the communication into multiple messages. Multi-intent communications delivered as single undifferentiated messages consistently underperform.
Third, after sending a significant communication, note what it actually produced. Not what you hoped it would produce, what it produced in fact. Over time, this note-keeping reveals patterns. You will discover that certain classes of your communications reliably produce outcomes you were not intending. This is Intent data, and it is more useful than most feedback you will receive.
Fourth, when receiving a communication, practice reading for intent. What is this message actually designed to produce? Sometimes the answer is different from what the sender has stated. This reading practice sharpens your capacity to design your own intents by giving you a running catalogue of how other communicators handle theirs.
Fifth, be honest about the intents you are unwilling to name. Some of your communications are designed to produce outcomes you would rather not articulate, approval-seeking framed as feedback-seeking, foreclosure framed as invitation, avoidance framed as delegation. Naming the actual intent, even privately, is not a demand that you change it. It is the practice of knowing what you are actually doing so that you can decide whether to keep doing it.
Intent draws on Self. A practitioner whose Self is emerging tends to have shifting intents, the intent adapts to the room, the audience, the mood. The intent becomes whatever the source is currently disposed to want. A practitioner whose Self is developed produces intents that are consistent enough across contexts to be practiced and improved. Without Self as foundation, Intent has no stable ground to be practiced from.
Intent produces the conditions for Grasp. A practitioner cannot model the receiver's completion of a message until the sender knows what the message is for. Grasp asks how will this be received? This question is only tractable if the sender has first answered Intent's question, what am I trying to have received?. Without a stated intent, Grasp becomes an exercise in general audience awareness rather than specific receiver design.
Intent also shapes Narrative and Alignment. Narrative shape follows intent, a narrative designed to close a decision has a different structure than a narrative designed to open one. Alignment mechanisms follow intent, the design for producing motion in the receiver depends on what motion is being sought. Both layers assume Intent has already done its work.
Modern Edge overlays Intent in a specific way. On mediated surfaces where communications persist and are re-read out of context, the intent has to be legible on its own, the receiver cannot ask the sender to clarify what the message was for. A well-formed intent that traveled through synchronous conversation may need to be restated more explicitly when the same content is deployed asynchronously.
Among the five HEARD beliefs, Intent is most directly the practice of The System Is Designed, the belief that outcomes are the reliable products of a system that can be examined and redesigned. Naming the intent of a communication is one of the specific system-level design acts that separates practitioners from performers.
Communications without stated intent are performances of subject matter. Communications with stated intent are design objects with an outcome in mind. The difference between the two, over enough time, is enormous.
If Intent is where your Profile identifies the largest compound return, this is the layer where installing the practice of naming outcomes before drafting messages will change the class of results your communication system produces. Ninety days of naming intents before every significant message produces different messages, and different messages produce different outcomes.