What a Good Project Kickoff Looks Like (Hint: It’s Not About Design)

Most website project kickoffs start with the wrong conversation. They start with design — mood boards, competitor sites, inspiration from Dribbble, layout preferences. The client gets excited. The designer gets excited. A few weeks later, something isn’t working, and nobody can trace it back to where it went wrong.

Here’s what actually matters at kickoff, in the order it matters.

1. Why are we doing this?

Not “we need a new website.” That’s not a reason. The real reason is one of these, and it’s worth being precise about which:

• We’re losing leads because our current site converts poorly.
• Our business changed and the site is out of sync with what we do now.
• The current site is broken or unmaintainable and we need to start over.
• We’re launching a new product or service and need a place for it.
• Our competitors launched something that made us look outdated.
• We’re raising money or selling the business and the site needs to match.

Each of these requires a different project. A “conversion optimization” site is structured very differently from a “we’re launching” site. A kickoff that doesn’t name the reason ends up trying to solve all of them at once, which means solving none of them well.

2. Who are we building for?

Not “everyone who might be interested.” The specific people who, when they land on your site, should leave with a clear reason to contact you or buy from you.

A useful exercise at kickoff: name three specific visitor types and, for each, describe:

• What they were doing right before they arrived (search? referral? ad?)
• What question they’re trying to answer by visiting your site
• What they should see in the first 5 seconds
• What you want them to do next

If the team can’t answer these, the project isn’t ready to start — no matter how good the designer is.

3. What does success look like?

Write it down. Make it measurable. “More leads” is not measurable. “20% more qualified lead form submissions, measured quarterly” is. “Faster” is not measurable. “Core Web Vitals passing on the homepage and top 10 landing pages” is.

If you can’t name measurable success criteria, you won’t know whether the project worked. And if you don’t know whether it worked, you can’t tell whether the next project is improving on it.

4. What do we have to work with?

Realistic inventory:

• Content (what exists, what needs to be written, who’s writing it)
• Images and brand assets (logos, photography, colors, fonts)
• Existing systems the site has to talk to (CRM, email marketing, payment, analytics)
• People (who from the client side is making decisions, who’s reviewing, who’s signing off)
• Timeline and budget

Most projects underestimate content by a factor of 3. Kickoff is when you catch this, not three weeks later when the designer needs real text.

5. What are we not doing?

Maybe the most important question. A project kickoff should explicitly name the things that are out of scope — not because they’re bad ideas, but because “we’ll figure it out later” is how projects double in cost.

Common out-of-scope items to name explicitly:

• New photography (are we hiring a photographer or using existing/stock?)
• Copywriting (is the team writing or hiring a copywriter?)
• Migration of old blog content
• Custom integrations
• Multi-language support
• SEO audits of existing content
• Ongoing maintenance plan (separate agreement)

Everyone at the kickoff should leave with the same understanding of what’s in and what’s out.

6. How will we communicate?

Where does the team talk to the client? Slack? Email? A project tool? How often? Who decides what? Who approves? What happens when there’s a disagreement?

Projects that don’t set this up default to chaos. The client sends emails to three different people who each respond with different answers. Decisions take days because nobody’s sure who should make them. Revisions pile up because there’s no clear approval step.

A short, explicit communication plan — “weekly Monday calls, questions in Slack, written approvals in the project tool” — saves weeks of friction.

What design conversations should look like at kickoff

Very brief. “What’s the tone we’re going for?” and “Are there visual directions we want to rule out?” is plenty. Detailed design talks happen after the strategic conversation, not instead of it. Jumping to design before you know the answers to everything above is how projects drift off course.

The kickoff test

If your project kickoff spent more than 30% of the time on design, you skipped the important parts. If it spent less than 10% of the time on success criteria and scope, you skipped the most important parts.

A good kickoff feels a little bit boring. Nobody is looking at pretty images. Everyone is writing things down. Disagreements surface early, when they’re cheap to fix. The design conversation, when it finally happens, is informed by everything that came before, and it goes three times faster because nobody is designing in a vacuum.

That’s what a useful kickoff looks like. Worth slowing down for.

Photo by Matheus Bertelli on Pexels.