# Technical project kickoff: what to settle in the first meeting

> A kickoff decides most of what goes wrong later. The goal, what is out of scope, who decides and the riskiest assumption to test first. An agenda and a one-page brief to copy.

Source: https://hintvo.com/blog/technical-project-kickoff-meeting | Last updated: November 20, 2026 | Reviewed: 2026-11-20

Most projects that go wrong do so because of something nobody said at the start: a goal two people understood differently, a piece of work everyone assumed someone else would do, a decision nobody knew who could make. A kickoff is one hour to say those things out loud. Write a one-page brief first, and use the meeting to argue with it.

## Before: a one-page brief

```text
# Payment retries

Goal
  Failed card payments are retried safely, so fewer orders fail.
  Success: first-try failures that end in a paid order go from 0 to 80%.

Out of scope
  Bank transfers. Retries of refunds. A new checkout screen.

Who decides
  Scope: product manager. Design: tech lead. Launch date: both.

Riskiest assumption
  That a retry can never charge twice. Test this first.

Dates
  Design review 25 November. First release behind a flag 6 December.

Open questions
  Does the payment provider limit retries per card?
```

## The agenda

1. **The goal and how you will measure it.** Ten minutes. Everyone should be able to say it in one sentence.
2. **Out of scope.** Ten minutes. The most useful list in the brief.
3. **Who decides what.** Five minutes.
4. **The riskiest assumption** and how to test it first. Fifteen minutes.
5. **The first two weeks,** with names. Ten minutes.
6. **Open questions,** each with an owner. Ten minutes.

## Out of scope is the most useful list

Saying what the project will not do prevents more arguments than saying what it will. Every item on the list is a conversation you will not have to have in week six, when someone assumed it was included.

## Decide who decides

For each kind of decision, name one person. Not a group, a person. Everyone can give input. When two people think they own the same decision, the project stalls the first time they disagree.

## Test the riskiest assumption first

Ask what, if it turned out to be false, would make the whole plan wrong. Then make testing it the first piece of work, before anything that depends on it. A week spent proving the risky part early is cheap. A month spent building on a false assumption is not.

## After the kickoff

- Update the brief with what changed in the meeting, the same day.
- Put it where the team will find it, next to the tickets or in the repository.
- Look at it again at the first review. If the goal has drifted, say so then.

> **Where Hintvo fits:** before the call, Prepare me writes a one-page briefing from the code the project touches. When you stop listening, the notes list the decisions, the open questions and the action items with their owners. Prepare me briefings and meeting notes need a pack of hours. See [pricing](https://hintvo.com/pricing).

## Related

- [Write the decision down: a one-page decision record](https://hintvo.com/blog/write-the-decision-down.md): How do I record a technical decision so the team does not argue about it again?
- [Meeting another team about their API: what to ask before you build on it](https://hintvo.com/blog/meeting-another-team-about-their-api.md): What should I ask in a meeting with a team whose API I am going to use?
- [Design reviews: ten questions worth asking](https://hintvo.com/blog/design-review-questions-worth-asking.md): What questions should I ask in a design review?
