Meeting types · Project kickoff
A kickoff that still holds up in week six
Most kickoffs are a good hour followed by a forgotten file. Scope is explained once, risks are mentioned but not recorded, and the decisions that were supposed to unblock the work leave the room without a single name attached.
Curact treats the kickoff as the project's record instead of a presentation. Each block is written beforehand by the person who owns it, the live session is spent only on the open decisions, and every decision leaves with an owner and comes back at the first checkpoint.
30 days, no card, cancel in one click.
How do you run a project kickoff meeting successfully?
A project kickoff is the first session that aligns a team on the goals, scope, and risks of a new project. For remote teams, the plan works best when it is treated as a living record rather than a one-time presentation. Defining what is 'out of scope' and assigning owners to open decisions is what makes the plan hold up in week six.
- 01Define the goal and success criteria clearly before anyone is invited.
- 02Assign scope, milestone, and risk blocks to the people who will own them.
- 03Collect initial thoughts and related context from the team's existing tools.
- 04Review the draft deck and highlight the trade-offs that need a call.
- 05Spend the live session only on open decisions and risk mitigations.
- 06Carry all open items into the project's first weekly checkpoint.
Today
Why kickoffs fade
The meeting itself is rarely the problem. What happens to it afterwards is.
Scope lives in one head
The person who wrote the brief explains it once, and everyone leaves with a slightly different version of what is in and what is out.
Decisions without names
"We'll figure out the auth approach" is agreed by nodding, assigned to nobody, and rediscovered as a blocker in week three.
Risks mentioned, never recorded
Someone raises the dependency that will hurt in a month. It gets a sympathetic murmur and no line anywhere.
The deck is never opened again
A file in a folder that describes a plan the project stopped following on day nine, so nobody trusts it enough to check.
The flow
Before, during and after — with the call kept short
Describing a plan is written work. Choosing between two plans is what a room is for.
Before
Goal, scope, milestones and risks are written by the people who own them, each from a link they can open on their own time and share with their team. Agents pull in related Slack threads and board cards as suggestions, and the host approves everything in one review inbox.
During
Nothing already agreed is read out loud. The session covers the open decisions and the trade-offs, with live polls on the scope calls and questions from the room so the quieter half of the project team is also heard.
After
Each decision is recorded with an owner and a date, the recap posts to Slack, and the open items are carried into the first checkpoint deck with their status. The kickoff stays readable for whoever joins the project next month.
A focus slide written by the sponsor beforehand, with the out column filled in rather than left implicit.
A closing slide naming the decisions the kickoff exists to make, each with the person who will close it.
The kickoff deck
What the project's record contains
Six blocks that come ready-made with the template, each assigned to a person rather than filled in by whoever built the slides.
Goal and success criteria
One sentence on why the project exists and the measurable thing that says it worked. Written by the sponsor, not paraphrased by the deck builder.
Scope, in and out
Two columns, both filled in. The out column is the one that prevents the argument in week five, so it is a required field rather than an afterthought.
Milestones and dates
The three or four dates that matter, each with the person accountable for the milestone rather than for the whole project.
Roles and owners
Who decides, who does the work, who needs to be kept informed — written down while everyone is still in agreement about it.
Risks and mitigations
Collected from the team beforehand, including the ones nobody wants to say out loud, with an owner per risk and what would trigger action.
Open decisions
The questions the kickoff exists to close. Each one gets an owner and a date on the slide, and stays visible until it is decided.
Decisions
A decision that carries an owner
The difference between a kickoff that holds and one that fades is whether its decisions survive contact with the following week.
Every decision has one person, not a team. The name is on the slide and in the Slack recap, so nobody has to reconstruct who agreed to what.
A decision that is still open carries the date it needs to be closed by, which turns a vague intention into something the next meeting can check.
Open items reappear on the next deck in the series with their status attached, so the checkpoint starts from what was promised rather than from a blank page.
The reasoning stays with the decision — the options considered, the room's vote, the questions asked — so a new colleague can see why, not just what.
Example
What one kickoff actually looks like
A cross-functional project with nine people in four timezones, and no evening spent in a slide editor.
- Two weeks out
The host creates the kickoff from the template. The blocks appear ready-made — goal and success criteria, scope in and out, milestones, roles, risks, open decisions, first checkpoint.
- Ten days out
Each block is assigned to the person who owns it. They get a link in Slack, write their part on their own time, and can share the link with the rest of their team to fill in together.
- A week out
Agents propose context from the connected channels and boards: earlier threads about the same area, related cards, previous attempts. Suggestions wait for approval, they never publish themselves.
- Three days out
The host works one review inbox — accept, edit or drop each submitted block and each suggestion. Everyone can read the draft deck and comment before the session.
- The kickoff
Twenty-five minutes on the open decisions only, with live polls on the scope calls and questions from the room. Everything already agreed in writing stays in writing.
- The same afternoon
Decisions leave with an owner and a date, the recap posts to Slack, and the deck stays readable for anyone who joins the project later.
- First checkpoint
The open decisions and risks reappear on the next deck with their status, so the project's record continues instead of restarting.
Agenda
A 25-minute project kickoff agenda, and the days around it
A kickoff agenda that prioritises alignment over presentation. Copy it into your project doc or use it as a starting point for your own format.
Yours to use, with or without Curact. No signup for the template.
Templates
Three ready-made versions of this meeting
Pick the depth that fits the week. Every template opens as a real deck you can edit, reorder or throw away.
Short
The 20-minute small-project start
Goal, scope and the one or two open decisions — for projects small enough not to need more.
20 min · 5 slides
- 1.Kickoff — checkout redesign
- 2.Goal and success criteria
- 3.Scope, in and out
- 4.Open decisions
- 5.That's the kickoff
Standard
The full project kickoff
Goal, scope, roles, milestones, risks and the open decisions — the complete starting record.
30 min · 10 slides
- 1.Kickoff — customer portal rebuild
- 2.Join in
- 3.Goal and success criteria
- 4.Scope, in and out
- 5.Roles
- + 5 more
In depth
The multi-team programme kickoff
The full record for a programme spanning several teams: dependencies, staffing, budget and risk in depth.
52 min · 14 slides
- 1.Kickoff — platform migration programme
- 2.Join in
- 3.Goal and reasoning
- 4.Scope — Platform workstream
- 5.Scope — Data workstream
- + 9 more
FAQ
Questions people running kickoffs ask first
Who writes the kickoff deck?
Not one person the night before. The host sets the blocks — goal, scope, milestones, roles, risks, open decisions — and each block is assigned to the person who actually knows it. They get a link, write their part from wherever they are, and send it back. The host reviews everything in one place and the deck is finished before anyone joins a call.
Do we still need a live kickoff session?
Usually a short one. Reading scope and milestones out loud is written work, so it happens beforehand. The live half hour is for the open decisions and the trade-offs people disagree about — and if nobody disagrees, the kickoff can run entirely in writing.
How does a decision get an owner?
A decision is recorded as its own item with a name and a date, not as a line in someone's notes. The owner is visible on the slide, gets the recap in Slack, and the item stays open until it is closed — so "who was going to sort that out?" has an answer on the page.
What stops the deck from being forgotten in week two?
The kickoff belongs to a series, not to a single date. Its open decisions and risks are carried into the first checkpoint deck with their current status, so the record is reopened by the next meeting rather than by someone remembering to look for it.
Can people who missed the kickoff catch up?
Yes. The deck stays readable afterwards with the questions that were asked, the answers given and the decisions taken. A person joining the project in week four reads the same record the room saw, instead of asking three colleagues for a summary.
Does it work with Slack and our board?
Agents can read the channels and boards you point them at and propose slides — related threads, existing cards, prior work on the same area — with a suggested owner. Nothing is published automatically: every suggestion waits in a review inbox until the host accepts it.
Instead of
What does this replace?
A kickoff deck is often the most important document in a project, yet it is usually the first one to be abandoned. Curact keeps it alive by making it a series.
Project brief doc
Detailed but rarely read by the whole team.
Goal and scope are presented as focused slides, ensuring everyone sees the same version of the plan.
Presentation tool
A static file that dies the moment the meeting ends.
The kickoff deck remains interactive and is the source for the project’s ongoing checkpoints.
Project management board
Too much detail for an initial alignment.
Agents pull in related cards as context without overwhelming the initial kickoff deck.
Slack for recap
Decisions are buried in the thread history.
Decisions leave with an owner and a date, and reappear automatically in the next meeting.
Curact does not replace Slack, your boards or your video call. It sits next to them: the deck is the meeting, and the tools you already pay for stay where they are.
Built by Textalk
Curact is made by Textalk AB in Sweden, a software company that has run its own distributed weekly meeting for years. This is the tool we built for ourselves first.
Participants need no account
People join from a link or a code on screen and answer from their phone. Only the people who build the deck need a login.
Works next to your stack
Slack for the reminders and the recap, your boards for the source material, any video tool for the call itself.
30 days, no card
The trial is the full product, not a stripped demo. Nothing to cancel if you walk away.
Written and reviewed by the Curact team. Last reviewed August 2026.
Other meetings teams run this way
Retro / check-in
Anonymous 1–5 scales and word clouds answered from a phone, so the honest signal is on the screen before the discussion starts.
Read moreWorkshop / brainstorm
Contributions collected on a link days ahead, prioritised by a live vote from everyone's phone, and turned into follow-ups with owners.
Read moreOnboarding / welcome
A repeatable welcome deck: who's who, an icebreaker from phones, and a page the new colleague writes themselves before day one.
Read moreStart the next project with a record, not a slideshow
Set the kickoff up once as a series. The blocks are written by their owners, the decisions leave with names, and the first checkpoint opens with everything still unresolved already on the page.
30 days, no card, cancel in one click.