Project & Development
4L Retrospective for Beginners | Project-End Board: Choose 3 Promises for the Next Project
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.
Close a project with a 4L retrospective and pick 3 promises to carry into the next one.
Read more Show less
4L asks four questions: Liked, Learned, Lacked, and Longed for. This board pairs Lacked with Longed for items and narrows them to 3 promises. Line up the goal, result, and a timeline so everyone recalls the same period, then write notes in one color per person and group similar ones. Turn each pair into a draft promise, place it on a chart (likely to recur next project, changeable by us), and vote with 3 votes each. Give each chosen promise an owner, a check date, and a signal to redraft it if it is not kept.
Unlike KPT, which teams often run regularly, this board uses 4L once at a project milestone and goes on to what you long for next time. Plan on 5-8 people and 2 hours: 60 min for timeline and notes, 60 for promises and owners.
The board is four A4 pages. The task board has five 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
4L Retrospective for Beginners - Project-End Board
How to use (4 pages): ① Page 1, write purpose, goal vs. result, and timeline (sections①–④) → ② Page 2, add 4L notes, one color each, and group them (sections⑤–⑨) → ③ Page 3, pair Lacked with Longed for and pick 3 promises by vote (sections⑩–⑮) → ④ Page 4, set actions, owners, check dates, signals (sections⑯–⑱)
1/4 Review the period
① Purpose, period, people (start here)
- Purpose of this look back e.g. List what went well and what was lacking in the website rebuild, and carry 3 promises into the next project (rebuilding the newsletter)
- Period and participants e.g. June to August, 3 months. Five people (the director, comms, two in programs, and admin) meet for 2 hours on Thursday of the week after launch
- One color per person e.g. The director uses orange, comms purple, programs pink and turquoise, admin light purple. Pick colors different from the frame color, and add a name like (Director)
② Starting goal and final result
| Starting goal | Final result | Gap (number or word) | |
|---|---|---|---|
| Launch date | e.g. Live by July 31 | e.g. Launched Aug 20 | e.g. 3 weeks late |
| Inquiries | e.g. 10 a month | e.g. 4 in week 1 | e.g. Cannot tell yet |
| Update effort | e.g. Staff post news | e.g. Admin posted 3 | e.g. Done |
③ Timeline of key events (in time order)
- Start e.g. Week 1 of June. The 5 of us listed 30 problems with the current site
- Phase 1 e.g. June. Compared 2 web agencies and chose 1
- Phase 2 e.g. July. Gathering text. No deadline, so the programs text came 2 weeks late
- Phase 3 e.g. Early August. Re-requested photo permissions and pushed back the launch
- Phase 4 e.g. Launched Aug 20. Admin posted the news alone
- Goal e.g. Week after launch. Goal was 10 inquiries a month but only 4 came, so we held this retrospective
④ What the 4 Ls mean (read this)
- Liked and Learned Liked = what pleased you and what you want to keep. Learned = what you only understood by doing it
- Lacked and Longed for Lacked = what was missing in people, time, information, or tools. Longed for = what you wish for next time
- The name and the difference from KPT All four English words start with L, hence 4L. Longed for is sometimes put as wished for or wanted. KPT is often run regularly. This board uses 4L once at a milestone and goes on to what you long for
2/4 Write the four Ls
⑤ Liked = what to keep
- How to fill in: one thing per note, in your color, and add which event in ③ it is about
- e.g. (Director) The weekly 15-minute check-in got all 5 of us in one room
- e.g. (Admin) I can now post news on my own
- e.g. (Comms) Brighter photos brought in 1 volunteer application
⑥ Learned = learned by doing
- How to fill in: write what you found out in one sentence, closer to what happened than to a feeling
- e.g. (Programs) Learned that photos need permission from the people in them
- e.g. (Comms) Text is easier to write when you picture one reader
- e.g. (Director) Spelling out the request brought the quote down
⑦ Lacked = missing people, time, info
- How to fill in: do not blame people, write what was missing
- e.g. (Programs) No deadline for text, so it came 2 weeks late
- e.g. (Admin) There was no table to record photo permissions
- e.g. (Director) Nobody had the final say, so color choice took 3 meetings
⑧ Longed for = what you want next time
- How to fill in: write "Next time I want ..." or "I wish we had ..."
- e.g. (Programs) I want the text deadline set at the start
- e.g. (Admin) I want to check photo permissions in one place
- e.g. (Comms) I want the final decider chosen at the start of the project
⑨ Name groups of notes from ⑤–⑧
| Group name | Notes (frame, count) | People who wrote | |
|---|---|---|---|
| Group A | e.g. Deadlines, steps | e.g. 3 in ⑦, 2 in ⑧ | e.g. 4 people |
| Group B | e.g. Photos, permission | e.g. 1 in ⑥, 2 in ⑦, 1 in ⑧ | e.g. 3 people |
| Group C | e.g. Final decider | e.g. 2 in ⑦, 2 in ⑧ | e.g. 3 people |
| Group D | e.g. The web agency | e.g. 2 in ⑦, 1 in ⑧ | e.g. 2 people |
3/4 Pick promises to carry over
⑩ Pair A Deadline (⑦ + ⑧ = draft)
- e.g. Lacked → no text deadline, so it came 2 weeks late
- e.g. Longed for → set the text deadline at the start
- e.g. Draft promise → at the first meeting, make a table of owners and deadlines per text
⑪ Pair B Photo permission
- e.g. Lacked → no table to record photo permissions
- e.g. Longed for → check permissions in one place
- e.g. Draft promise → before using a photo, add a row to the permission table
⑫ Pair C Final decider
- e.g. Lacked → nobody decided, so color choice took 3 meetings
- e.g. Longed for → pick the decider at the start of the project
- e.g. Draft promise → at the first meeting, choose one final decider
⑬ Pair D Agency contact
- e.g. Lacked → all contact with the agency went through the director alone
- e.g. Longed for → let admin see the exchanges too
- e.g. Draft promise → send agency messages to a shared email address
⑭ Likely again × changeable (3 votes each)
Vertical axis: Likely in the next project too / Horizontal axis: We can change it ourselves
- Likely, hard to change Do not make it a promise. Tell whoever can change it. e.g. the board approval that takes 2 weeks - the director asks the board for an earlier meeting
- Likely, changeable Choose from here, up to 3. Each person places 3 circles and you pick in order of votes. e.g. Pair A 6 votes, Pair C 4, Pair B 3
- Unlikely, hard to change Set aside. Write the reason in ⑮. e.g. No draft landed here this time
- Unlikely, changeable Try it if you have room. e.g. Pair D 2 votes. The next project will not use an agency
⑮ Chosen promises, set-aside drafts
- 3 chosen promises e.g. A make the deadline table (6 votes), C pick a final decider (4 votes), B use the photo permission table (3 votes)
- Why we chose them e.g. All 3 will recur in rebuilding the newsletter, and the 5 of us can change them
- Set-aside drafts and why e.g. D shared email address (2 votes). The next project will not use an agency
4/4 Hand over to next project
⑯ 2 first actions for each promise in ⑮
- Promises for the next project
- Promise A Deadline table e.g. List the texts at the first meeting / write owners and deadlines
- Promise B Photo permissions e.g. Decide the table columns / add a row before using a photo
- Promise C Final decider e.g. Pick one at the first meeting / write the name in the table
- First meeting next project e.g. The newsletter meeting on the first Thursday of October. Read these 3 aloud
⑰ How to check promises next project
- Read aloud Read the 3 promises from ⑯ at the start of the first meeting e.g. The director reads them aloud in 5 minutes
- Say the date Each owner in ⑱ states the due date of the first action e.g. Programs says the deadline table will be ready by the second meeting
- Ask midway Ask at the weekly check-in whether each was kept e.g. Mark ○ or × in the last 3 minutes of the check-in
- Count At the end of the project, count how many were kept e.g. 2 of 3 kept. Discuss it at the next retrospective
⑱ Owner, check date, and signal
| Owner | Check date | Kept mark | Signal and fallback | |
|---|---|---|---|---|
| Promise A Deadline | e.g. Programs | e.g. First + weekly meetings | e.g. ○ in the table | e.g. Miss 2 in a row, change it. Go back to (board⑩–⑬) |
| Promise B Photos | e.g. Comms | e.g. The first day we use a photo | e.g. A row in the permission table | e.g. Keep it after 3 weeks of use. Go back to (board⑩–⑬) after 2 misses |
| Promise C Decider | e.g. Director | e.g. First meeting | e.g. The decider's name is in the table | e.g. Drop it if still undecided after 2 weeks. Go back to (board⑩–⑬) |
Task board contents
Not started 16 items
Review the period
On page 1, set the purpose, period, participants, and note colors, then line up the goal, result, and key events. Move to page 2 once everyone recalls the same period. Press Ctrl+F (⌘F on a Mac) and type "3/4" to jump to page 3.
Set purpose, colors
On the 3 notes in section ①, write the purpose, the period and people, and one note color per person. Done when everyone's color is set.
Goal and result
In the table in section ②, write the starting goal, the final result, and the gap for 3 rows. Done when the 3 gap cells are filled.
Build the timeline
In the 6 steps of section ③, write the key events in time order, one per step, then read the meaning of the 4 Ls together in section ④. Done when everyone says nothing more needs adding to the timeline.
Write the four Ls
On page 2, everyone puts notes in their own color under the four Ls, then you group similar ones. These notes are the raw material for the draft promises on page 3.
Write Liked/Learned
Looking at the timeline in ③, put at least 2 notes each in your color under Liked in ⑤ and Learned in ⑥.
Write Lacked/Longed
Under Lacked in ⑦ and Longed for in ⑧, put at least 2 notes each in your color. Done when you wrote what was missing rather than who was at fault.
Group similar notes
Move similar notes in ⑤ to ⑧ together, and in the table in ⑨ write each group's name, its notes, and the number of people, up to 4 rows.
Choose the promises
On page 3, pair Lacked and Longed for notes into draft promises, then narrow them to 3 with the 2 axes and votes. Only the promises chosen here go to the next project.
Draft 4 promises
Using the groups in ⑨ as clues, pair one note each from ⑦ and ⑧ and write one draft promise in each of ⑩ to ⑬.
Place, vote 3 each
Place the drafts from ⑩ to ⑬ on the chart in ⑭, and give each person 3 circle stamps. Done when you pick the 3 with the most votes from those in the top right.
Write the reasons
In ⑮, write the 3 chosen promises with reasons, and the set-aside drafts with reasons. Done when the 3 notes are filled.
Hand over promises
On page 4, set the first action, owner, and check date for each promise. This retrospective ends when you read the promises aloud at the first meeting of the next project.
Write first actions
On the branches in ⑯, write the 3 promises and the date of the next project's first meeting, and add 2 first actions for each promise.
Set owners, dates
In the table in ⑱, write each promise's owner, check date, and kept mark. Done when the steps in ⑰ are on the agenda of the next project's first meeting.
Keep or change them
Midway through the next project, read the Signal and fallback column in ⑱ and decide to keep, change, or drop each promise. Write the result in the same column, and for a dropped promise go back to ⑩ to ⑬ and redraft it.