“It’s one project, but everyone in the group wants something different out of it.”
“How do we even have a productive conversation with that many people in the room?”
“Last time we did a call like this it went completely off the rails, I know we need a kickoff call but I don’t want that to happen again.”
Hearing “kickoff call” and assuming it means “convene a large group to… kickoff the project” without having any meetings before the meeting is a surefire way to derail your meeting before it starts and send your project into chaos before it kicks off.
When you’re kicking off a new project for a group of cross-functional leaders, the last thing you want is a large group of competing interests trying to figure out how to get their questions answered against the crosstalk of a 14 person Zoom meeting.
On a good day, maybe you set up a kickoff call to accommodate the senior leader at the top of your chain of command, plan an agenda, and watch it go off track after a few questions.
On a bad day, the boss skips your meeting and now you have eight bosses, all grumpy, some openly, some simmering silently - and very little idea about how you’re going to build anything.

So how do you plan yourself a project kickoff that is… not that?
First, What is a kickoff call?
And what are we kicking off, exactly?
I don’t know about you, but I’ve been in kickoff meetings where:
A stakeholder wants something added to a cycle already in progress
The user and buyer discovery for a project is done and we’re “kicking off” with a development team who is hearing about the project for the first time
The team leading the meeting has already done months of work on a project and all we need to do is get it out the door ASAP
The entire team is internal and preparing for a new client, who will then have another new kickoff meeting with the client champions, and then the agency and client champions will have yet another meeting with the CEO
The main goal is to check that I have access to email and a couple databases
The main goal is to decide on a single point of contact
I am figuring out how to communicate to the person who called the meeting that the project they want to start will not help them — while making it seem like it’s their idea to change direction
The person who needs to make a decision is only learning about the project for the first time on the call
The marketing team is frustrated that the product feature has already been built and they’re only just now hearing about it
The sales team has already promised the feature to a customer and the product team is frustrated that they have to figure out how to build it
And on and on and on. All shaped differently, all for different goals. Some feel successful in the moment, others feel like shouting matches. Some led to excellent work and happy aligned teammates, others revealed their shortcomings only at the very end of the project.
For a long time, I tried to design a process and set of SOPs that would contain this mess. How do we make sure we design the perfect kickoff call? Okay, sure, maybe not the perfect kickoff call. But one that sets us up for success. Well, what do we mean by success? That list is infinite. How do we pick success for the kickoff meeting?.
Here’s the “meeting retro” for one of my most successful projects. Can you spot the kickoff call?
One day I had a project that just kind of started. A sales leader sent a ticket requesting a feature. I read it, I thought it sounded interesting, I knew it was in line with the vision I’d set for my team that year. I also knew the priorities in my chain of command, so I knew that the spirit of what the sales leader proposed was more likely to be championed than resisted.
At the same time, I knew that the outlines of the solution the sales leader proposed weren’t going to work.
I pinged the sales leader, “I saw your ticket, great idea! You have 30 minutes on Thursday to tell me more?”
We showed up on Thursday, “I love this idea, tell me more about what you’re hoping to achieve?”
The sales leader elaborated. They shared more about the solution they had in mind. I didn’t say no, but I did ask them to share more about the problem they were trying to solve. Like many problems, this one had a hundred possible solutions. As the seller spoke, I started to see 3 other ideas form in my mind’s eye.
I took the input, went back to my team, shared the pitch.
“The sales team has a great idea that isn’t going to work. They want to do X, but we know X doesn’t work. Their end goal is something else, they want to do Y, and here’s a loose outline of an alternative solution, I’m gonna go refine it. Cool? Cool.”
I opened a whiteboard, I added screenshots of my product to the canvas, and I played around with a few different places to put this new feature. I pushed on it here and there, broke the brittle parts, poked around for the flimsy parts, and worked out a V2.
I pinged someone in customer success. The solution I’d devised looked like it could solve a problem in that department, too, so I asked their opinion. “Yes, this is exactly the conversation I can have in the QBR if we have this, plus here is how much TAM it’s going to open up.”
I explained the origin story, told the tale of how the first suggestion from the sales leader sent me down this path, explained that it wouldn’t work the way we hoped so I wanted to find another way.
“Oh yeah we’ve tried to have that conversation a few times on the customer success side of the business, but the way the sales team wants to do it won’t ever work and here’s why.”
I pinged my product team to let them know we had confirmation from the customer success team on our new direction. “I’m pretty sure this is technically inexpensive because of reason A, B, and C, anything I’m missing that stops this from shipping before {sales milestone}?”
Then all 4 of us plus a few others showed up for a regularly scheduled informal touchbase. In that call, I asked the sales leader to explain the goals and project. I said nothing as the customer success leader explained the ways that the sales leader’s solution would not work, so I didn’t have to ever say, “No.” Then I shared that I had another alternative, one that might look something like X but solve the problem in a different way.
“Oh wow that could be interesting, we can definitely do ABC with that idea.”
From there I went and brought the refined, pressure-tested idea to the executive stakeholders. “Here’s the problem we’re solving, here’s how it helps sales and customer success drive revenue, here’s what they said when we showed it to them, here’s where we think it breaks, here’s why we think the outcome we expect is worth the relatively small risk.
“Sounds great, do it!”
A few weeks later the new thing was live.
Which meeting was the kickoff meeting?
This was one of the most impactful projects I worked on that year. If I were to do a retro, I would want to study how the process led to the great outcome. And if I’m building a process, I’m often looking for the moment where that process starts and ends. The “terminal path” as I might call it in a user interface - something you start, run, and then stop when it is complete.
So if you were to look back for the moment the project was officially kicked off in a kickoff call, which one would it be?
Would it be…
The informal session where I pinged my sales leader for more background?
The informal sync meeting where I created the space for customer success to refine the idea so I could present the refined solution?
The multiple DMs between me and my team where we agreed to ship this?
The formal presentation to the execs?
The meeting where we called the sales and customer success team to let them know the thing was live?
The all hands presentation when the team lead said, “The product can now do X, which means sales and customer success can do Y”
None of the above? All of the above?
Was there one kickoff call? Were there many?
Or, the correct answer: depends who you ask.
An effective kickoff is a series of meetings, each one serving a different purpose for you, your team, and your stakeholders
If you ask me, the exec meeting where I secured the blessing to move forward would certainly be a contender.
If you ask me, the informal gathering where I presented the refined V1 with my cross-functional stakeholders would be hard to argue against.
If you ask m, the first discovery call with the seller certainly sounds like a possibility, too.
From my perspective, I could pick any one of these.
From each individual stakeholder’s perspective, each call they were on could have been called a kickoff call.
The exec learned about the project in the exec meeting and committed to providing cover for it.
The folks in the informal gathering agreed to the version of the prototype I’d shared.
The individual meetings I had with sales and CS each introduced the project to the stakeholders involved.
They were all kickoff calls, each serving a different purpose, each one at a just-right time for the shape of this project and this team.
Instead of a Kickoff Call, Plan a Kickoff Call Sequence: Remember to ask “What’s up, DOC?”
Hearing “kickoff call” and assuming “convene a large group to… kickoff the project” without having any meetings before the meeting is a surefire way to derail your meeting before it starts and send your project into chaos before it kicks off.
What you need instead is a sequence of kickoff meetings that precede anything that you might plausibly call a “Kickoff Call” in a calendar invite.
There are 3 types of kickoff calls.
Discovery
Operational
Ceremony
Aka, DOC, aka What’s up DOC? Because as you read this your brain will give you a nice way of remembering it.

Here’s the gist of each of the three types of meetings in your kickoff call sequence.
Discovery Kickoff Goal: Understand the product problem
In a Discovery kickoff call, you’re meeting with people who you will serve and people you will collaborate with to execute the project.
If a leader brings you a solution, you want to learn more about the problem they’re trying to solve. If a leader brings you a problem, you want to learn more about the solutions they have tried so far and what has and has not worked.
You’ll also want to learn more about my team’s capability to execute on the vision based on where it stands today.
In the example I described above, the call with the sales leader was a Discovery Kickoff call. I didn’t call it that because I hadn’t committed to funding the project yet. You don’t have to call yours a “Kickoff call” either at an early stage, but you’ll likely find yourself in situations where it makes sense to do that.
Operational Kickoff Goal: Figure how things work and who owns what
In an Operational kickoff call, you’re meeting with both your internal team and with cross-functional partners. You very likely already have enough strategic intel to start shaping and scoping a solution and are now figuring out how you will work together going forward.
These meetings tend to be a mixture of 1:1 and small group settings and are more about the “how” than the “why” or the “what” (though these questions bump into each other). You will probably have several of them.
In the example I described above, the call with my customer success leader, the calls with my team, and the exec call all had operational elements.
Ceremony Kickoff Goal: Mark the official start of the project
By the time you get to a Ceremony kickoff call, you have a room full of nodding heads. You have had strategic calls in 1:1 and small group settings. You have had operational calls in similarly small forums. You have an idea of what everyone wants out of the project and everyone has an idea of how they’re expected to participate.
Everyone in the room knows their strategic or operational role in the project. Most of the people working on the project will have had the opportunity to ask questions and influence the content of the meeting.
The goal of the Ceremony Kickoff Call is very often about giving the senior leaders an opportunity to ask questions they might not have time to think about without a dedicated time and a formal ceremony for them to see and feel the project’s beginning.
In the example above, both the informal call and the exec call are contenders for the “Ceremony” call.
How to plan a kickoff sequence
In the example I shared, each of the folks involved knew each other. We’d worked together for months or years prior to this project. We were a senior group of mostly ICs coordinating work amongst ourselves. The process that worked well for us here might not work as well might not have worked perfectly in a larger group with more people or more moving parts. The operational complexity of this project was relatively simple, the timeline relatively short. If your project involves 20 people, 200 people, 2 quarters, 2 years, then yours won’t look like mine.
And yet, the more complex and varied your project, the more you’ll want to build a sequence that looks like the one I described to prepare yourself for a successful kickoff call and successful project kickoff.
The volume of each of the three types of calls will vary for every project. Some will need more discovery, some more operational coordination. Some won’t have a real ceremony, others will have several ceremonies. Think “What’s up, DOC?” and think “What are the questions I need to ask?”
Reframe your kickoff sequence away from the meeting and toward the questions and outcomes to get at each stage
When you think “What’s up, DOC?” to plan a project, you take the pressure off a single kickoff meeting to do everything you need to do to start a project.
Break out each phase of the project into a blend of 1:1, async, and group meetings.
Hit these milemarkers in each stage:
Outcomes of Discovery Kickoff Stage:
Write the Headline for Project Success: At the start of a project, “writing the press release” helps us anchor the outcome we want to achieve and the news we want to be able to share.
If our project is successful, our leaders will be able to share it far and wide. What is the message that we want to send? “{Company} launches new feature or product} that enables _____” How do we fill in the blank? What strategic goals will we set?
We know we can move on from discovery into operations when we have a Headline and 3 bullets for the outcome we want to achieve.
Go/no-go decisions: Some projects sound like a great idea but in a few discovery calls we learn they are more complex than our appetite allows or less impactful than we hoped. We may need a few discovery calls to commit to a strategy or a single call to realize our problem is an important one to solve but our solution won’t work.
We know we can move on from discovery when we’re committed to both the shape of our problem and the outline of our solution.
Intelligence collection: Project leaders understand the desired outcomes of the project and begin to understand the shape and scope of what success looks like.
We know we can move on from discovery when we have enough empirical evidence to back up the problem we want to solve and build the solution we have in mind – loosely.
Determine next steps: If we don’t have data on the problem we’re solving, we might collect it as our first step so we can set a baseline. If we don’t have a prototype to align around, we might pull examples together to communicate the direction of our vision.
We know we can move on from Discovery when we have a list of action items for our next steps.
Outcomes of Operational Kickoff Stage:
Define Roles: Understand and agree to each team and department’s contributions to a project.
Determine Timelines: Early on in the project, that means choosing a target end date to ship and target end date for go/no-go decision. As we proceed, we identify additional deadlines.
Collect Data & Tooling: Assess what tooling and projects we do and do not have at our disposal, the technical blockers holding us in place, and anything else we might need to know before we proceed.
We never really move on from the operational stage. But we do move into operating when we have met either a formal or informal set of criteria for knowing that we have our mise en place for the project.
Outcomes of Ceremony Kickoff Stage:
Project is officially sanctioned: Leader officially and publicly sanctions the project. The team has collected enough information for a go/no-go decision and presented it to the leader. The leader gives the official decision in this call.
Share the success headline: Give the team a way to align around a goal and mobilize the message around the agencies involved.
Repeat and recap roles and responsibilities: Who is doing what when? We’ll review details at a high level with more detailed briefs already covered in writing.
This is the only stage that ends at the end of the call.
Next time you need to schedule a kickoff call, remember: What’s up, DOC?
Next time someone asks you to schedule a kickoff call, think about planning a kickoff sequence. Schedule the calls and do the investigation for each of these stages before you have your Ceremony call.
