Kickoff Icebreaker for Beginners: Hopes and Worries Map for a New Project

Project & Development

Kickoff Icebreaker for Beginners: Hopes and Worries Map for a New Project

A kickoff icebreaker for beginners: in the first meeting of a new project, everyone places a piece on a hopes-and-worries map so unspoken worries surface early. Across four pages, page 1 states the aim, introduces the project with 5W1H, and sets roles, piece colors, and placing rules; page 2 has everyone place a piece in one of four spots and write what excites and worries them; page 3 sorts worries into missing information, time, roles, and technology and narrows them to one; page 4 closes the gap to the goal with week-one fixes, each with an owner and a deadline. The task board has five columns - to do, discussing, fixing, awaiting check, and done - and four parent tasks with three subtasks each. Tips: agree that no placement gets blamed, sort worries by type rather than by person, and end by turning worries into week-one tasks. Members of a limited-visibility team can write on it together.

0 Likes 0 Copies Author: WeProcess
kickoff icebreaker for beginners project launch hopes and worries
Other language versions
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode Kickoff Icebreaker for Beginners: Hopes and Worries Map for a New Project
Sign up free and use this template

Whiteboard preview

① Kickoff aim and today's goal (start... ③ Members and roles ④ Piece colors (one each) ⑤ Placing rules ⑥ Using the rules in ⑤, place a piece... Big worry × not very excited Big worry × very excited Small worry × not very excited Small worry × very excited ⑦ One row each: your spot, what excit... ⑧ Missing information (from the worri... ⑨ Time ⑩ Roles ⑪ Technology ⑫ A typical worry per type, with size... ⑬ From ⑫, choose the first worry to t... ⑮ Fixes to close the gap (what to do,... ⑯ Flow of the week-one fixes Kickoff Hopes and... How to use (4 pag... Aims, what excite... Rules and agreements Worries Fixes and findings 1/4 Introduce the pro... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Place hopes and w... ↙ 3/4 Kickoff aime.g. Six people from different teamslearn each other's names, hopes, and worries Today's goale.g. Choose the first worry to tackle, andgive the week-one fix an owner and a deadline Time plan (40 minutes total)e.g. Intro 10 min, place pieces and talk 15 min,narrow down 10 min, set fixes 5 min ② Introduce the p... This projecte.g. Launching a member … Whatwhat we build e.g. Turn the shop's member card into a phone app Whywhy we do it e.g. No more lost paper cards, and more visits Whowho takes part e.g. Six people from sales, development, and support Whenby when e.g. Start this month, launch in six months Wherewhere we talk e.g. The weekly meeting and this board Howhow we work e.g. Build in two-week rounds and show everyone Write each name and their role in this project e.g. Sam (sales) works with the shops e.g. Taylor (dev) builds the app screens A piece is one small sticky note in your color e.g. Sam = blue, Taylor = red If colors run out, write your initial e.g. Everyone places at once, then we talk e.g. No blame and no laughing, wherever you place e.g. One minute each, and passing is fine 縦軸: Worry (bottom... e.g. Maybe I cannot keep up with two jobs. The first place to listen e.g. I like the new tech, but I have never used it e.g. Still watching. Ask what could become exciting e.g. I am glad to turn the shops' voices into a product Your spot What excites you What worries you e.g. Sam (blue) e.g. Big worry × very excited e.g. Making the shops happy e.g. Unclear who makes the final call on specs e.g. Taylor (red) e.g. Big worry × not very excited e.g. Learning a new payment system e.g. Not sure how many hours a week I can give Member 3 e.g. Small worry × very excited e.g. Hearing customers directly e.g. Unsure where the old app's history is documented Member 4 e.g. Big worry × very excited e.g. Teaming up with a new department e.g. Nobody has touched the payment system 3/4 Narrow to one worry → 4/4 4/4 Set week-one fixes Worries from ⑦ caused by things we do not know e.g. Unsure where the old app's history is documented e.g. Do not know who the shop contact is e.g. Have not heard the budget limit Worries from ⑦ about not having enough time e.g. Not sure how many hours a week I can give e.g. Will we make the launch date e.g. Some days we cannot fit the weekly meeting Worries from ⑦ about who does it or who to ask (people issues go here too) e.g. Unclear who makes the final call on specs e.g. Who takes the shops' questions e.g. Who to ask when stuck Worries from ⑦ about not knowing how to do it e.g. Nobody has touched the payment system e.g. Will it run on older phones e.g. Can we hold member data safely Typical worry Size (large, medi... Who knows best First step Missing information e.g. No history of the old app e.g. Medium e.g. Priya from support e.g. Ask where the files are kept Time e.g. Not sure how many hours a week I can give e.g. Large e.g. Each team's manager e.g. Talk to managers about available hours Roles e.g. Unclear who makes the final call on specs e.g. Large e.g. The project lead e.g. Name one person to decide Technology e.g. Nobody has touched the payment system e.g. Medium e.g. The outside payment vendor e.g. Ask for a briefing date The first worry to tackle, and whye.g. Unclear who makes the final call on specs.It is large, and we can name that person in week one What we do with the other worriese.g. Talk about time in the week-two meeting.Keep the rest as tasks on this board ⑭ Split the worry... As-IsCurrent state e.g. Spec questions go to three people and the answers differ Gap / issue e.g. Nobody decides last, and how to decide is not set To-BeTarget state e.g. By the end of week one, everyone knows who decides and where to ask What to do Owner Deadline Sign it is done Fix 1 e.g. Name one person who decides on specs e.g. Morgan, the project lead e.g. End of day 1 e.g. Everyone knows the name Fix 2 e.g. Make one place on this board for spec questions e.g. Taylor e.g. Day 2 e.g. Questions are collected in one place Fix 3 e.g. Write how to decide (who to ask, by when) e.g. Sam e.g. Day 3 e.g. A sticky note on how to decide sits next to ⑤ Fix 4 e.g. Review at the end of week one e.g. Everyone e.g. Day 5 e.g. The next worry is picked from ⑫ 1. Share it todayTell everyone, including people who missedthe meeting, the worry from ⑬ and the fixes in ⑮ 2. Owners actEach owner in ⑮ carries out the fix by the deadlineand marks "Sign it is done" when finished 3. Check in midweekOn day 3, ask each person in a wordwhether any fix has stalled 4. Review at the end of week onePlace the pieces in ⑥ againand pick the next worry from ⑫ → 2/4 Place hopes and w... ↙ 3/4 Narrow to one worry → 4/4 Set week-one fixes
100%

Drag to move, scroll to zoom

Task board contents

To do 16 items

Introduce project
Map hopes & worries
Narrow the worries
Set week-one fixes
Write the aim
Intro with 5W1H
Pick color and role
Place all pieces
Fill the table
Spot the clusters
Sort into 4 types
Size & first step
Pick the first one
Write the gap
Table the fixes
Share week-one plan

Discussing 0 items

Fixing 0 items

Awaiting check 0 items

Done 0 items

Related templates

← Back to templates