communicate-consulting-message

name

communicate-consulting-message

description

Frame and deliver one or a few concise consulting messages from a central-case-lead-approved answer. Use for recommendation, diagnosis, insight, status, risk, options, learning, or operating-instruction messages in meetings, emails, updates, and slide titles. Consume the existing Audience/Onboarding Contract, preserve the approved claim state and evidence boundary, and choose a family-appropriate close. Do not decompose the problem, adjudicate hypotheses, change the overall answer, sequence a full storyline, or design slides.

Communicate Consulting Message

Express an approved answer clearly. Do not use wording to repair unresolved evidence, change a hypothesis result, or manufacture action.

Confirm the handoff

Require the approved conclusion/status, proof and uncertainty, claim state, communication job, any real decision/action/threshold/learning gate, and Audience/Onboarding Contract locator. Return the smallest unresolved gap to the central lead; do not reconstruct an answer from raw evidence.

Choose the family and close

Select recommendation/decision, diagnosis, insight, status/progress, risk/warning, options/trade-off, learning/validation, or operating instruction.

governing message → basis → implication → family-appropriate close

The close may be a takeaway, current state, threshold, next learning gate, instruction, escalation, decision, or explicit no decision requested. Require authority, owner, or date only when a real approval, commitment, assigned action, or time-critical escalation is requested.

Preserve claim state and audience

Act as the single owner of expression rules for claim state:

• Facts and supported conclusions may be declarative.
• Estimates use We estimate...; targets use Target....
• Unvalidated propositions use Hypothesis: ... or Test whether....
• Recommendations use Recommend...; material uncertainty stays beside the claim.
• Use causal wording only for an approved causal claim; otherwise use bounded association.

Apply the received audience contract: explain an unfamiliar company by what it is and why it matters, define unfamiliar concepts before acronyms, honor the new-noun budget, and cold-read consequential standalone messages. Audience variants may change relevance, order, vocabulary, detail, and an authority-consistent close; they may not change the fact, scope, period, unit, confidence, caveat, status, or decision boundary.

Use the complete family-specific decision object in message-patterns.md only for pilot/validation decisions, recurring status/weekly updates, or another operating message that needs it. Do not add an approval object to an informational update.

Deliver proportionately

• 15 seconds: governing message and implication.
• 30 seconds: add one proof and the appropriate close.
• Two minutes: add minimum context, two or three proofs, uncertainty, and close.
• Executive email: message in subject; basis, implication, and required response in body.
• Meeting: why it matters, message, proof, and intended outcome.

Before delivery verify one-sentence governing message, correct family, claim-state fidelity, proof fit, first-use comprehension, visible uncertainty, and a close that asks only for what is required. Return evidence, hypothesis, answer, or authority challenges upstream. Use a syndication template only when the user requests a pre-wire/approval record or governance explicitly requires one; never infer agreement from silence.

Do not sequence a multi-message storyline or design slides; route those to $structure-consulting-storyline and $design-consulting-slides.

Load detail only when needed

• Read audience-and-delivery.md for a materially different audience/channel or failed cold read.
• Read message-patterns.md for operating, recurring, decision, or unfamiliar message families—not every short message.
• Read quality-bar.md for consequential delivery or failed review.
• Use stakeholder-syndication.template.md only when explicitly needed.