Andrew Luxem

Business Writing: Make the point, evidence, mechanism, and action easy to find

A document contains relevant information but makes the reader reconstruct the recommendation, evidence, decision, and next action. This brief shows the mechanism, failure check, and adoption test.

Andrew Luxem
Andrew Luxem
CRM, Lifecycle & AI Strategy

2 min read
The argument
A document contains relevant information but makes the reader reconstruct the recommendation, evidence, decision, and next action.
The skill should make the point, evidence, mechanism, and action easy to find.
Give the draft to one informed reader. Ask for the decision, strongest evidence, and required action. Revise anything they cannot identify quickly.

A document contains relevant information but makes the reader reconstruct the recommendation, evidence, decision, and next action.

The useful response is not more ceremony. It is a mechanism that can make the point, evidence, mechanism, and action easy to find.

What the skill produces

The Business Writing skill turns supplied context into a self-contained business document organized around point, evidence, mechanism, and action. It should expose missing evidence instead of inventing it. The free skill packages this mechanism for explicit use. It does not fetch remote instructions, and the practitioner remains responsible for the facts and final decision.

Run the mechanism

  1. Lead with the recommendation, decision, or material status.
  2. Use evidence to explain why it matters and show the operating mechanism.
  3. Close with the required action, owner, and date.

The owner should review the output against the original evidence before it is used. Any unresolved assumption stays labeled, with an owner and date when it affects the decision.

Failure check

Formatting cannot rescue an unclear argument. A document that needs a narrator is not yet self-contained.

Adoption test

Give the draft to one informed reader. Ask for the decision, strongest evidence, and required action. Revise anything they cannot identify quickly.

Keep the skill only if it improves the artifact or decision against that baseline. Revise the playbook when the same failure survives more than one review cycle.

Infographic

A DOCUMENT SHOULD NOT NEED A NARRATOR infographic
Andrew Luxem
20 years building CRM and lifecycle programs at Amazon, Ancestry, and Stanley Black & Decker.