What makes a project retrospective lead to change?
How many actions are realistic? Who checks follow-through?
Topic library
How many actions are realistic? Who checks follow-through?
Which expectations should be shared? Which accommodations can remain private?
Which details should move to an appendix? How can obsolete pages be retired?
What would make reversal expensive? Who should approve each kind?
How much reasoning should be shared? When is reconsideration appropriate?
Which variable should stay fixed? How can results avoid overgeneralization?
What inequality may precede the process? How should appeals work?
What commitment can still be clear? How often should updates come?
What evidence would justify stopping? Who can raise the question safely?
What should be clarified before escalating? How can a backup plan protect the relationship?
Which norm serves a real need? Who should revise the agreement?
What limits are agreed beforehand? How are unexpected effects reported?
Which checks support trust? How can review avoid suspicion?
Whose interests might be missing? What alternative measure helps?
Does expertise justify exceptions? How can the load stay visible?
Who needs to be consulted? How should an overpromise be repaired?
Which room comes first? What question would you ask the guide?
Which object becomes a landmark? Where is the busiest route?
Which scent leads? What would you name it?
What problem would it face? How would it express surprise?
Where would it store the collection? What item would be rare?
What room would be hardest to design? How would visitors enter?
What mood should it create? Would each floor sound different?
Decide who finds the button and where. Connect the button to an unexpected obligation.
100 focused questions + a 60-second practice for each.