How to run a project kickoff in 30 minutes
Big organisations run project kickoffs with slide decks, RACI charts and a two-hour agenda. Small teams often skip kickoffs entirely and just start, which works until two people do the same thing and nobody does the thing that blocks everything else.
There is a middle ground: a 30-minute kickoff that answers the few questions that actually matter, and ends with the project visible on the board.
Before the meeting (5 minutes of prep)
The project owner writes three lines and shares them:
- Goal: what done looks like, in one sentence
- Why now: the reason this matters this quarter
- Constraints: deadline, budget, anything fixed
If you cannot write those three lines, you are not ready for a kickoff.
Minute 0-5: agree the goal
Read the goal out loud. Ask: does everyone understand what done looks like? Adjust the wording until they do. A shared definition of done prevents most of the arguments that come later.
Minute 5-10: name one owner
One person owns the project. They do not do all the work; they make sure it keeps moving and that the ball never drops between people. See clear ownership without status meetings.
Minute 10-20: list the first actions
Not the whole plan. Just enough to start:
- What are the first five to ten actions?
- Who does each one?
- Which ones depend on someone outside the team?
Write them straight onto the board as you go. Put actions the team owns in Mine or Next, and actions waiting on someone else in Other, with that person's name.
Minute 20-25: find the dependencies
Ask: what could stop this project? Usually the answer is a person: a client who needs to provide content, a manager who needs to approve budget, a supplier with a lead time. Those dependencies are where projects stall, so make them visible from day one. See the easiest way to see blocked work.
Minute 25-30: agree how you will check in
Decide how progress will be seen: a weekly look at the board, a short update in a chat channel, or a check-in at an existing meeting. Avoid creating a new recurring meeting if an existing one will do. See how to run async standups.
After the meeting
The owner sends a short summary: goal, owner, first actions, dependencies, check-in rhythm. If the board already shows all of that, the summary is a link.
What to skip
- Detailed timelines for work you have not started
- Long risk registers
- Assigning every possible task up front
Small projects change as you learn. Plan enough to start, then adjust.
The test
At the end of 30 minutes, every person in the room should know what they are doing first, and the board should show where every action sits. If it does, the kickoff worked.