Team & People
Tuckman Model for Beginners: Team Stage Check | Everyone Places a Piece and Picks Next Actions
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.
A Tuckman model team check: everyone places a piece on one of 5 stages, then picks 1–2 actions.
Read more Show less
The five stages are forming, storming, norming, performing and adjourning. Write the events since launch, place one stamp per person on the closest stage and say why. Where pieces scatter, list the troubles, compare actions on two questions (can we do it now, does everyone agree) and vote with circle stamps. Bruce W. Tuckman set out the model in 1965; adjourning was added in 1977. A stage is not a score, so never rate people with it.
Suits 4–8 people, 30–45 minutes after a regular meeting, in a team 1–3 months old. Set the project visibility to "Unlisted" and choose this team so only members see the board, making it easier to explain your pieces. Place the pieces again after 30 days.
The whiteboard has four A4 pages (current state, pieces, actions, review) with a spot for last time's result. The task board has 5 columns, 4 parent tasks and 12 subtasks.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Tuckman Model Team Stage Check Workshop
How to use (4 pages): ① Write the last result, events and team state (sections①–⑤) → ② Place pieces on the 5 stages, with reasons and gaps (sections⑥⑦) → ③ Compare actions from the troubles and vote down to 1–2 (sections⑧–⑫) → ④ Set first steps, owners, deadlines and signals; re-place in 30 days (sections⑬⑭)
1/4 Write current state
① Last result, ground rules (start here)
- Result of the action chosen last time e.g. Leave blank the first time. From the second time, write something like "Made a roles table → overlapping duties fell from 3 times a week to once a week"
- Today's purpose and attendees e.g. 45 minutes after the June regular meeting. Align the views of 5 people and decide the action to try in July. Attendees are 2 from planning, 1 from research and 2 from sales
- Piece color for each person e.g. Planning lead (50s) = red, planning (20s) = orange, research (40s) = green, sales (30s) = blue, sales (20s) = purple
- Ground rules for placing e.g. One piece per person. Explain with events. Never use it to rate people, and do not blame anyone for where they placed
② Events since launch (write by month)
| Events | What went well | What clashed | |
|---|---|---|---|
| April | e.g. At the kickoff we shared the aim of the new skincare product | e.g. All 5 attended the weekly meeting | e.g. Nobody settled who would ask for the prototype |
| May | e.g. The first prototype was ready | e.g. Research moved the skin-compatibility test up by a week | e.g. Planning and sales split over the price |
| June | e.g. 10 store staff tried it | e.g. Sales shared the feedback they collected with everyone | e.g. It was unclear who decides, so the launch date stalled for 2 weeks |
③ Ease of talking (seen in meetings)
- How to fill in: write what you actually saw in meetings and chat, one fact at a time
- e.g. Mostly the planning lead and a sales member (30s) speak in the regular meeting
- e.g. Research stays quiet in meetings and sends objections by chat afterwards
④ How we decide (who decides how)
- e.g. The planning lead alone decides the prototype direction
- e.g. Price was nearly decided by a planning-sales majority vote, then stalled
- e.g. Decisions are not recorded, so the same talk comes up next week
⑤ Helping each other (asking, giving)
- e.g. Sales (20s) does not ask for help even when stuck
- e.g. Research tells everyone its free test days on its own
- e.g. Before deadlines the work piles up on planning (20s)
2/4 Place stage pieces
⑥ From ②–⑤, one piece each on 5 stages
- Forming Just gathered. People hold back and check goals and roles with each other e.g. 1 purple piece (sales, 20s)
- Storming Opinions and ways of working clash. More arguments, and some things stay undecided e.g. 3 pieces, red, green and blue (planning lead, research, sales 30s)
- Norming Rules and roles come together. People accept each other's ways and can decide by talking e.g. 1 orange piece (planning, 20s)
- Performing Trusting each other with tasks to deliver results. The team fixes its own rules as it goes e.g. Nobody placed one this time
- Adjourning The job is done and the team heads toward breaking up. Work is handed over and lessons are kept e.g. The team will disband after launch. Nobody placed one this time
⑦ Pieces from ⑥, reasons and gaps
| Pieces | Reason | Gap in views | |
|---|---|---|---|
| Forming | e.g. 1 (sales, 20s) | e.g. Not yet clear who to ask for what | e.g. The other 4 thought it was already clear who to ask |
| Storming | e.g. 3 | e.g. Price and launch date lead to arguments | e.g. The planning lead saw "good debate" and research saw "tiring" |
| Norming | e.g. 1 (planning, 20s) | e.g. Prototype steps are ready every week | e.g. They only looked at the prototype work, not the price talks |
| Performing | e.g. 0 | e.g. Nobody placed one | e.g. All 5 agreed it is still far off |
| Adjourning | e.g. 0 | e.g. Nobody placed one | e.g. 2 people did not know when the team will disband |
3/4 Choose the actions
⑧ Trouble with roles (from ⑦)
- How to fill in: pick one gap from ⑦ and write in one line what is hard because of it
- e.g. Not knowing who to ask, sales (20s) stops asking questions
- e.g. The person asked for a prototype changes every time
- e.g. Before deadlines only planning (20s) works overtime, so prototype requests go out late
⑨ Trouble with process (from ⑦)
- e.g. It was unclear who decides, so the launch date stalled for 2 weeks
- e.g. Decisions are not recorded, so we repeat the same talk next week
- e.g. Price talk is left to the end of the meeting and time runs out
- e.g. There is no place where everyone can see the test results
⑩ Trouble with talking (from ⑦)
- e.g. Research does not object in meetings and sends it by chat later
- e.g. Some see arguing as "good debate" and others as "tiring"
- e.g. Sales (20s) has not spoken once in a meeting
- e.g. Objections get answered with "but", and the talk stops
⑪ Compare actions from ⑧–⑩, 2 votes each
| Action | Quick to do? | Everyone agrees? | Votes | |
|---|---|---|---|---|
| Option A | e.g. Make a roles and who-to-ask table and show it on the meeting screen | e.g. ○ 30 minutes at next week's meeting | e.g. ○ All 5 agree | e.g. 4 votes |
| Option B | e.g. For each agenda item, set who decides and the deadline first | e.g. ○ From the next meeting | e.g. △ The planning lead hesitates a little | e.g. 3 votes |
| Option C | e.g. Take 5 minutes at the start of meetings for objections | e.g. ○ Can start right away | e.g. △ Research prefers to submit it in writing | e.g. 2 votes |
| Option D | e.g. Spend half a day talking once a month | e.g. × Schedules do not match | e.g. △ Sales travels a lot | e.g. 1 vote |
⑫ Chosen and set-aside actions, reasons
- Chosen action and reason e.g. Option A. 4 votes, can start next week and all 5 agree
- Second chosen action and reason (leave blank if only one) e.g. Option B. 3 votes. It directly addresses the stalled launch-date decision (⑨)
- Action set aside and reason e.g. Option D. The 5 schedules do not match. Change option C into a written form and compare again next time
4/4 Test and review
⑬ Branch ⑫'s action into first steps
- e.g. Roles and who-to-ask table, decide who decides first
- e.g. Make a roles table First step: write out the duties of all 5 people, one line each
- e.g. Add who to ask First step: decide who to ask for prototypes, tests and price, one person each
- e.g. Decide who decides first First step: for each agenda item of the next meeting, write who decides and the deadline
- e.g. Keep a record of decisions First step: read out what was decided in the last 5 minutes of the meeting
⑭ Owner, deadline, check and signal
| Owner | Deadline | How to check | Signal and fallback | |
|---|---|---|---|---|
| Roles and who to ask | e.g. Planning (20s) | e.g. End of June | e.g. Count the questions with no one to ask each week | e.g. Continue at once a week or less. If it rises, go back to (section⑧) |
| Decider and deadline | e.g. Planning lead | e.g. First meeting in July | e.g. Number of agenda items stalled for over 1 week | e.g. Continue at 0. At 2 or more, change how we decide and go back to (section⑨) |
| Record of decisions | e.g. Sales (30s) | e.g. Every weekly meeting | e.g. Times the same talk came up the next week | e.g. Continue if 0 for 2 weeks in a row. At 3 or more, stop and go back to (section⑨) |
| Re-place in 30 days | e.g. Planning lead | e.g. After the late-July meeting | e.g. Re-place pieces on section⑥ and compare with last time's pieces | e.g. Stop if 2 or more pieces went back a stage, and go back to (section⑪) |
Task board contents
Not started 16 items
Write current state
On page 1, write last time's result and today's ground rules, the events since launch, and how the team behaves. What you write here is the material for explaining your pieces on page 2. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.
Write last result
On the four notes of section①, write last time's result (leave blank the first time), the purpose and attendees, each person's piece color, and the ground rules for placing. Done when everyone can name their piece color.
Write the events
In the table of section②, write one line per month for events, what went well, and what clashed, from launch to this month. Done when no more than 2 cells are blank.
Describe the team
On sections③–⑤, write one note at a time on how easy it is to talk, how decisions are made and how people help each other, using things you actually saw. Done when each of the 3 frames has at least one note.
Place stage pieces
On page 2, everyone places a piece on the 5-stage flow, and you tabulate the piece count, the reasons and the gaps in how people see it. This parent task brings out everyone's different views before you choose actions.
Place your piece
Read the descriptions of the 5 stages in section⑥, then place a person stamp in your own color, one per person, on the stage closest to the team now. Done when everyone's piece is down.
Explain your reason
One minute each, say which events in sections②–⑤ you based it on, and write it in the Reason column of section⑦. Done when everyone has spoken.
Note the gaps
In the Pieces and Gap in views columns of section⑦, write the piece count per stage and the different views people had. Done when at least one gap is written.
Choose the actions
On page 3, pull troubles out of the gaps in views, then narrow the candidate actions to 1–2 using two criteria and votes. The action you test on page 4 is decided here.
Sort the troubles
Read each gap in section⑦ one by one, decide whether it is a trouble of roles, process or communication, and write it as a note on sections⑧–⑩. Done when each of the 3 frames has at least one.
Compare the actions
In the table of section⑪, write up to 4 candidate actions and fill in "Quick to do?" and "Everyone agrees?" with ○△×. Each person places 2 votes with circle stamps. Done when the count is written in the Votes column.
Record the reasons
In section⑫, write the chosen actions (1–2) and the ones set aside, each with its reason. Done when everyone has read it and has no objection.
Test and review
On page 4, split the chosen actions into first steps and decide owner, deadline, how to check and signal. After 30 days, place the pieces again, check whether the stage moved and lead into the next action.
Add the first steps
In the center of section⑬ write the action chosen in section⑫, and add a one-line first step for each branch. Done when the 4 branches are filled.
Owner and deadline
In the table of section⑭, write owner, deadline and how to check for each step, and set the day to re-place the pieces after 30 days. Done when it is in everyone's calendar.
Decide by signal
After 30 days, look at the Signal and fallback column of section⑭ and decide for each action whether to continue, change or stop. Done when the result is written in "Result of the action chosen last time" in section① of the next session.