Build / Template / 6 min read
A good idea deserves a better brief.
Turn a promising thought into a brief someone else can act on. Start with the decision, not the deliverables.
LLC FIELD NOTES / A PRACTICAL WORKING GUIDE
01
Name the decision
A brief is useful when it makes the next decision easier. Describe the uncertainty you want the work to resolve before choosing its format.
- Write the decision in one sentence.
- List what you know and what you are assuming.
- Name the person who will approve the next step.
02
Make the constraints useful
An honest boundary is more helpful than an unlimited wish list. Give the team enough context to make tradeoffs without guessing.
- Set a working budget and review date.
- Separate must-haves from nice-to-haves.
- Link the source assets and note usage rights.
03
Define a complete response
Agree on what a professional submission contains. This keeps review fair and prevents the scope from expanding halfway through.
- Ask for a rationale and clearly named deliverables.
- Define the feedback window and number of revisions.
- Write the acceptance criteria before work begins.
Make it a working documentKeep the questions.
Keep the questions.
Add your context.
Download the full guide with a checklist and space for ownership, evidence, and the next decision.