How to lead a Project Kick-Off

Want to get your project off to the best start? The goal is to ensure everyone on the team (including the client and stakeholders) has a clear understanding of any potential weak spots and, ultimately, to create a hypothesis statement. The Project Kick-Off recipe is a curated set of five Workshop Tactics designed to help you evaluate newly created or already existing projects.

🧠 Learn how to…

✔️ avoid potential problems

✔️ create clear focus

✔️ identify risks

✔️ prioritise risks

✔️ summarise results

🃏 Cards used…
Human story map.
A sticker with the words huh test on it.
Punchy prototypes.
Anatomy of an insight.
📚 Before you start

In person

  • Prepare (book room, invite people, write and share agenda)
  • Materials (whiteboard, sticky notes, pens)
  • Tech check (charger, adapter, screen projector)
  • Room (refreshments, temperature, chairs, wall space)


  • Prepare (book room, send call link, invite people, write and share agenda)
  • Materials (whiteboard, sticky notes, pens, Miro board)
  • Tech check (charger, adapter, screen projector)
  • Room (refreshments, temperature, chairs, wall space)


  • Prepare (invite people, write and share agenda, create and send call invite)
  • Materials (Miro board)
  • Tech check (charger, adapter, Microphone/headphones)
⏱ How much time?…
  • Over multiple days: three to five short sessions.
  • On one day: 2.5 hours session and 2 hour session with a longer break in the middle.
✨ Extra reading…

👀 Let’s walk through this recipe using an example: the launch of a new marketing campaign to help an alcohol-free drink company attract new customers.


Use Premortem to avoid potential problems


Time: 1 hour

🧠 Core Objective: identify problems before they happen, and make a plan to prevent them from happening.

The Premortem tactic will get you to think about all the ways that your project might go wrong, so you can effectively plan to stop it from happening. Running this tactic at the beginning of a project highlights things that might slow you down or stop you later on. What’s the worst that could happen? Now’s the time to figure that out. 

💡 Tip: invite project stakeholders to the session. Use Stakeholder Map beforehand to help you invite the right people (complete before).


  1.  Since this is the start of your overall workshop, make sure to start with an icebreaker to warm everyone up.
  2. Brief the room on the project. Define what success is for this project: who, what, where, when, why, how. Give indication of the goal of this project. (5 minutes)
    Example: We will be creating and implementing a new ad campaign for our alcohol-free drink company that will roll out nationally with a 100,000 people reach. This campaign is important for the client because…etc.
  3. Imagine the project has failed and ask participants to write down every possible reason why (one per sticky note). If needed, give your group more structure with subjects: brand, financial, team, clients, etc. (10 minutes)
  4. Ask participants to share their notes. (15 minutes)
  5. Group similar ones with Theme Sort. (5 minutes) 
  6. Discuss potential risks and talk about how to mitigate these risks. (15 minutes) Example: What do we need to do to avoid _____ from happening…
  7. Optional: Assign responsibilities for actions with Who, What, When. (10 minutes)

Use Problem Statement to create clear focus


Time: 1 hour

🧠 Core Objective: frame the problem the project aims to solve, and what the measures of success will be.

The Problem Statement tactic allows you to capture the project’s goals, problems, and measurable success criteria. A problem statement gives your team a clear focus for their work. It also defines any important constraints. Constraints are important for group work; they provide guardrails that keep the team grounded and aligned. 

💡 Tip: this is great for projects where the client is unclear what problem they’re trying to solve.


  1. Invite stakeholders to this session to make sure you’re all agreeing on the same overall problem to tackle.
  2. On sticky notes, answer the following questions and Theme Sort.
    • What are the current goals of the product or system?
    • What problem does the stakeholder(s) want addressed?
    • Which goals aren’t being met?
    • What is the explicit request for improvement that doesn’t dictate a specific solution?
  3. Complete the following template from the group’s answers. Discuss and amend until everyone is happy with the problem statement.

[Our service/product] was designed to achieve [these goals].

We have observed that the product/service isn’t meeting [these goals], which is causing [this adverse effect] to our business.

How might we improve [service/product] so that our customers are more successful based on [these measurable criteria]?

Example Problem Statement
  • [Our alcohol-free drink ad campaign] was designed to achieve [an awareness of our alcohol-free product for a specific target group].
  • We have observed that the service isn’t meeting the goal of [reaching and educating our main target group], which is causing [lower income for our business].
  • How might we improve [our targeted ad campaigns] so that our customers are more successful based on [an increase of sales and returning customers]?

Use Assumption Collecting to help identify risks


Time: 1 hour

🧠 Core Objective: gather all of the team’s user and business assumptions about the problem.

The Assumption Collecting tactic helps you uncover the assumptions you and your team may have about a project. Declare what you think to be true at the start of the project to help you identify risks. Make everyone’s assumptions visible to remove any surprises later on. Use your clear problem from the previous workshop to start unpacking your assumptions from. 

💡 Tip: this is an opportunity for everyone to brain-dump what they think is ‘the truth’ about the project. It’s very interesting to get stakeholders and clients in a room and they give you six different answers to questions like “I believe my customers have a need to…”. 


  1. Invite key stakeholders to the workshop. If you used Stakeholder Map in the previous tactic, include those people. Otherwise, try it now to help you invite the right people (complete before)
  2. Read through assumption questions and give examples to fill in the blanks if needed. (10 minutes)

  3. Ask participants to fill in the blanks themselves, one answer per sticky note. (30 minutes)

  4. Theme Sort the answers. (10 minutes)
  5. Identify any other missing assumptions specific to your project. (10 minutes)

Using the Assumption Map to help prioritise risks


Time: 1 hour

🧠 Core Objective: prioritise your most unknown and riskiest assumptions, to give the project the right focus.

The Assumption Map tactic helps you prioritise your assumptions based on certainty and risk. Identify your riskiest and most unknown assumptions to gain a clear picture on where to focus your energy. It’s safe to assume that this is one of the most valuable tactics to have in your back pocket. 

💡 Tip: the point is to work out which assumptions carry the most risk, and which include the most unknowns.


  1. Make an Assumption Map with Certainty and Risk on the axes to plot assumptions. (20 minutes)
    Assumption Map prioritisation matrix
  2. Plot each assumption from the previous session on the map, asking the group (20 minutes):

    • How bad would it be if we were wrong about this?
    • How much understanding do we currently have?

    Tip: it can help to ask “is this one more or less risky or unknown than this one?” to get a sense of relativity between items.

  3. Finish plotting all assumptions on the map. (20 minutes)

  4. Identify the riskiest and most unknown assumptions and turn them into a Hypothesis Statement for validation (see next workshop).

Use Hypothesis Statement to summarise results


Time: 30mins

🧠 Core Objective: frame your prioritised assumptions as experiments that will put them to the test.

The Hypothesis Statement tactic tests your assumptions, treating each of them as experiments by turning them into hypotheses. Take the subjective and political conversation out of the decision-making process, and focus the team towards feedback from users and customers.

💡 Tip: be mindful of the fact that bias is a risk at this point. It’s easy to look for the positives in a product or project you believe in, and to ignore the negatives or risks. It can be good to get the team to come up with hypotheses in groups, and then swap them for testing to try to encourage objectivity.


  1. Put the riskiest and most unproven assumptions from the previous session into a hypothesis template (see example below). (20 minutes)
    • Use a quantitative or qualitative insight to support the assumption. 
    • State what you believe to be true.
    • Identify feedback that will confirm whether you are right or wrong.
    • Break down the hypothesis into smaller parts if it’s too big to test with a single statement.
  2. Have the group Secret Vote on the hypothesis they want to commit to. (5 minutes)
Hypothesis Examples
  • We believe that [making a new life-style ad campaign] for [pregnant people] will achieve [an increase of pregnant customers and sales].
  • We will know this is true when we see [our pregnant customers actively engage with the ads and buy products].

What next?


Congratulations you have completed your Project Kick-off! You have now gotten your project off to the best start, while also preventing potential problems. 

Now you’ve kicked off your project, you’ll need to give your team the best chance of success with Team Time.

Do you have questions, tips or tricks, etc? Join our Slack community of over 13,000 professionals.

1 thought on “How to lead a Project Kick-Off”

  1. Looking forward to using this Guide in real time with my team after reading it through in much detail. The examples are exactly what I was looking for. Can’t wait to use the other Guides as our project continues on.


Leave a Comment

Let us know what thoughts or questions you have about this guide so we can improve it.

If you leave us your email, we'll let you know if we update this guide based on your feedback.