--- title: 'Team Kickoff Session' description: 'A kickoff session helps the team agree on goals, roles, constraints, working rules, and success indicators before starting a project.' type: knowledge-card locale: en canonical: 'https://yoseno.com/docs/knowledge/team-kickoff-session' --- # Team Kickoff Session A kickoff session helps the team agree on goals, roles, constraints, working rules, and success indicators before starting a project. - **Topics:** Clarity of Roles and Boundaries, Team Alignment, Team Climate, Team Structure Clarity ## What it is This is a kickoff meeting before a new project, phase, or significant change in work. Together, participants clarify why the work is starting, who is responsible for what, what constraints exist, and how decisions will be made. This practice reduces the risk of early expectation divergence, where people start working on different versions of the same task. ## When it helps - The team is starting a new project, phase, or major initiative involving several participants. - Participants have different understandings of the goal, priorities, or criteria for a finished result. - It is unclear who makes decisions, who approves changes, and who is responsible for the next step. - The project has constraints related to deadlines, resources, dependencies, or access that need to be discussed in advance. - The team has previously encountered repeated approvals due to different expectations at the outset. ## How to start 1. Appoint a session owner: typically, this is the project manager, team lead, or manager responsible for initiating the work. 2. Gather participants whose decisions, expertise, or work impact the project's outcome. 3. Prepare a concise agenda: objective, expected outcome, roles, constraints, interaction rules, and open questions. 4. Document agreements in a single record: who is responsible for what, where decisions are stored, and how the team raises risks. 5. At the end of the meeting, verify that each participant can state their role, next step, and the project's success criteria. ## Expected benefit The team starts work faster with a shared understanding: responsibilities are clearer, there are fewer repeated clarifications, and risks become easier to spot before they lead to missed deadlines or conflicts in expectations. ## Common mistakes - Conducting the kickoff as a presentation by a single manager rather than a collaborative agreement on roles and expectations. - Failing to document decisions in writing: after a few days, participants may start relying on different versions of the agreements again. - Discussing only the inspiring goal while omitting constraints, dependencies, and escalation rules. - Inviting too broad a group, causing the meeting to turn into a general discussion without specific decision-makers. - Treating the kickoff as a substitute for regular project management: agreements need to be revisited when conditions change. ## Further reading - Book: Patrick Lencioni, The Five Dysfunctions of a Team - Book: J. Richard Hackman, Leading Teams - Book: Jeff Sutherland, Scrum: The Art of Doing Twice the Work in Half the Time - Documentation: Atlassian Team Playbook, Project Kickoff ## Questions and answers ### Who should lead the kickoff session? Usually the outcome owner: the project manager, team lead, product manager, or team leader. It's important that this person can document decisions and bring the team back to agreements after the meeting. ### How much time should be allocated for this meeting? It depends on the scope of work. A short working meeting may be enough for a small phase, while a complex project might need more time. Don't stretch the session: the goal is not to discuss every detail, but to agree on initial frameworks. ### Can a kickoff be held without an external facilitator? Yes. For most teams, a meeting owner, a clear agenda, and a shared document with decisions are enough. A facilitator is helpful if there is a strong conflict of interest or many participants with equal decision-making authority. ### What if participants disagree on goals or roles? Don't smooth over the divergence. Document the point of contention, assign a decision owner, and set a deadline for reporting back to the team. The value of a kickoff lies precisely in surfacing such disagreements before active work begins. ### How can you tell if a kickoff was productive? After the meeting, the team has a shared document, clear roles, next steps, and a list of open questions. Participants can explain what success looks like and where to go if risks or changing conditions occur. ## Related cards - [Team Charter](https://yoseno.com/docs/knowledge/team-charter.md) — A Team Charter captures goals, roles, communication rules, and decision-making processes, allowing the team to align with shared agreements in their daily work. - [RACI matrix](https://yoseno.com/docs/knowledge/raci-matrix.md) — The RACI matrix helps you agree on who carries out a task, who is accountable for the result, who needs to be consulted, and who only needs to be informed. - [Role Canvas](https://yoseno.com/docs/knowledge/role-canvas.md) — The Role Canvas helps the team explicitly agree on what the role is responsible for, who it interacts with, and how to recognize that the work is going well. - [Agile (Kanban/Scrum)](https://yoseno.com/docs/knowledge/agile-kanban-scrum.md) — Agile through Kanban or Scrum helps the team see the flow of tasks, limit overload, and regularly align priorities, commitments, and results.