A kickoff has succeeded when two people can explain the project the same way. Use the meeting to surface different assumptions while they are still inexpensive to correct.
Write the outcome before the agenda.
Describe the change the project should produce, who will use it and how the team will recognise an acceptable result. An activity such as “launch a dashboard” is incomplete without the decision or workflow the dashboard should support.
Ask participants to review the brief before the meeting and bring one unclear assumption or dependency.
Make the edges of the work visible.
Name what is included, what is excluded and what is still undecided. An explicit “not in this release” is easier to manage than a silent assumption.
| Question | Useful output |
|---|---|
| What must this release achieve? | Acceptance criteria in the user’s terms |
| What are we deliberately leaving out? | An agreed out-of-scope list |
| What depends on another team? | An owner, required input and needed-by date |
| Who can change the scope? | A named decision owner and escalation route |
Use the kickoff to resolve, not announce.
Walk through the areas where expectations differ. Separate a decision made in the room from a question that needs investigation.
- Confirm the problem and desired outcome.
- Resolve scope boundaries and acceptance criteria.
- Review dependencies and the earliest point each can block delivery.
- Agree decision owners, communication rhythm and the first checkpoint.
Finish with the first observable milestone.
Choose a near-term result the team can inspect together. Record what will be ready, who will bring it and what decision the checkpoint should enable. Share the revised brief and highlight only the changes made during the kickoff.
MAKE IT YOURS
Your editable template.
Replace the bracketed prompts, remove what you do not need, and save a version for your team.
PROJECT KICKOFF BRIEF Project: [Name] Sponsor / decision owner: [Name] Delivery lead: [Name] Kickoff date: [Date] 1. WHY THIS PROJECT Problem / opportunity: [What needs to change] People affected: [Users / teams] Desired outcome: [Observable change] Success evidence: [How we will judge the result] 2. SCOPE Included in this release: [List] Explicitly excluded: [List] Unresolved scope questions: [Question / owner / date] Acceptance criteria: [Concrete conditions] 3. DEPENDENCIES AND ASSUMPTIONS Dependency: [Required input] Owner / team: [Name] Needed by: [Date] If late: [Consequence / fallback] Assumption to test: [Statement] Test / evidence / owner: [Details] 4. HOW WE WILL WORK Decisions the lead can make: [Scope] Decisions requiring sponsor input: [Scope] Escalation route: [Who / when] Working documents: [Links] Update rhythm and channel: [Details] Change-request process: [Details] 5. FIRST CHECKPOINT Date: [Date] Result to inspect: [Deliverable] Owner: [Name] Decision we expect to make: [Question] 6. KICKOFF RECORD Decisions made: [List] Open questions: [Question / owner / date] First actions: [Deliverable / owner / due date] Prepared with the MeetriX resource library. Adapt to your organisation. https://meetrix2.lisan.com/resources/project-kickoff/
