What it means
A project can start badly when different people mean different things by 'done'. A kick-off gives them a shared starting point before separate teams spend time and money on conflicting assumptions.
Hold it after there is enough approved work to discuss, and for a client project read the statement of work, signed scope or project charter first. If the commercial terms are still being negotiated, label open points rather than presenting a proposed feature as agreed.
Invite people who can explain the work and make relevant decisions, such as the sponsor, project lead, delivery team and key stakeholders, with a client representative joining a shared external project. Atlassian's project-kickoff guidance identifies purpose, roles, responsibilities and success markers as core topics, and a useful agenda also covers boundaries, milestone assumptions, dependencies and how the team will communicate.
Start with the 'why' by stating the business problem, intended user and desired outcome in plain language. A software migration may aim to reduce order-entry errors, not simply to launch a new screen, and that distinction helps the team make later trade-offs.
Then define deliverables and exclusions: if a website redesign includes product pages but not payment processing, say so. Agree on what acceptance means by identifying who reviews each deliverable, the criteria and the feedback window.
'Looks good' is too vague for a complex data conversion, where sample record accuracy and required reports may be more useful. Walk through roles and authority too, including who leads the work, approves content, signs off spend and can request a change.
Discuss the schedule with dependencies visible, since a supplier delivery, permit or client data set may be needed before work can proceed. A date without its assumptions can make the project team look late when the input was never available.
Surface risks early by asking what might prevent success and how people will notice in time, such as a data owner who is unavailable, an untested integration or a site with restricted access, and choose communication norms including the update channel, meeting cadence, document location and escalation route for a blocked decision. Record decisions, not just attendance, by circulating a short recap of agreed scope, open questions, owners and due dates, so that an unanswered point remains visibly open rather than becoming an assumed approval.
Do not use a kick-off to bypass formal change control, because if the client requests an extra dashboard the team should record the request and assess cost and timing under the agreement, and a friendly conversation is not a substitute for an authorised change order. Different projects need different meetings, from a short internal discussion for a two-week improvement to separate internal and client kick-offs for a multi-vendor implementation, and the result should be reviewed a few days later with the baseline revisited if the project changes, keeping both the original decisions and the approved revision.
In practice
Real-world examples.
Example
An implementation team agrees that product migration includes active items only and assigns the client to validate a sample file. The exclusion of discontinued items is written into the recap. Both sides leave knowing what will and will not be moved.
Example
A sponsor asks for an extra dashboard. The team records it as a change request rather than promising it during the meeting. Cost and timing are assessed under the agreement before any work begins.
Example
The project lead sends a recap naming the data owner, the first milestone and two open approval questions. Each open question has an owner and a due date. The sponsor can see at a glance what still needs a decision.
Formula
Calculation
Decision closure = kick-off decisions resolved / decisions identified x 100. It is a simple way to see how much remains open after the meeting.
Worked example: a kick-off identifies 10 decisions and resolves 7 of them. Closure = 7 / 10 x 100 = 70%. The remaining 3 decisions need named owners and dates, not silent assumptions.
If a follow-up call two days later resolves 2 more, closure rises to 9 / 10 x 100 = 90%, and the last decision is escalated to the sponsor with a deadline before any dependent work starts.Case study
Seen in the real world.
This entirely fictional example concerns Stonebridge Clinic, an invented business replacing its booking system. In a first meeting, one team assumed historical appointments would migrate while the vendor planned only future bookings. The project lead compared the signed scope and recorded historical migration as an open change request.
The group agreed on a test file, acceptance owner and weekly updates. The vendor did not begin the extra work until the authorised change process settled scope and price. This kept a useful meeting from becoming an accidental new promise.
Watch out
Common mistakes.
- Calling a meeting a kick-off before the approved scope and key stakeholders are known, then treating guesses as decisions.
- Leaving without named owners, acceptance criteria or a record of open issues.
- Promising extra scope or a fixed date verbally without the contract's change process.
Questions
People also ask.
What is a kick-off meeting?
It is the opening working meeting to align people on purpose, scope, roles and next steps.
Who attends?
The sponsor, project lead, delivery team and relevant stakeholders; include a client when the project calls for it.
What should be agreed?
Agree on goals, boundaries, decision rights, success measures, dependencies and a route for unresolved questions.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%