Direct
State the answer
Do not make the reader excavate the recommendation from context.
04 / Application
Direct enough to create movement, precise enough to preserve uncertainty, and human enough to sound like one person actually means it.
04.1 / Character
Good writing names the material thing, the relationship that matters, and what changes next. It avoids the fog of generic AI and startup language.
Direct
Do not make the reader excavate the recommendation from context.
Structural
Explain how parts of the system affect one another and where authority sits.
Concrete
Say workflow, operator, record, decision, resident, queue, cost, proof.
Human
Do not flatten complex work into automation theater or pretend uncertainty has vanished.
04.2 / Reasoning sequence
This is the default reasoning shape for a memo, briefing section, product rationale, or design critique.
Observation
The record exists in the system, but ownership and follow-through still live in local workarounds.
Pattern
Across tools and teams, people keep reconstructing the same missing coordination layer.
Implication
The organization cannot reliably improve what it cannot see, assign, close, and remember.
Strategy
Begin with one consequential event and build the complete accountable loop around it.
04.3 / Before + after
The better sentence is usually shorter because it names the operating reality instead of promising a feeling.
Use
Build the provider and its intelligence layer as one company.
The sentence names what is being built and the structural decision that distinguishes it.
Avoid
Leverage cutting-edge AI to revolutionize the future of care.
The sentence substitutes excitement for a company model, operating claim, or measurable change.
Use
Important exceptions need an owner, a clock, and evidence of closure.
Concrete nouns make the design obligation visible.
Avoid
Create a seamless, intelligent experience for all stakeholders.
Nothing in the sentence can be designed, tested, or held accountable.
04.4 / Copy roles
Visible copy is not narration, and metadata is not personality. Keep each role within its load-bearing limit.
| Role | Job | Limit |
|---|---|---|
| Monument | A rare first-order axiom or destination. | One complete thought; usually 2–7 words. |
| Display | Defines a section or decisive synthesis. | One line or a controlled two-line wrap. |
| Headline | Names the specific claim or change. | 16 words in film; one sentence on the web. |
| Body | Explains context, evidence, or implication. | One idea per paragraph; 45–65ch reading measure. |
| Label | Orients, indexes, dates, or verifies. | Short noun phrase; uppercase; never prose. |
| Film claim | Tells the viewer what the visual proves. | 36 visible words maximum unless composition is tested. |
04.5 / Opening + exit
The opening names the tension the artifact will resolve. The exit explains what the particulars mean at a durable level.
Opening contract
Start with the answer or tension. Do not start with the source, meeting, production process, or a title-only frame.
Exit contract
End with the consequence of the model. Hold the final composition; do not fade to black or append a generic CTA.
04.6 / Avoid
Revolutionize, unlock, empower, seamless, intelligent experience, AI-powered transformation.
Leverage, synergy, thought leadership, game-changing, category-defining without proof.
Do not turn a hypothesis, open question, or founder ambition into an established fact.
Do not expose tools, workflows, prompts, or production mechanics in recipient-facing copy.
The work should feel rigorous because it is rigorous, not because the copy says it is.