Example data. Fieldnote is a fictional company used to fill all 61 boards, so the examples tell one consistent story.
Field app squad at Fieldnote, monthly health check in May, after the March photo incident and before the offline mode project starts.
What the team took away
One red, on dependencies: the squad books a cross-team dependency map for next week instead of another retro.
How to run it
Preparation
The whole team, no manager in the room. The manager gets the result, not the debate.
Send the eight attributes with their green and red descriptions 2 days before, so nobody discovers the vocabulary live.
Grid ready: eight rows, columns Green, Yellow, Red, Trend. Prepare voting cards or a hidden poll; votes must be simultaneous.
Agenda
5 min
Rules Explain: everyone votes at the same time, red is normal, this is not a performance review. Say it twice.
25 min
Vote attribute by attribute For each of the eight attributes, read the green and red definition, count to three, everyone shows their card. Record the majority color and the spread.
15 min
Discuss the splits Only discuss attributes where votes were split or red. Two minutes each, ask the red voters first: what would make it yellow?
5 min
Trend For each attribute, arrow up, flat, or down compared to last time. If this is the first session, skip it.
10 min
One action Pick one red or downward attribute. One action the team can do itself before the next check. Owner, date, posted.
Pitfalls
Do not let people vote one after another. The second voter copies the first. Simultaneous or nothing.
Do not discuss the green attributes. You have 15 minutes of discussion; spend them on red.
Do not leave with three actions. This format works because it produces one, and the next check tells you if it worked.
Afterwards
The result goes to the manager as a photo of the grid, no commentary. Rerun every 4 to 6 weeks and compare trends. A red on Dependencies calls for a dependency map; a red on Value delivered calls for an OKR or impact mapping session, not another retro.