Customer Kickoff Meeting

Purpose

Projects can sometimes start off a bit wonky because we dive straight into the project without getting to know the client and truly understanding some of the tacit, latent, informal requirements which might not have been recorded, but without which mean we don’t fully understand what needs to be done to succeed.

Purpose: A simple way to help improve the chances of the project going well is to meet with the key clients before the project running.

Objective

The objective of connecting and meeting with the customer before the ‘real’ start is to level set expectations outside of the potentially much more emotionally and politically charged ‘real’ project start. It’s an opportunity to establish some rapport with your customer, communicate essential project and team information and get as much relevant information as possible prior to the project kickoff meeting with the whole client team.

You can use the kickoff meeting as an opportunity to refine the project process and feedback to your project team. The discussion should be focussed on how you’re going to work together and as much as possible, set and align expectations. It’s an important meeting to have so that you can cover off project management aspects of the project without a huge audience of stakeholders who might complicate the discussion!

Sample Kickoff agenda

Although every client meeting requires its own agenda tweaking, try and cover off these project management basics. We’ve created this sample project kickoff agenda with a rough idea of timings so you can fit this into a 60 min meeting:

  • Introductions – some warm and fuzzy banter (5 mins)
  • Review the project teams – who’s responsible for what? (3 mins)
  • Approval process – the process and personnel for acceptance deliverables? (3 mins)
  • SoW Review – what are we doing, when, how, and what will we produce? (20 mins)
  • Discuss Risk, Issue and Change Management – what’s the client’s attitude and approach to manage to risk and change? (3 mins)
  • Reporting – how will we track and communicate project progress, and to whom? (3 mins)
  • Collaboration – what tools will we use to work together? (3 mins)
  • Assets – what do we need to get started? (5 mins)
  • AOB – anything else that we need to discuss? (5 mins)

Sample questionaire

Prepare questionaire to interview customer with some sample here

Introductions – some warm and fuzzy banter (5 mins)

As long as your customer hasn’t brought along the entire project team for the ride this is a chance to have a bit of a heart to heart so that you can run the project better with fewer nasty surprises. The goal here is to get to know your customer outside of the context of the project and begin to develop a relationship and level of trust that develops over time and carries you through the ups and downs of the project.

Review the project team – who’s responsible for what? (3 mins)

The purpose of discussing the project team is to try and gain and share some insight on team dynamics.

You’re trying to get a behind-the-scenes perspective on who’ll be involved in the project and to what extent. You want to know the best way of engaging with them so they’ll help to progress the project. It’s really helpful to understand who the allies or supporters of the project might be and who is most likely to cause trouble.

It’s also an opportunity to sell the resources you’ve got booked on the project so that the client has a sense of confidence in the team that’s going to be at the client kickoff meeting. By giving them a bit of a behind-the-scenes insight into your team, hopefully, your client will reciprocate and give the skinny into the personalities who could impact the project, for better or worse.

Approval process – the process and personnel for accept deliverables? (3 mins)

After running through the ‘who’s who’ of the project teams and identifying the team, it’s an easy transition into governance, and who’ll need to sign of what, during the project. It’s important to clarify from the SoW what’s been assumed in terms of signoff in terms of timeline and rounds of revision

You’re trying to get and understanding from the client whether or not the process that you’ve assumed in your SoW is going to work. Is the timeline long enough? Are there enough rounds of revision accommodated for within the SoW? Are some of the team difficult to schedule for meetings or approvals? Are they off on vacation during the project?

SoW Review – what are we doing, when, how, and what will we produce?

This is an opportunity to take the customer through your draft SoW in granular detail, and yes, that means that – detailing how the project will be run, what activities can be completed, and to what extent (within the proposed budget and timeline) and what the deliverables will be. It’s important that you highlight rounds of review, dependencies and assumptions so that you’re on the same page with regards to what the project will ultimately deliver.

If you leave a discussion about the SoW to after the kickoff meeting, it can turn ugly – the dynamics of a large client team throwing around opinions of what should be in and out of scope are never pretty. Dicussions about scope are best reserved for small meetings with the client where you can have a discussion without turning it into a round table debate.

Discuss RAID (Risks, Assumptions, Issues, Dependencies) and change management – what’s the client’s attitude and approach to managing risk and change? (3 mins)

As part of rounding out the discussion on the SoW, it’s worth discussing with the client their preference for dealing with risks and issues as well as their appetite for change. If you can, in advance of your meeting, prepare a risk or RAID log and run through it as part of your discussion. You want to set the expectation from the start that you want to be transparent about identifying and responding to risks and issues collaboratively together.

You’ll benefit from getting an understanding from the client as to how much budget wiggle room there is. A useful way of framing it can be to ask the client whether there’s additional budget to pivot the project if new opportunities present themselves – such as additional rounds of design development, feature buildout or user testing. You need a shared understanding as to whether they’re hoping to

Remember too, to talk about the use of contingency and to get aligned on what the contingency is for, and how it can be used; is it a risk and issue budget or to accommodate small changes as the project progresses? Recommend an approach for how you think it should be used so that there’s clarity on what you’ll be doing when something pops up on the project that you weren’t planning for.

Reporting – how will we track and communicate project progress, and to whom? (3 mins)

Tracking project progress will require a status report which shows how the project is tracking on budget, timeline, tasks and milestones. Similarly to the preparation you’ll need to do for demonstrating how you’re planning to manage risk, it’s also helpful to prepare a status report that you can share with the client and so you can ensure that the format and detail works for them.

Getting the format and details right for your status report can be important because it’s usually tied to billing. You need to ensure that the client is getting the right level of ongoing detail so they don’t hold up payment of invoices. To help with that, track the budget on your status report with the upcoming invoice amount and when it will be billed.

Agree the distribution list for the status report so that everyone who needs to be in the loop, is kept up to date with what’s happening on your project. It’s always better to distribute the report to a wider audience than strictly necessary so that in the event that something doesn’t go to plan, no one can turn around and claim they were unaware.

Collaboration – what tools will we use to work together? (3 mins)

Most project managers and teams will have their default collaboration toolkit defined. But whether it’s Basecamp or Jira, Trello or Kanbanize, make a plan with your team of how you’re going to work together so that you can share with the client a plan for what you’re going to use, and how you’re going to use them. Then check with the client to make sure they’re happy with the selected toolkit and are able to use that platform to share files, information, status updates and to have project conversations.

Assets – what do we need to get started? (5 mins)

There’s always ‘stuff’ that’s needed before projects can get started properly. Make a list of all the things you need to remember to ask the client for so that you can get started, in priority order, so they can work through the most critical items first.

AOB – anything else that we need to discuss? (5 mins)

Wrap up the conversation with some clearly defined next steps and an opportunity for the client to raise anything that they want to cover off. Often just asking; Is there anything else we should know? will spur the clients to share things they hadn’t previously mentioned that are worth knowing.

And finally, be sure to end on a happy note. Go back to the banter you started with – it’s a chance for you to develop some rapport and get to know them better; find out what they enjoy outside of work, what they’re doing at the weekend, what they’re watching on Netflix or what sport they’re into. Do the groundwork for getting to know them as individuals and so you’ve got something to talk to them about next time you connect.

Remember to share the good news

Don’t keep all your newfound knowledge to yourself. After your meeting with the client, you’ll then need to go back to your team and bring them up to speed with your discussion so that they’re properly prepared for the kickoff meeting.

Sample