Project & Development
Kickoff Meeting Prep for Beginners: 5W1H Outline, Agenda, 60-Minute Schedule, Week-One Tasks
Beginner | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)
Beginner: No technical terms. Just answer the whiteboard's questions, following the examples, and it takes shape.
This template helps a leader, starting a week ahead, prepare a kickoff meeting for a new project of four to seven people, down to a 60-minute schedule and first-week tasks. Start by outlining the project with the six 5W1H questions, then put the topics you want to raise into four boxes for purpose, roles, working style, and the first week. Sort the topics into Must, Should, Could, and Won't (MoSCoW) and schedule only Must and Should, so the agenda never outgrows the hour. If you are unsure how to write a kickoff meeting agenda, follow the sample lines on the board and swap in your own words. On the day, work from the same board with your limited-visibility team and write each decided task's owner, due date, and finish marker on the spot. The whiteboard has 4 pages, and the task board has five columns with 4 parent tasks and 3 subtasks each.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Kickoff Meeting Prep Board
How to use (4 pages): ① Page 1: outline the project with the six 5W1H questions and list open items → ② Page 2: write out agenda items, members, and handouts → ③ Page 3: sort items into four groups and build the 60-minute schedule → ④ Page 4: assign week-one tasks with owners and due dates
1/4 Outline the project
① Project and meeting basics (start here)
- Project name e.g. Move internal requests from paper to the web
- Start date e.g. From Mon, Nov 9 to the end of February
- Meeting date and place e.g. Mon, Nov 9, 10:00 for 60 minutes, online
② Outline the project with 5W1H (one line per question)
- Project outline
- What the work e.g. Change expense requests from paper to web input
- Why the reason e.g. Requests take two weeks from filing to payment
- Who the people e.g. One leader and four members. All employees will use it
- When the timing e.g. Start in November, go live at the end of next February
- Where the place e.g. Start in the head-office accounting team, expand to branches in March
- How the method e.g. Check progress in a weekly team meeting. Questions you cannot answer go to ③
③ Open items to check (questions ② could not answer)
| What to check | Ask whom | By when | |
|---|---|---|---|
| Check 1 | e.g. Upper limit of the budget | e.g. Head of accounting | e.g. By Wed, Nov 4 |
| Check 2 | e.g. Whether branch staff join the meeting | e.g. Branch manager | e.g. By Thu, Nov 5 |
2/4 Get all topics out
④ Purpose topics (from What and Why in ②)
- e.g. Share what this project will change
- e.g. Decide the end goal (payment in 3 days)
- Write them as "decide X" or "share X" lines
⑤ Role topics (from Who in ② and ⑧)
- e.g. Decide who designs screens and who talks to accounting
- e.g. Decide whom to ask when stuck
- Leave names out for now and write them as things to decide at the meeting
⑥ Working-style topics (from Where and How in ②)
- e.g. Decide the day and time of the weekly team meeting
- e.g. Decide where to communicate (chat, task board)
- e.g. Decide where to keep decisions
⑦ First-week topics (from When in ② and answers in ③)
- e.g. Decide who investigates the current paper request flow
- e.g. Share the budget limit confirmed in ③
- e.g. Decide the date of the next meeting
⑧ About the members (material for the roles in ⑤)
| Strengths | Available hours (per week) | Candidate role | |
|---|---|---|---|
| Member A | e.g. Thinking about screen usability | e.g. 8 hours | e.g. Draft the screens |
| Member B | e.g. Knows accounting work well | e.g. 4 hours | e.g. Talk to accounting |
| Member C | e.g. Summarizing numbers in a spreadsheet | e.g. 6 hours | e.g. Investigate the current flow |
| Member D | e.g. Unknown (ask at the meeting) | e.g. 2 hours | e.g. Record decisions |
⑨ Handouts to send in advance (send 2 days before the meeting)
- Handouts e.g. The outline from ② and the schedule from ⑪
- What to read beforehand e.g. A one-page summary of the current request flow, readable in 5 minutes
- Send date and method e.g. Send in chat on Thu, Nov 5
3/4 Narrow down to a schedule
⑩ Sort the topics in ④ to ⑦ into four groups (MoSCoW: Must, Should, Could, Won't)
Must essential
- e.g. Decide the end goal
- Topics without which week one cannot start. Three at most
Should important
- e.g. Decide the day and time of the team meeting
- Topics to decide on the day, though later is still fine
Could if possible
- e.g. Decide where to keep decisions
- Topics to cover if time is left over
Won't not this time
- e.g. Decide when to expand to branches
- Topics to decide at the next meeting or in chat
⑪ Schedule for the day (line up the Must and Should items from ⑩, 60 minutes in total)
| Time | Topic | Speaker | To decide | |
|---|---|---|---|---|
| Slot 1 | e.g. 0–5 min | e.g. Greetings and today's flow | e.g. Leader | e.g. Confirm the end goal in ⑫ together |
| Slot 2 | e.g. 5–20 min | e.g. Purpose of this project | e.g. Leader | e.g. The end goal |
| Slot 3 | e.g. 20–35 min | e.g. Split the roles | e.g. Everyone | e.g. Owners for screens and accounting |
| Slot 4 | e.g. 35–50 min | e.g. Working style | e.g. Member A | e.g. Team meeting day and place to communicate |
| Slot 5 | e.g. 50–60 min | e.g. First-week tasks | e.g. Everyone | e.g. Owners and due dates in ⑬ |
⑫ What is settled when the meeting ends
- Purpose is aligned e.g. Everyone can say "payment in 3 days"
- Roles are settled e.g. Screens, accounting, and records have names
- Week one can start e.g. Table ⑬ has an owner and due date in every row
4/4 Assign week-one tasks
⑬ Week-one tasks decided in the meeting, following the schedule in ⑪
| Task | Owner | Due | Finish marker | |
|---|---|---|---|---|
| Task 1 | e.g. Investigate the current paper request flow | e.g. Member C | e.g. Wed, Nov 11 | e.g. Drew the flow on one page |
| Task 2 | e.g. Ask accounting about pain points | e.g. Member B | e.g. Thu, Nov 12 | e.g. Wrote down five pain points |
| Task 3 | e.g. Sketch three screen ideas | e.g. Member A | e.g. Fri, Nov 13 | e.g. Posted the three ideas in chat |
| Task 4 | e.g. Record the decisions | e.g. Member D | e.g. Mon, Nov 9 | e.g. Sent ⑭ and ⑮ to everyone |
| Task 5 | e.g. Tell everyone the budget limit | e.g. Leader | e.g. Tue, Nov 10 | e.g. Wrote it in chat |
⑭ Decided
- e.g. The end goal is "payment in 3 days"
- e.g. The team meeting is every Wednesday at 15:00 for 30 minutes
- Write each in one sentence that means the same to anyone who hears it
⑮ Carried over
- e.g. When to invite branch staff
- e.g. Whether to make the request screen work on smartphones too
- Also write who decides by when
⑯ To decide at the next meeting
- e.g. Next meeting is Wed, Nov 18 at 15:00 for 30 minutes
- e.g. Pick one of the screen ideas from ⑬
- e.g. Decide on the carry-overs in ⑮
Task board contents
Started writing 16 items
Sketch the project
On page 1, write the project name and meeting date, outline the project with 5W1H, and decide who to ask and by when about anything still open. A clear outline keeps you from getting lost when you list topics on page 2. Press Ctrl+F (⌘F on Mac), type "3/4", and you jump to page 3.
Note name and date
On board ①, write the project name, start date, and meeting time and place. Done when the three notes are filled.
Write the 5W1H
On board ②, answer the six questions with one line each. Leave unanswerable ones blank and move them to table ③.
List open questions
In table ③, list up to two open items and decide whom to ask and by when. While you wait, keep the card in the Checking column.
Surface all topics
On page 2, use the outline and confirmed answers from page 1 to put every topic into four boxes, and note the members and handouts. Listing plenty of topics now makes choosing on page 3 easier.
Fill the 4 boxes
In boxes ④ to ⑦, write what you want to discuss as "decide X" or "share X" lines. Done when each box has three.
Fill member table
In table ⑧, write each member's strengths, available hours, and a candidate role. Ask the person at the meeting for any blank cell.
Send the handouts
In box ⑨, write what to send in advance, what to read, and the send date. Done when sent at least two days before the meeting, after schedule ⑪ is ready.
Build the schedule
On page 3, sort the page 2 topics into four groups and line up only Must and Should on a 60-minute schedule. This shapes how the meeting runs, so it is the most important parent task.
Sort into 4 groups
In ⑩, sort the topics from ④ to ⑦ into Must, Should, Could, and Won't. Done when Must has three or fewer.
Time the agenda
In table ⑪, line up the Must and Should topics with time, speaker, and decision. Done when the times add up to 60 minutes.
Define the outcome
In box ⑫, write three things that will be settled by the end, and show them to the members at the start.
Assign week one
On page 4, assign the week-one tasks decided at the meeting with an owner, due date, and finish marker, and record what was decided and carried over. Track assigned tasks in the Assigned column.
Set owner, due date
In table ⑬, write one task per row and decide the owner, due date, and finish marker in the meeting. Done when no cell is empty.
Record decisions
In boxes ⑭ and ⑮, write what was decided and what carries over, and share it with the members the same day.
Draft next agenda
In box ⑯, write the next meeting's date and what to decide. Done when the carried-over items from ⑮ are in.