5 reasons to start every project with a kick-off meeting

Michał Merchelski

Nov 29, 20185 min read

5 reasons to start every project with a kick-off meeting

Table of Content

  • The common denominator: kick-off meeting

    • 1. A team that trusts is a team that triumphs

    • 2. Establishing rules of engagement

    • 3. Building a dictionary

    • 4. Non-verbal communication

    • 5. The spark

Having worked on several development projects as part of a remote product team taking care of everything from design to AppStore launches, I’ve had numerous occasions to see that, indeed, sometimes you win and sometimes you learn.

One of the lessons was: a kick-off meeting is a must!

Every project is different when you work at a software house. No surprise here. Some of them are like a brand new highway at sunset (yeah, right...), others are way more bumpy (yep, sounds more like it). The bumpy projects might not be pleasant when you're trying to put out a fire from inside the house, but they have a lot to offer in educational terms.

The common denominator: kick-off meeting

I've been trying to identify the source of the problem among the bumpiest of my projects and I've finally had the “a-ha” moment recently. It was about the kick-off. The most significant red flag connecting all those dirty little projects keeping me awake.

There was no kick-off meeting on any of them. And that was da mistake, an arrow to the knee right at the starting line. All the projects with a proper kick-off went way more smoothly from the very beginning. Of course, there were some problems in the end, but at least we hit the ground running and the client felt involved and co-responsible for the outcome.

Without further ado, I present you the 5 reasons you should always push your team and your client for an in-person kick-off meeting at the beginning of every single project.

DISCLAIMER: By a kick-off, I mean an all-day workshop with the whole team - design, devs, PM, QA, project owner/client, etc. Basically, everyone involved in the project should participate.

1. A team that trusts is a team that triumphs

We all know how rapid, hectic and competitive the digital business gets. Lead, call, NDA, estimate, meeting (maybe), contract, GO. There is little time to really get to know the other side. It's almost impossible to get their trust as most of your credibility comes from your portfolio.

And as digital as the digital industry might be, humans are still humans. We are social creatures, we are guided by our feelings and we don't want to get into business with random, shady people.

The kick-off is a great opportunity to win the client's trust and get them on board with your methods, ideas and approach. It's your chance to become their partner in crime. Trivial as it may sound, a dinner (and some beers) after a whole day of hard work towards a common goal is a seriously bonding experience.

Remember, at the end of the day, your client wants to go to bed with a piece of mind (or at least less horror). They want to know that they picked the right guy to be in their corner. Delivering results is not everything when you invest your own money.

2. Establishing rules of engagement

Moving on to more practical aspects of project work, a kick-off is when all ground rules for further collaboration should be established. It's the moment you should clearly outline the competence of both sides and figure out communication patterns.

This is when you should explain the processes, timelines, feedback loops and expectations regarding day-to-day collaboration. Get your client involved in the sprint planning process, they'll feel more in control and be more understanding when things go south.

You should make sure that the client is OK with all the sprints, scrums, standups, daily Slack updates or whatever practices your team has in place and that she understands the purpose of each.

If your team uses Jira, you should show your client how Jira works, if you use Zeplin, show them how to add comments in Zeplin. Get the picture? Even if they claim to be familiar with a tool, you should see how they use it, and make sure they know it well enough to fit into your process.

It's like explaining your homecourt rules to the new kid on the block.

3. Building a dictionary

If you're at a kick-off, you've probably already done some design work and know the scope of the product.

Now is the time when you make sure that everyone on the team knows what you know and, most of all, what the client knows!

I've gone through some serious quagmires because of miscommunication and semantics. Trust me, it might seem boring, but going through wireframes with everyone and naming every view and every component of the application is worth every second.

Literally, make a dictionary if needed. Otherwise, you risk being bamboozled when your client decides to refer to a question form as "Modular part". 

4. Non-verbal communication

This is a pretty subtle and sensitive matter but spending a whole day with someone can give you a really good picture of his habits, communication approach and how they react to feedback or discussion.

If you work with international customers, always do your homework. Check what are the cultural, especially business-related, traits of the nation you're going to work with. Read a little, ask around, and verify on the kick-off if they are what they are said to be.

There are a lot of subtle intricacies when it comes to customs and workplace etiquette worldwide and you should know who you're getting in bed with. Be prepared.

Pro-tip: Some nations won't tell you outright that you screwed up, your self-reflection is the key to a happy relationship here.

5. The spark

Last lesson for today: it's easier to keep the train going than it is to get it moving in the first place. #kindergartenphysics

If you run the kick-off right, the whole team should be on fire right after. The feeling of starting something new, working as a team and creating valuable products usually gets people going. They are in the room because they want to do cool stuff and all they need is a spark to get their engines revving.

If you're a real hotshot, you can end the workshop with a pep talk (Coach Carter- or Braveheart-style), but a short and loud "Let's do this!" followed with some applause will do.

The point here is: the kick-off is like a GO signal for the whole team, they just start running, the train starts rolling, and all you need to do is keep the momentum throughout the whole project. It's much more effective than trying to push-start everyone individually.

I mean, if they work remotely, there's only so much you can do. Being there in person makes life a lot easier.


Do you have similar experiences? Or think otherwise? Feel free to comment on your experience with kick-off meetings! Drop us a line: 

Don't miss a beat - subscribe to our newsletter
I agree to receive marketing communication from Startup House. Click for the details

Published on November 29, 2018


Michał Merchelski Product Strategist

You may also highlightlike...

How to write a Software Requirements Specification (SRS) for a startup MVP?
Ruby on RailsMVPAgile

How to write a Software Requirements Specification (SRS) for a startup MVP?

Whether you are launching your first startup or you are a seasoned entrepreneur, you should always begin your work with clearly outlining the project's structure. A software requirement specification will help you communicate with the development team and make sure that they deliver what you expect, not what they assume you expect.

Michał Merchelski

Aug 27, 20185 min read

Differences between Agile and Scrum

Differences between Agile and Scrum

Confused about the differences between Agile and Scrum? While Agile is a broader approach, Scrum is a specific methodology categorized under Agile. Explore the disparities here.

Ewa Rutczyńska-Jamróz

Jun 02, 20235 min read

What's the Difference Between Agile and Waterfall Methodologies?
AgileProduct management

What's the Difference Between Agile and Waterfall Methodologies?

Still undecided on whether you adopt an Agile or Waterfall approach to your software development project? As experienced developers, we know the feeling well, and understand even better when an entrepreneur asks: 'Which project management methodology is best for my software development processes?' To find out, it's best we begin simply with 'What's the difference between Agile and Waterfall methodologies?' Lots, as it turns out. So, let's revisit and refresh these Agile and Waterfall methods to help you maximize your resources and ensure your projects are run as smoothly and successfully as possible.

David Adamick

May 05, 20237 min read

Let's talk
let's talk

Let's build

something together


We highlightbuild startups from scratch.

Startup Development House sp. z o.o.

Aleje Jerozolimskie 81

Warsaw, 02-001

VAT-ID: PL5213739631

KRS: 0000624654

REGON: 364787848

Contact us

Follow us


Copyright © 2023 Startup Development House sp. z o.o.

EU ProjectsPrivacy policy