Project Kickoff Canvas

Framework: Project Kickoff Canvas
Use for: Aligning a cross-functional team on scope, ownership, risks, and success criteria before substantive work begins. Works for product launches, operational initiatives, internal projects, and cross-team programs.
Time required: 60–90 minutes with the core team (3–8 people). Filling it solo first and reviewing with the team is the most efficient approach.

How to use this template

1. Fill in Goal and Success Criteria first. Everything else on this canvas is in service of those two sections. If you can't complete them clearly, you're not ready to kick off.
2. Be explicit about what's out of scope. The most valuable line on any project canvas is often the "What this project is NOT" row. It stops scope creep before it starts.
3. Populate Stakeholders before Timeline. You can't set realistic milestones until you know who has approval authority and who needs to be in the loop.
4. Risks before Dependencies. Risks are things that might go wrong. Dependencies are things outside your control that could block you. They're different and both need owners.
5. Decision rights last. The DACI or RACI row surfaces the conversations most teams avoid — who actually decides — and starting there creates conflict. Resolve scope and ownership first, then lock decision rights.

Project context

Project name: _______________
Project owner: _______________
Date of kickoff: _______________
Target completion / ship date: _______________
Version / iteration: _______________

One-sentence project description:

§1 Goal and success criteria

Problem this project solves:

Goal statement (what changes in the world when this project succeeds?):

What this project is NOT (explicit out-of-scope):

Success criteria (how will you know it worked? Be specific and measurable):

Minimum viable outcome (if you had to ship with half the resources, what would you cut?):

§2 Stakeholders

Who needs to know about this project and at what level?

Executive sponsor (who escalation goes to when the team is blocked):

Key external parties (vendors, partners, customers involved in the project):

Stakeholder risks (who is likely to become an obstacle? What is their concern?):

§3 Timeline and milestones

Project duration: _______________

Critical path (which milestones, if delayed, delay everything else?):

Buffers planned (what contingency is built in, and where?):

§4 Risks

Risks are things that might go wrong that are currently inside your control to mitigate. Rate each: Low / Medium / High.

Top risk that could kill this project:

Contingency plan if top risk materializes:

§5 Dependencies and blockers

Dependencies are things outside your direct control that this project relies on. They require coordination, not just mitigation.

Blocker escalation path (if a dependency goes unresolved, who resolves it and how quickly?):

§6 Decision rights

Who decides what? Use this row to prevent the most common project failure mode: ambiguity about who has final say.

Tie-breaking rule (when the team disagrees and can't resolve it internally, how is it resolved?):

Standing meeting cadence:

Alignment check

Before finalizing this canvas, confirm:

• Everyone on the core team has read the Goal and Success Criteria sections and agrees with them
• Out-of-scope items are written down, not assumed
• Each milestone has a named owner
• Each risk has a named owner and a mitigation plan
• The decision rights table has been reviewed (and any disagreements resolved)
• The executive sponsor is aware of the project and has agreed to the escalation role

Open questions this canvas didn't resolve:

For governance structures referenced in §6, see the DACI, RAPID, and RACI templates in the decision-rights folder. Decision Infrastructure Guide on biztechprimer.com covers the decision-layer vocabulary in depth.