BriefMe
Sign in

Project kickoff agenda template (60 minutes)

Projects conflict in week six over something that was unclear from the start. A full fifteen minutes goes to scope and non-goals together — above all to what the project explicitly will not touch. Being clear about what you are not building prevents scope creep and the arguments that follow later.

Topic Minutes Running total
Introductions Names, roles, and what each person brings. Keep it brief unless the team is entirely new. 5 5
Why and goals Why does this project matter? What does done look like? Be specific; vague goals hide conflict. 10 15
Scope and non-goals What the project will do and what it will not do. The non-goals half prevents week-six scope arguments. 15 30
Roles and ways of working Who decides what. How you communicate. What the working rhythm is. Document it. 15 45
Risks What could derail this? Dependencies, skills, timeline constraints. Name them now, not week three. 10 55
Close Confirm understanding of goals and non-goals. Check in on energy. Set the next sync point. 5 60

Opens a working agenda you can start straight away. Nothing to sign up for — anonymous agendas are kept for 7 days.

Build it with your assistant

Already connected to BriefMe? Paste this. Connect BriefMe to Claude 

Using BriefMe, create a 60-minute project kickoff for eight people: a 5-minute introductions, 10-minute goals, 15-minute scope and non-goals, 15-minute roles and ways of working, 10-minute risks, and 5-minute close.

Questions

How long should a project kickoff be?
One hour is standard for a new project team up to about ten people. Thirty minutes feels rushed; 90 minutes suits a larger team or one with complex dependencies. Whatever the duration, the non-goals section should never be compressed: that is the part that prevents week-six arguments.
What if the goals are still fuzzy at kickoff?
Then the kickoff job is to name the fuzziness and what you need to do to clarify it by when. A fuzzy goal that everyone mistakes as certainty is worse than no goal at all. Use this meeting to get as concrete as you can, and schedule the research that will get you the rest of the way.
Should non-technical people be in the kickoff?
Yes. Project scope affects resourcing, timeline, and risk for everyone involved. Someone who thinks they understand non-goals because they were mentioned in passing will make different decisions later than someone who heard them discussed and stated explicitly. Include the people who need to say no.

Related templates