A concretely phrased open question is available that can be thought through individually in 60 seconds and allows multiple answers.
1-2-4-All
Prerequisite
What needs to be finished first
Preparation
What needs to be ready before start
Timer with audible signal; whiteboard or Miro board for synthesis; pens or digital sticky notes; visible question at the top of the board.
One facilitator who leads phases and timing strictly; four to 60 participants; above 20 people, a co-facilitator for forming the 4-person groups and for plenary synthesis.
Question sent to the group as a single sentence in advance, at least 30 minutes before; context for the question in two to three sentences; desired output type (idea, assumption, decision, risk).
12-15 min core flow, plus 5-15 min plenary synthesis
Make the question central and clearly visible. Announce timer phases: 1 min alone, 2 min in pairs, 4 min in fours, 5 min plenary. Rule: write during the 1-person phase, otherwise ideas evaporate.
Core question
The one question this method answers
Which answers, ideas, or concerns about the question emerge when each person first thinks alone and then increasingly in the group?
Flow
Marker: Minute
| Step | Duration | Action | Hint |
|---|---|---|---|
10-1 min | 1 min | Silent individual work: Each person notes answers, ideas, or concerns about the question. Bullet points are enough. | If the room gets noisy, the facilitator reminds everyone of silence. Writing is mandatory, otherwise the thought is lost in the pair phase. |
21-3 min | 2 min | Pair exchange: Two people swap their notes, find common ground, and add to each other. One shared list per pair. | If someone has already read their sheet aloud after 30 seconds, they should actively ask the other person. Not two monologues, but dialogic synthesis. |
33-7 min | 4 min | Groups of four: Two pairs merge, compare their lists, and agree on two to three core points or patterns. | Four is the upper limit. A group of five suppresses one voice, a group of six splits into two camps. Stay strictly at four. |
47-12 min | 5 min | Plenary synthesis: Each 4-person group names its two to three core points in 30 seconds. The facilitator clusters them visibly on the board. No discussion in this phase. | If groups start arguing, the facilitator interrupts: 'First collect, then distill.' Argumentation happens after 1-2-4-All in a separate discussion round. |
Artifact
What comes out at the end
Visible cluster of the core points collected in plenary, saved as a photo or board export. Optionally transferred into a list with topic headers and frequency (how many groups named the point).
Date, question, and participant count in the header. For repeats with the same question, create a new file and note the previous run. Attach the cluster snapshot as an image because spatial arrangement matters.
- Miro or Mural board with a cluster frame
- Whiteboard with sticky notes, photographed
- Notion page with cluster headers and bullet lists
- FigJam board for hybrid settings with synchronous remote work
1-2-4-all-working-template.md
Compact working template for 1-2-4-All with context, input, output artifacts, and next step.
1-2-4-All Working Template
Goal
Scales idea generation from individual reflection to group and plenary synthesis.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- Idea List:
- Shared Insights:
- Emergent Themes:
Assumptions and open questions
- ...
Decision / Next step
Owner, date, and success signal.
Example output
Concrete filled scenario, fictional example
1-2-4-all-beispiel.md
Concrete filled scenario, fictional example
1-2-4-All — Team Falcon retrospective, 03.06.2026
Question: Which obstacles cost us the most energy over the last two weeks?
Participants: 16 people, 4 groups of four.
Plenary clusters
- Unclear requirements (4/4 groups): Tickets without acceptance criteria, follow-up questions only during the sprint.
- Tool switching between Linear and Jira (3/4): Duplicate maintenance, context loss.
- Late reviews (3/4): PRs wait 2-3 days, the author has to re-enter context.
- Meetings overlapping (2/4): Standups and refinement only 15 minutes apart, no focus block.
Next step
Top 2 clusters ('Unclear requirements' and 'Late reviews') go into Decision Jam on 06.06., owner: @sabine.
Pitfalls
Recognize symptoms and steer against them
Question too large or too vague
Participants ask during the 1-person phase what is meant, and the 4-person groups produce answers that do not match each other.
Abort the method and reshape the question into one concrete aspect with a clear answer type. Test: can the question be answered meaningfully in 60 seconds? If not, split it.
1-person phase is skipped
Conversation starts immediately, silence is perceived as uncomfortable, and the phase is interrupted.
The facilitator explicitly marks silence as a work phase. If the disruption repeats, make the timer visible and state silence as a rule, not a request.
Group size is not kept
Groups of five or six emerge because counting is lost or people drift together.
Have people count aloud before the 4-person phase and number themselves. If the number of people is odd, explicitly allow one 2-person or 3-person group, never a group of five.
Plenary turns into a discussion
Instead of 30 seconds of output per group, arguments start and the time window is exceeded by far.
The facilitator interrupts with 'We are only collecting now, we will deepen later.' Put argument points into a parking lot. Hold the discussion in a separate follow-up session with Decision Jam or a consensus workshop.
Top-down dominance in pairs
In mixed pairs with a hierarchy gap, only one person speaks and the other adds nothing of their own.
Arrange pairs in advance so that no direct reporting line is matched. Announce the rule: each person must report from their own notes in the pair phase, not simply agree.
Stop criteria
Done signals checkable in under a minute
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.