Build a project kickoff brief that survives the first meeting
A practical project kickoff brief covering the outcome, constraints, decisions and evidence that teammates and AI assistants need.
Project kickoffs generate plenty of conversation. Two weeks later, someone asks why the team chose a particular approach and gets three different answers.
A useful kickoff brief gives future work a stable starting point. It should be short enough to read before a task and specific enough to prevent the most likely wrong turns.
Start with the change you want
Describe the outcome in observable terms. “Improve onboarding” is too broad. “A new workspace administrator can invite a teammate without contacting support” tells the team which experience matters.
Then name the evidence you will use to judge it. That might be a usability session, a support issue disappearing or a completed workflow. Do not invent a numerical target just to make the brief look measurable.
Capture boundaries before tasks
Use these fields:
Outcome and intended user.
Current problem, with links to evidence.
Scope and explicit exclusions.
Constraints that cannot move without approval.
Decisions already made, including the reason.
Open questions, each with an owner.
Acceptance evidence and the person who reviews it.
Keep proposed choices separate from approved decisions. Otherwise an assistant may turn a suggestion from the meeting into an instruction for implementation.
Include one concrete example
For an invitation project, describe a representative administrator, the action they take and what successful completion looks like. Include one important exception, such as an invitation to an existing member. Examples expose disagreements that abstract goals hide.
Avoid loading the brief with every research note. Link to supporting material and state when a task requires it. A designer exploring the flow and an engineer changing permission checks need different supporting details.
Update the brief at decision points
When scope changes, update the current brief and add a short dated explanation. Keep the original outcome visible so the team can see whether the project has changed direction.
At the next handoff, ask the receiving person or assistant to restate the outcome, exclusions and unresolved questions. If their understanding differs, repair the brief before assigning more work. That check is cheaper than discovering the mismatch after delivery.