The Project Start: A Kickoff Meeting That Prevents Later Conflicts

Why project conflicts often begin on the first day

In the sixth week of a project, it turns out that the customer understood 'employee training' as two days on site, while the project team planned one hour by video. The project manager thought the customer would supply the data, the customer thought the company would collect it. Nobody lied, and nobody was sloppy. The different pictures were there from the start. They only surfaced once it became expensive.

In small companies, projects often start without a dedicated kickoff meeting. The salesperson hands over, the technical team gets going, and the customer receives an email with the start date. That saves an hour at the beginning and often costs many times that later.

This article answers one question: what does a kickoff meeting have to look like to actually prevent later conflicts in the project? To answer, we first clarify the terms, then present the thinking model of shared mental models, examine the findings, weigh an important counterposition, and finally describe a 90-minute agenda.

A project does not begin with the first task, but with the first moment in which everyone has the same goal in view.

What is a kickoff meeting, and who belongs in it?

A kickoff meeting is the first joint meeting of the people who carry a project: your own project team, the responsible person at the customer, and, where necessary, other parties such as decision-makers or future users. It takes place after the commitment and before the actual work begins. Its purpose is not to get acquainted or to present the plan, but to align everyone's expectations and clarify open points.

The kickoff should be distinguished from two other meetings. The internal handoff from sales to the project team precedes it. It transfers what was discussed during the sale and is described in the article on the handoff from sales to the project team. The project plan is created partly beforehand and partly in the kickoff itself. How it fits on one page for small teams is shown in the article on project planning for small teams. In the 30-day plan from the article on customer onboarding, the kickoff is the second touchpoint and takes place within five working days of the commitment.

An image from sports shows what this is about. A well-practiced soccer team knows without a shout where the pass will go, because everyone has the same picture of the play. A newly assembled team has to create that picture first; otherwise two players run in the same direction and the space behind them stays empty. A project team with customer involvement is almost always a newly assembled team.

The thinking model: shared mental models

A mental model is the inner picture a person has of a task or situation: what needs to be done, in what order, with what means, and who contributes what. In the early 1990s, the psychologists Janis Cannon-Bowers, Eduardo Salas, and Sharolyn Converse proposed explaining teamwork through the similarity of these pictures (Cannon-Bowers, Salas, and Converse 1993). When team members have similar mental models, they can better anticipate the needs of the task and the behavior of others and coordinate without discussing everything explicitly.

Research distinguishes two kinds of shared models. The task model concerns the work itself: goal, work steps, tools, resources. The team model concerns the collaboration: who has which role, who expects what, how communication and decisions work. Project conflicts arise in both areas. The dispute over the scope of training is a conflict in the task model, the dispute over who collects the data one in the team model.

For the kickoff meeting, a clear task follows: it must make both models visible and align them. A kickoff in which only the project manager presents the plan does not check which pictures the others have in mind. It creates the impression of agreement without establishing it.

What studies show about shared pictures and project success

Carraro, Furlan, and Netland (2025) examined how shared mental models influence problem-solving in teams. Between September 2020 and September 2021, they surveyed production employees at 13 manufacturing companies in Veneto. After removing teams whose members rotated weekly, 266 employees in 48 teams remained. The similarity of mental models was not asked about directly but calculated from the team members' answers, separately for the task and team model.

The result: the more closely individual employees matched their colleagues' task and team models, the more likely they were to solve problems independently before they grew, and the better the team coordinated its problem-solving. The two models worked differently: the shared task model mainly supported individual action, the shared team model mainly coordination within the team. A caveat: the data come from one region and one industry, and only a small part of the differences in problem-solving lay between teams.

How early the different pictures arise is shown by an interview study with twelve project managers at an IT service provider in Sri Lanka. Dilan Viduranga and Divakara (2025) found that many difficulties in project delivery went back to failures during the sale, such as unclear commitments and insufficiently clarified requirements. The study is small and qualitative. But it fits what the article on the handoff to the project team describes: the riskiest commitments from the sale are the ones not written down anywhere.

Harmony or groupthink? A counterposition

There is a serious objection to the goal of shared pictures. If everyone thinks the same, perhaps nobody thinks critically anymore. Research on groupthink describes how groups under pressure for consensus suppress objections and overlook risks. A kickoff that mainly creates harmony could encourage exactly that.

Carraro and colleagues explicitly pursued this question. In their data, shared models led not to less but to more independent problem-solving. The authors explain this by noting that a shared picture of the task is what gives individuals the confidence to act independently, because they know where the team wants to go.

I therefore read the objection not as an argument against alignment but as a requirement for its form. What should be shared is the picture of goal, scope, and roles, not the opinion on every solution. A good kickoff therefore explicitly looks for differences and risks instead of assuming agreement. Welcoming objections at the kickoff brings them in early, while they are still cheap.

The 90-minute kickoff agenda

The following agenda is the tool of this article. It clarifies seven points, each part of the task or team model, and ends with a check of whether the pictures actually match. For small projects 60 minutes are enough, for larger ones it should be 90.

1. Goal and success criteria (15 minutes)

   Each participant writes down in advance in one sentence how they will recognize success at the end. The sentences are read out and condensed into two or three shared criteria.

2. Scope and what is not included (15 minutes)

   The scope from the order confirmation is reviewed, especially the 'not included' point. Where there is ambiguity, it is resolved today or noted as an open point.

3. Roles and responsibilities (10 minutes)

   For every important task it is settled who is accountable, on both sides. With many parties, a small RACI matrix helps.

4. Dates and milestones (10 minutes)

   The key milestones are named with date and responsible person, including dependencies.

5. Customer's contribution (10 minutes)

   What the customer has to deliver and when: data, approvals, access, contacts. Each item gets a date.

6. Communication and decisions (10 minutes)

   Who decides on changes, how are they recorded, when are there progress updates?

7. Risks and playback round (20 minutes)

   Everyone names the biggest risk from their perspective. At the end, each participant restates in one sentence what should be finished by when and what they contribute themselves.

The last step is the most important. The playback round shows whether the pictures match. If two sentences differ markedly, that is not a failure of the kickoff but its real yield. The difference costs ten minutes of clarification today and a conflict in week six. The content of points 2 and 5 should already be in the order confirmation, as the article on the order confirmation describes. For point 3, the RACI matrix is suitable.

What follows beyond the individual case

Shared pictures are not created once and then remain. With every change, every new participant, and every interim result, they can drift apart again. The kickoff is therefore the beginning of an alignment that continues throughout the project, for example with a short playback question in every progress meeting: does our picture of the goal still match?

For the company as a whole, it is worth collecting experience from kickoff meetings. Which points were unclear in several projects? Which questions should already have been asked during the sale? These lessons belong in the template for the next quote and the next kickoff, as described in the article on project closure and lessons learned.

• Every project above a defined size starts with a kickoff meeting with the customer.
• Participants write down their picture of success in one sentence in advance.
• Scope, what is not included, and the customer's contribution are discussed explicitly.
• The kickoff ends with a playback round.
• The summary goes to everyone involved on the same day.

Conclusion: how does a kickoff meeting prevent later conflicts?

The question at the start was
a kickoff meeting has to look like to prevent later conflicts. Research on shared mental models gives the answer in its basic idea: teams work together better when they have a similar picture of the task and the roles, and the study by Carraro and colleagues shows that such pictures tend to promote rather than stifle independent action. A kickoff therefore prevents conflicts not by presenting the plan, but by making everyone's pictures visible and aligning them: goal and success criteria, scope and what is not included, roles, dates, the customer's contribution, decision paths, and risks. The playback round at the end checks whether this has succeeded. A conflict that becomes visible at the kickoff is no longer a conflict but a clarification.

How to get started

1. Define the project size above which a kickoff meeting with the customer is mandatory.
2. Adopt the seven-point agenda as a template for the next project start.
3. Ask the participants of the next kickoff to write down their picture of success in one sentence in advance.
4. Schedule the playback round firmly and hold it even when time is short.
5. Send the summary on the same day.

Anyone who has done this two or three times usually notices already in the playback round how many invisible differences a project without a kickoff would have carried along.