How to write an AI project brief
Quick answer: A useful AI project brief defines the task, inputs, output, reviewer, boundaries, acceptance test, and handoff. Decide these before comparing tools or commissioning a build.
A useful brief gives everyone the same definition of done. Write these seven decisions before comparing tools or commissioning a build.
1. The task
Describe the repeated work, who does it, and what triggers it. Keep the first version to one workflow.
2. The input
List the documents, messages, or approved facts the work needs. Establish whether they are available and appropriate to use. Do not assume every tool is permitted to receive customer or employee information.
3. The output
Specify a concrete result: a reply draft, a structured row, an action list, or a content outline. Include one example of a result you would accept.
4. The reviewer
Name the person who checks facts, handles exceptions, and approves external actions. Decide what happens when the reviewer is unavailable.
5. The boundary
State what the system must not decide or do. For an inquiry-drafting pilot, that might mean no sending, no invented prices, and no booking commitments.
6. The test
Select representative examples and record the current time and quality. Compare the whole assisted workflow, including corrections. Define a specific quality checklist and a time target before testing.
7. The handoff
Decide who owns the instructions, documentation, access, and maintenance. If you hire help, agree on the deliverables, price, responsibilities, and acceptance checks before work begins.
A good brief makes a small experiment possible. You can expand after the experiment works.