COST Principle: Clarify, Organize, Simplify, Transfer

You can know the work and still lose the room.

In a standup, a status email, or a walkthrough for a non-specialist, people often start in the middle of their own notes. The audience hears history, jargon, and branching details. They still cannot say what the point was. That is not always a personality problem. It is often a sequence problem: the speaker never locked the core message, never ordered the support, never cut what this audience does not need, and never chose a channel that fits.

COST is a way to do those four jobs in order. It is not a promise that the message will persuade anyone.

COST is a four-step pipeline from thinking to delivery:

The letters are teaching shorthand. The method is the order. Production copy sometimes treats Transfer as a third step and tells people to simplify after they have already spoken. The usable order is still Clarify, then Organize, then Simplify, then Transfer.

COST is preparation. It is not PREP's spoken loop, not SCQA's story setup, and not a full pyramid of arguments. Those can live *inside* Organize if you need a specific shape. They are not COST itself.

A useful COST pass is four decisions, not a poster of four letters.

1. Clarify

Write the core message in one sentence. If you cannot, you are still researching, not communicating. "We should delay the launch one week because the payment retry path still fails for returning users" is a core message. "Let me walk through the sprint" is not.

2. Organize

Order only what supports that sentence. Typical patterns: conclusion then reasons; problem then change; three grouped supports. If you need a named story shape, you can borrow SCQA or SCR *as the order*, then return to COST. Do not paste a feedback model here.

3. Simplify

Cut for this audience. A finance partner may need the dollar effect and the date. They rarely need the class name of the retry job. Simplifying is not talking down. It is refusing to hide the takeaway under work you are proud of.

4. Transfer

Choose channel and length: thirty seconds in the meeting, a six-line email, one slide. Tone follows the room (a board update is not a hallway check). Transfer is delivery of the message you already clarified. It is not a new argument, and it does not require a body-language percentage rule.

If the audience still cannot restate the core sentence, go back to Clarify or Simplify. Do not add more slides.

COST is the lens for think-then-say when the point is not locked yet. Other methods help when the job is already a specific message architecture.

• Meeting contributions. Discussion drifts, and your turn still sounds like a tour of everything you know.
• Written updates. A report or Slack thread buries the ask under technical history.
• Explaining specialist work. The audience cares about impact and next action, not the internal architecture.

Example: Incident update to a business team

An engineer is asked why checkout failed for an hour. Their first draft starts with queue depth, a deploy hash, and three possible root causes.

Clarify. Checkout was down for 52 minutes because a retry job looped on expired tokens.

Organize. What happened, who was affected, what we changed, when we expect it to hold.

Simplify. Drop the class names. Keep "expired tokens," "returning users," and "fix shipped at 14:10."

Transfer. A six-line Slack to the sales lead, not a fifteen-minute architecture tour in the standup.

Implication: COST moved the message from the engineer's notes to what the sales lead can act on. It did not prove the engineer is a good speaker. It showed a pipeline.

Example: A rambling meeting turn

A product manager is asked whether to cut a report from the launch. They narrate four weeks of debate.

Clarify. Cut the PDF report from launch; keep the on-screen export.

Organize. Cost in engineering days, who actually opens the PDF, the reversible follow-up.

Simplify. One number for opens last month, one sentence on the reversible path. No history of the debate.

Transfer. Forty seconds when the question is asked, then stop.

Implication: Same four steps. Transfer was length and timing, not a new deck.

What COST can help with

• Locking a core message before speaking or writing
• Ordering support so the audience is not reconstructing the point
• Cutting detail that belongs to a different audience
• Matching channel and length to the room

What COST cannot replace

• A point-first spoken loop. PREP states a claim, supports it, and restates the claim. COST can feed PREP. It is not PREP.
• A story setup. SCQA walks Situation, Complication, Question, Answer. That is one possible order inside Organize, not the COST pipeline.
• A memo architecture. The Pyramid Principle puts a governing thought on top with grouped support. COST does not replace that hierarchy.
• A short incident update shape. SCR (Situation, Complication, Resolution) is a cousin for rapid updates. It can live inside Organize.
• A persuasion sequence. VSNC (Vision, Steps, News, Contributions) is a different job: make a future believable. COST is preparation, not that sequence.
• Thin thinking. If the recommendation is wrong, COST will only make the wrong point easier to hear.

Honest scope: COST structures preparation from thought to delivery. It does not replace the methods above, and it should not be sold as guaranteed clarity.