Build a brief that can be challenged
A useful executive brief shows its sources, assumptions, gaps, and dissent. The goal is not polished authority; it is a reviewable input to human judgment.
Use an approved environment and an approved, redacted source pack. Do not paste confidential board papers, privileged legal material, employee records, customer data, credentials, unpublished financials, or vendor-confidential documents. Confirm rights, lawful basis, retention, and access before processing any real material.
Any production implementation additionally requires approved redacted inputs, rights and lawful basis, data minimization, least privilege, tenant separation, managed secrets, audit logs, representative, adversarial, and regression evaluations, proposal-only behavior, human approval, monitoring, a stop condition, an incident path, and tested rollback.
The EXEC brief contract
Separate the layers
Fact
A bounded claim linked to a permitted source and date. Reviewers should be able to open the source and locate support.
Inference
An interpretation explicitly tied to facts, assumptions, confidence, alternatives, and possible disconfirming evidence.
Proposal
A reversible option with dependencies, risks, owner, decision gate, measurement plan, stop condition, and no automatic execution.
Fact: the fictional dataset records a higher return count for one synthetic category in the latest period. Inference: fit guidance may be contributing, but channel mix is an alternative explanation. Proposal: run a controlled content test after analytics and merchandising owners validate the data. This wording avoids turning correlation into a causal claim.
Prompt for a reviewable draft
Review before circulation
- Open every cited source and verify the claim, date, scope, and units
- Check that quotes and media are licensed and not misleadingly excerpted
- Challenge unsupported causal language and false numerical precision
- Ask a domain reviewer to document disagreement rather than forcing consensus
- Record the model, configuration, prompt, source-pack version, reviewers, and decision
Instructions to sound certain or imitate a famous consultancy can suppress useful uncertainty and invite misleading authority. Specify evidence and decision requirements instead. A polished unsupported answer is a failed brief.
Completion gate
The brief is ready for review when
Prompt features change. Check current official guidance such as OpenAI prompt engineering and Anthropic prompt engineering, then validate the complete workflow with representative and adversarial evaluations.