9 finished slides

Project kickoff deck

A nine slide kickoff for a warehouse system rollout. It is written to end a meeting with decisions made, which is the only thing a kickoff deck is for.

Make one like thisEditable, then export to PowerPoint or PDF

The full deck

Every slide as it was built, in order. All the content was written for this example, so the structure can be judged on real numbers rather than placeholder text.

Photograph of a large modern distribution warehouse interior, tall racking rows, clean concrete floor, cool daylight from roof lights, wide calm composition, no text, no logos, no people
Photograph of a large modern distribution warehouse interior, tall racking rows, clean concrete floor, cool daylight from roof lights, wide calm composition, no text, no logos, no people

Project kickoff, 18 August 2026

Orchard: one warehouse system

Replacing four site systems with one platform by March 2027.

Nadia Fischer

Program lead, Supply Chain

Slide 1 of 9

Why now

The case

Our four distribution centres run three different warehouse systems and one spreadsheet. Stock accuracy sits at 91 percent, every transfer needs a manual reconciliation, and the oldest system loses vendor support in June 2027.

1
Support ends June 2027

The Kingsway system goes out of vendor support, with no security patches after that date.

2
Stock accuracy at 91%

Roughly $2.4M of write-offs a year traced to counts that do not match the system.

3
No single view

Nobody can see national stock in one place, so we hold buffer inventory at every site.

02

Slide 2 of 9

What is in and out

Agreed with the steering group on 11 August. Anything not listed here is a change request.

In scope

Four sites

Kingsway, Rowville, Wacol and Wingfield, in that order.

Core flows

Receiving, putaway, picking, packing, dispatch and cycle counting.

Out of scope

Transport

Carrier booking stays in the current system this year.

Store systems

Retail replenishment is a separate program in FY28.

Assumptions

Data owner

Each site names one person to own its master data cleanup.

Freeze window

No promotions in the two weeks around each site cutover.

Constraints

Peak season

No cutover between 15 November and 10 January.

Budget

$3.1M approved, with 10 percent contingency held by finance.

03

Slide 3 of 9

Three workstreams

Each has a named lead, a weekly checkpoint and its own risk log.

Platform, Dev Patel

Environments

Build, test and production environments stood up and access granted by week 3.

Integrations

Finance, ecommerce and carrier interfaces mapped, built and tested against real files.

Data migration

Item, location and vendor data cleaned at source, then loaded and reconciled per site.

Cutover runbook

Hour by hour plan for each site, rehearsed twice before the first live weekend.

Operations, Sam Iqbal

Process design

One standard way to receive, pick and count, agreed across all four sites.

Layout and labels

Racking relabelled to the new location scheme ahead of each site go live.

Training

Floor trainers certified first, then two shifts trained per site before cutover.

Hypercare

Two weeks of on-floor support at each site, with a daily issue standup.

Change, Rita Nunes

Stakeholders

Site managers, unions and the finance team briefed on the same message each fortnight.

Comms plan

One page per milestone, posted at the sites and sent to shift leads by email.

Readiness checks

A go or no-go checklist per site, signed by the site manager five days out.

Benefits tracking

Stock accuracy and pick rate measured weekly from four weeks before cutover.

04

Slide 4 of 9

The plan to first go live

Five months from kickoff to the Kingsway cutover, with the other sites following each quarter.

Task
Month 1
Month 2
Month 3
Month 4
Month 5
Discovery and process design
Preparation
Label
Data cleanup at source
Preparation
Build and integrations
Execution
Label
Site training
Execution
Label
Cutover rehearsals
Execution
Kingsway go live and hypercare
Stabilization
Label

05

Slide 5 of 9

Success measures

How we will know it worked

Objective
Key Result
Progress
Status
Accurate stock
Stock accuracy from 91% to 98% at Kingsway
Baseline set
On track
Faster picking
Lines picked per hour up 15% within 8 weeks
Baseline set
On track
One system
All four sites off legacy systems by March 2027
0 of 4 sites
Not started
Clean data
Item master duplicates under 0.5% before each load
3.1% today
At risk
Safe cutover
No more than 4 hours of dispatch downtime per site
Rehearsal 1 due
Not started
Reviewed at the fortnightly steering group. Status is owned by the workstream lead.

06

Slide 6 of 9
Photograph of an empty bright meeting room with a long table, glass wall and a whiteboard with faint marks, morning light, documentary style, no readable text, no logos, no people

How we will work

Monday standup

Thirty minutes, three leads, blockers only. Anything needing a decision goes to the steering group.

Decisions in writing

Every decision is logged with a date and an owner. If it is not in the log, it was not decided.

Risks raised early

A risk raised in week two is a plan. The same risk in week ten is an escalation.

Site voice in the room

A supervisor from the next site to go live joins every design session, not just the review.

07

Slide 7 of 9

Decisions needed

Five things we need from this room

Without these five, the plan on the previous slide does not hold.

1

Confirm Kingsway as the first site and 6 February as the cutover weekend.

2

Name a data owner at each site by Friday, with time released from their day job.

3

Agree the promotion freeze either side of each cutover with the trading team.

4

Approve two floor trainers per site to be released for four weeks.

5

Sign off the $3.1M budget and who holds the contingency.

08

Slide 8 of 9

Questions before we start

Next checkpoint is the steering group on 1 September, with the design walkthrough for Kingsway.

09

Slide 9 of 9

What makes this deck work

Scope has an out list

Naming what is out of scope stops the slow expansion that kills delivery dates, and it is agreed in the room on day one.

Every workstream has a name on it

Three lanes, three owners. Nobody leaves the room wondering who runs data migration.

It ends with decisions, not thanks

The final content slide lists five things the room must approve, each written so it can be answered yes or no.

Questions people ask

What should a project kickoff deck cover?

Why the project exists, what is in and out of scope, who owns each workstream, the plan, how success is measured and what decisions are needed to start.

How long should a kickoff presentation be?

Eight to twelve slides. Long enough to align the room, short enough to leave time for the discussion that matters.

Should risks be in the kickoff?

Yes, but as constraints and assumptions rather than a long risk register. The register lives in the project tools.

Can I adapt this for a client project?

Yes. Generate it with your project described, then edit the workstreams and dates. The structure works for internal and client kickoffs.

Make yours in about a minute

The button opens the presentation generator with this deck already described. Change the wording to your own business, pick a theme, and edit any slide afterwards.

Make my project kickoff deck

Other presentation examples

Investor pitch deck

A full seed round deck for an imaginary freight software company, written the way investors expect to read it. Every number, chart and slide order here is deliberate, so you can judge the structure on real content.

Sales proposal presentation

An eleven slide proposal from a maintenance contractor to a property group. It shows what a buyer actually needs to approve a contract: the change, the plan, the price and the answers to their objections.

Company profile presentation

A ten slide corporate profile for a food manufacturer. It answers the questions a buyer, a partner or a candidate actually asks, with real detail instead of stock phrases about excellence.

New to the builder? Start withmake a pitch presentation with AI, thenchange the theme, fonts and colours.